mcpField
T
TeamDynamix MCP

TeamDynamix MCP

Local
teamdynamix-mcp.self.agencyBusiness & Marketing3Updated today

About TeamDynamix MCP

TeamDynamix MCP is a TypeScript server for AI agents and MCP clients that need structured access to TeamDynamix ITSM. It groups operations across service domains and gates risky changes behind explicit settings and confirmation.

Key features

  1. 0111 domain gateway tools
  2. 02Coverage across 207 API endpoints
  3. 03Write and admin actions disabled by default
  4. 04Explicit confirmation for destructive actions
  5. 05Standard and admin authentication modes
  6. 06Input validation and rate-limit retries

Use cases

  1. 01Look up and manage support tickets
  2. 02Retrieve knowledge base and asset data
  3. 03Work with people, services, and projects
  4. 04Enable controlled TeamDynamix changes

MCP support

Exposes TeamDynamix ITSM operations to MCP clients through gateway tools for discovery, tickets, knowledge base, assets, CMDB, people, services, projects, time, and reference data. Write and destructive actions are gated by configuration and confirmation.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"teamdynamix": {
"command": "npx",
"args": [
"-y",
"@selfagency/teamdynamix-mcp"
],
"env": {
"TEAMDYNAMIX_BASE_URL": "<TEAMDYNAMIX_BASE_URL>",
"TEAMDYNAMIX_AUTH_MODE": "<TEAMDYNAMIX_AUTH_MODE>",
"TEAMDYNAMIX_USERNAME": "<TEAMDYNAMIX_USERNAME>",
"TEAMDYNAMIX_PASSWORD": "<TEAMDYNAMIX_PASSWORD>"
}
}
}
}
Run commandnpx -y @selfagency/teamdynamix-mcp
Environment variables to set
TEAMDYNAMIX_BASE_URL
TEAMDYNAMIX_AUTH_MODESecret
TEAMDYNAMIX_USERNAME
TEAMDYNAMIX_PASSWORDSecret

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@selfagency/teamdynamix-mcp

Tools

11

Saved tool list · updated 3w ago

ParameterTypeRequiredDescription
actionenumYesserver_status | get_current_user | list_applications | list_ticket_statuses
payloadobjectNo
response_formatenumNoOutput format for the response.markdown | json

Details

From the project README

🎟️ TeamDynamix MCP Server (unofficial)

NPM Version CI codecov

A TypeScript Model Context Protocol (MCP) server that exposes TeamDynamix ITSM capabilities as agent-callable tools. Designed for AI agents and MCP clients that need structured, safety-gated access to TeamDynamix operations.

Features

  • 11 domain gateway tools that route validated actions across discovery, tickets, relationships, KB, assets, CMDB, people, services, projects, time, and reference data
  • Safe by default: write, delete, and admin tools disabled until explicitly opted in; destructive operations require confirm: true
  • Two auth modes: standard (username/password) and admin (BEID/WebServicesKey)
  • Covers 207 API endpoints across all TeamDynamix domains, verified against the SDK route manifest
  • Rate-limit aware: SDK built-in retry with exponential backoff on 429 and 5xx responses
  • Zod-validated inputs: schema enforcement before any API call
  • Agent skill and prompt included: ready-to-use skill definition for GitHub Copilot and compatible agents

MCP Registry

This server is published to the MCP Registry as io.github.selfagency/teamdynamix-mcp.

  • Registry name: io.github.selfagency/teamdynamix-mcp
  • Install via registry: mcp-install io.github.selfagency/teamdynamix-mcp (when available)
  • Manual install: Use npm package @selfagency/teamdynamix-mcp as shown below

Quick start (developer setup)

This quick start is for contributors running the server from source in this repository. If you are a regular MCP client user, skip to MCP client configuration and use the npx command examples.

# 1. Clone the repository
git clone https://github.com/selfagency/teamdynamix-mcp.git
cd teamdynamix-mcp

# 2. Install dependencies
pnpm install

# 3. Configure environment
cp .env.example .env
# Edit .env with your TeamDynamix credentials and base URL

# 4. Start the development server
pnpm dev
Minimum required environment variables
TEAMDYNAMIX_BASE_URL=https://your-tenant.teamdynamix.com/TDWebApi
TEAMDYNAMIX_AUTH_MODE=standard          # or: admin
[email protected]    # standard mode
TEAMDYNAMIX_PASSWORD=your-password      # standard mode

# Optional: default application IDs (used when app_id is omitted in tool calls)
TEAMDYNAMIX_DEFAULT_TICKET_APP_ID=12345
TEAMDYNAMIX_DEFAULT_ASSET_APP_ID=23456
TEAMDYNAMIX_DEFAULT_KB_APP_ID=34567

For admin mode, use TEAMDYNAMIX_BEID and TEAMDYNAMIX_WEB_SERVICES_KEY instead.

MCP client configuration

Security notice: Values shown above are placeholders. Never commit real credentials to source control. Inject secrets at runtime via a .env file (excluded by .gitignore), CI/CD secrets, or a secret manager.

VS Code (.vscode/mcp.json)
{
  "servers": {
    "teamdynamix": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@selfagency/teamdynamix-mcp"],
      "env": {
        "TEAMDYNAMIX_BASE_URL": "https://your-tenant.teamdynamix.com/TDWebApi",
        "TEAMDYNAMIX_AUTH_MODE": "standard",
        "TEAMDYNAMIX_USERNAME": "[email protected]",
        "TEAMDYNAMIX_PASSWORD": "your-password"
      }
    }
  }
}
Claude Desktop (claude_desktop_config.json)
{
  "mcpServers": {
    "teamdynamix": {
      "command": "npx",
      "args": ["-y", "@selfagency/teamdynamix-mcp"],
      "env": {
        "TEAMDYNAMIX_BASE_URL": "https://your-tenant.teamdynamix.com/TDWebApi",
        "TEAMDYNAMIX_AUTH_MODE": "standard",
        "TEAMDYNAMIX_USERNAME": "[email protected]",
        "TEAMDYNAMIX_PASSWORD": "your-password"
      }
    }
  }
}
Production (built bundle)
pnpm build   # outputs to dist/
{
  "command": "npx",
  "args": ["-y", "@selfagency/teamdynamix-mcp"]
}
Verify connectivity

After connecting your MCP client, call teamdynamix_discovery with:

  • action: "server_status"
  • payload: {}
  • response_format: "json"

A successful response shows status.configured: true.

Domain gateway tools

Each gateway tool accepts:

  • action: domain-specific operation name
  • payload: object for that action’s parameters
  • response_format: "markdown" or "json"
DomainGateway tool
Discoveryteamdynamix_discovery
Ticketsteamdynamix_tickets
Ticket relationshipsteamdynamix_ticket_relationships
Knowledge Baseteamdynamix_knowledge_base
Assetsteamdynamix_assets
CMDBteamdynamix_cmdb
Peopleteamdynamix_people
Servicesteamdynamix_services
Projectsteamdynamix_projects
Timeteamdynamix_time
Reference datateamdynamix_reference_data

† Requires confirm: true in addition to write tools being enabled.

All write/mutating actions require TEAMDYNAMIX_ENABLE_WRITE_TOOLS=true.

Safety defaults

FlagDefaultEffect when true
TEAMDYNAMIX_ENABLE_WRITE_TOOLSfalseEnables all create/update/comment/mutation tools
TEAMDYNAMIX_ENABLE_DELETE_TOOLSfalseEnables asset, CI, service, and service category deletion
TEAMDYNAMIX_ENABLE_ADMIN_TOOLSfalseEnables admin-scope operations

Destructive operations additionally require confirm: true in the tool call regardless of the flag state.

Agent skill

This repository ships a GitHub Copilot-compatible skill definition:

Install the skill via your Copilot skill configuration (see skills/teamdynamix/SKILL.md for full details).

Documentation

SectionPurpose
TutorialsStep-by-step setup and first workflows
How-to guidesTask-oriented recipes for real operations
ReferenceExhaustive tool catalog, configuration, safety model, errors
ExplanationArchitecture, auth model, safety rationale, rate limiting
DevelopmentArchitecture, contributing, testing

Development

pnpm typecheck   # TypeScript strict checks
pnpm lint        # oxlint
pnpm test        # vitest (200+ tests, 90%+ coverage)
pnpm build       # tsup → dist/

License

MIT © The Self Agency LLC

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.