MCP.so
ログイン

TeamDynamix MCP Server

@selfagency

基本情報

カテゴリ

その他

トランスポート

stdio

作者

selfagency

投稿者

Daniel Sieradski

TeamDynamix MCP Server について

🎟️ TeamDynamix MCP Server (unofficial)

#teamdynamix#tdx#itsm#issues#tickets

TeamDynamix MCP Server の設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

{
  "mcpServers": {
    "git": {
      "command": "npx",
      "args": [
        "-y",
        "@selfagency/teamdynamix-mcp"
      ],
      "env": {
        "TEAMDYNAMIX_BASE_URL": "https://your-tenant.teamdynamix.com",
        "TEAMDYNAMIX_AUTH_MODE": "standard",
        "TEAMDYNAMIX_USERNAME": "your-username",
        "TEAMDYNAMIX_PASSWORD": "your-password-preferably-stored-securely"
      }
    }
  }
}

TeamDynamix MCP Server のツール

11

Gateway for discovery operations: server status, current user, applications, and ticket status lookup.

Gateway for ticket metadata, read/search, create/update, comments, and feed operations.

Gateway for ticket tasks, linked assets, and linked contacts operations.

Gateway for user and group retrieval/search operations.

Gateway for TeamDynamix Knowledge Base retrieval, search, and write operations.

Gateway for TeamDynamix asset retrieval, search, and lookup enumerations.

Gateway for CI/CMDB retrieval, search, types, relationship types, and vendors.

Gateway for TeamDynamix service catalog list/get/search/category operations.

Gateway for TeamDynamix projects retrieval/search and project issue/risk operations.

Gateway for TeamDynamix time type lookup and authenticated user time entries.

Gateway for TeamDynamix reference/enumeration lookups such as accounts, locations, roles, and custom attributes.

概要

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

よくある質問

1

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.

2

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.

3

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.

4

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.

5

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.

コメント

「その他」の他のコンテンツ