Claude Plugin

The TeamDynamix MCP server ships as a Claude plugin — a package of skills, commands, and MCP server configuration that teaches Claude how to use your TDX tools effectively.

What the plugin provides

Component	Description
Navigation skill	Teaches Claude the lazy-loading pattern — always call `tdx_navigate` before domain tools
Tickets skill	Guided workflows for searching, creating, and updating tickets
Assets skill	Search, view, and create hardware/inventory assets
People skill	Directory lookups with cross-domain workflows (e.g., find UID → assign ticket)
Knowledge Base skill	Search, read, and create KB articles with category browsing
`/start` command	Onboarding flow that verifies connectivity and shows available domains

Installing the plugin

Add the marketplace and install the plugin in Claude Code:

/plugin marketplace add chatt-state/teamdynamix-mcp-server
/plugin install teamdynamix@teamdynamix-mcp-server

The plugin uses npx to run the MCP server automatically — no build step needed.

Set the required environment variables before starting:

export TDX_BASE_URL=https://yourinstance.teamdynamix.com
export TDX_BEID=your-beid-guid
export TDX_WEB_SERVICES_KEY=your-web-services-key
export TDX_TICKETING_APP_ID=123
export TDX_ASSETS_APP_ID=456
export TDX_KB_APP_ID=789

To update later: /plugin marketplace update teamdynamix-mcp-server

Clone the repo and add it as a plugin:

git clone https://github.com/chatt-state/teamdynamix-mcp-server.git

Then add the plugin path to your Claude Code settings. The .mcp.json at the repo root configures the MCP server automatically.

Set the required environment variables before starting:

export TDX_BASE_URL=https://yourinstance.teamdynamix.com
export TDX_BEID=your-beid-guid
export TDX_WEB_SERVICES_KEY=your-web-services-key

Add the MCP server to your claude_desktop_config.json:

{
  "mcpServers": {
    "teamdynamix": {
      "command": "npx",
      "args": ["-y", "--registry", "https://npm.pkg.github.com", "@chatt-state/teamdynamix-mcp-server"],
      "env": {
        "TDX_BASE_URL": "https://yourinstance.teamdynamix.com",
        "TDX_BEID": "your-beid-guid",
        "TDX_WEB_SERVICES_KEY": "your-web-services-key",
        "TDX_TICKETING_APP_ID": "123",
        "TDX_ASSETS_APP_ID": "456",
        "TDX_KB_APP_ID": "789"
      }
    }
  }
}

Using the `/start` command

After installing, type /start to verify your connection:

You: /start

Claude: calls tdx_status — Server is running. Ticketing app configured (ID: 123), Assets configured (ID: 456), KB configured (ID: 789). What would you like to do?

How skills work

Skills are markdown files that Claude reads automatically when your request matches their trigger conditions. You don’t need to invoke them — they activate based on what you ask.

For example, asking “find open tickets about printing” triggers the tickets skill, which tells Claude to:

Call tdx_navigate({ domain: "tickets" }) to load ticket tools
Call tdx_tickets_search({ searchText: "printing" }) to find matches
Format results as a table with ID, Status, Title, and Requestor columns

Skill triggers

Skill	Activates when you mention…
Navigation	”TDX”, “TeamDynamix”, “ITSM”
Tickets	”ticket”, “incident”, “service request”, “help desk”
Assets	”asset”, “hardware”, “serial number”, “laptop”, “inventory”
People	”person”, “user”, “contact”, “directory”, “who is”
Knowledge Base	”KB”, “knowledge base”, “article”, “FAQ”, “how-to”

Plugin structure

teamdynamix-mcp-server/
├── .claude-plugin/
│   ├── plugin.json          # Root plugin (for local installs)
│   └── marketplace.json     # Marketplace catalog
├── plugins/
│   └── teamdynamix/         # Marketplace plugin package
│       ├── .claude-plugin/
│       │   └── plugin.json
│       ├── skills/
│       │   ├── navigation/SKILL.md
│       │   ├── tickets/SKILL.md
│       │   ├── assets/SKILL.md
│       │   ├── people/SKILL.md
│       │   └── knowledge-base/SKILL.md
│       └── commands/
│           └── start.md
├── skills/                  # (mirrors plugins/teamdynamix/skills/)
├── commands/                # (mirrors plugins/teamdynamix/commands/)
└── .mcp.json                # MCP server config (local dev)

ℹ️ Note

The plugin’s skills teach Claude when and how to use each tool, including the critical navigation prerequisite. Without the plugin, Claude can still use the MCP tools directly — but may not know to call tdx_navigate first.