TeamDynamix MCP

What is TeamDynamix MCP?

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

How to use TeamDynamix MCP?

Install via npm (npx -y @selfagency/teamdynamix-mcp) and configure with environment variables: TEAMDYNAMIX_BASE_URL, TEAMDYNAMIX_AUTH_MODE (standard or admin), and credentials. Then call domain gateway tools (e.g., teamdynamix_discovery, teamdynamix_tickets) with an action, payload, and response format ("markdown" or "json").

Key features of TeamDynamix MCP

• 11 domain gateway tools covering tickets, assets, KB, CMDB, and more
• Safe by default: write, delete, and admin tools disabled until opted in
• Two authentication modes: standard (username/password) and admin (BEID/WebServicesKey)
• Covers 207 API endpoints across all TeamDynamix domains
• Rate-limit aware with built-in retry and exponential backoff
• Zod-validated inputs enforce schema before any API call

Use cases of TeamDynamix MCP

• Automate ticket creation, updates, and relationship management via AI agents
• Query and manage assets, CMDB CIs, and knowledge base articles
• Retrieve people, services, projects, time entries, and reference data
• Build safety-gated ITSM workflows with destructive operations requiring explicit confirmation

FAQ from TeamDynamix MCP

What authentication modes are supported and what credentials are required?

Standard mode requires a username and password. Admin mode requires a BEID and WebServicesKey. Set TEAMDYNAMIX_AUTH_MODE accordingly.

Are write, delete, and admin tools enabled by default?

No. They are disabled by default and must be explicitly enabled via environment flags (TEAMDYNAMIX_ENABLE_WRITE_TOOLS, TEAMDYNAMIX_ENABLE_DELETE_TOOLS, TEAMDYNAMIX_ENABLE_ADMIN_TOOLS). Destructive operations also require confirm: true in the tool call.

How does the server handle rate limiting?

The SDK has built-in retry with exponential backoff on HTTP 429 and 5xx responses, making it rate-limit aware.

Where does the data live? Is data stored locally?

The server acts as a gateway to TeamDynamix’s API; no data is persisted locally beyond configuration environment variables. All operations are performed against your TeamDynamix tenant.

What transports and authentication methods are supported?

The server uses the stdio transport (MCP standard). Authentication is via the two modes described above; credentials are passed as environment variables at runtime.