TDX MCP Server

TDX MCP Server

An MCP server that wraps the TeamDynamix Web API, enabling AI assistants to search tickets, manage assets, query the knowledge base, and look up people in your TDX instance.

Category
Visit Server

README

TDX MCP Server

An MCP (Model Context Protocol) server that wraps the TeamDynamix Web API, enabling AI assistants to search tickets, manage assets, query the knowledge base, and look up people in your TDX instance.

Quickstart

Prerequisites

  • Bun v1.3+
  • A TeamDynamix instance with Web API access
  • Admin service account credentials (BEID + Web Services Key)

1. Install dependencies

bun install

2. Configure environment

cp .env.example .env

Edit .env with your TDX instance details:

TDX_BASE_URL=https://yourinstance.teamdynamix.com/TDWebApi/api
TDX_BEID=your-admin-beid-guid
TDX_WEB_SERVICES_KEY=your-web-services-key-guid
TDX_TICKETING_APP_ID=123
TDX_ASSET_APP_ID=456
TDX_KB_APP_ID=789

Finding your App IDs: If you don't know your application IDs, you can discover them after setup using the tdx_applications_list tool, or by calling GET /api/applications on your TDX instance directly.

3. Run the server

bun run src/index.ts

The server communicates over stdio using the MCP protocol. It's designed to be launched by an MCP client (like Claude Desktop or Claude Code), not run standalone.

4. Connect to an MCP client

Claude Desktop (~/.claude/claude_desktop_config.json):

{
  "mcpServers": {
    "tdx": {
      "command": "bun",
      "args": ["run", "/absolute/path/to/src/index.ts"],
      "env": {
        "TDX_BASE_URL": "https://yourinstance.teamdynamix.com/TDWebApi/api",
        "TDX_BEID": "your-beid",
        "TDX_WEB_SERVICES_KEY": "your-key",
        "TDX_TICKETING_APP_ID": "123",
        "TDX_ASSET_APP_ID": "456",
        "TDX_KB_APP_ID": "789"
      }
    }
  }
}

Claude Code (.claude/settings.json):

{
  "mcpServers": {
    "tdx": {
      "command": "bun",
      "args": ["run", "/absolute/path/to/src/index.ts"]
    }
  }
}

When using Claude Code, place your credentials in .env at the project root (it's gitignored). Bun loads .env automatically.

Running tests

# All tests (unit + QA)
bun run test

# Unit tests only
bun run test:unit

# QA/integration tests only
bun run test:qa

Unit and QA tests run in separate processes to avoid mock.module cross-contamination.

Project structure

src/
  index.ts              # Entry point — stdio transport, graceful shutdown
  server.ts             # MCP server — tool registration
  config.ts             # Env var loading with Zod validation
  auth/
    client.ts           # TDX auth — JWT caching, proactive refresh
    schemas.ts          # Auth Zod schemas
  api/
    client.ts           # Fetch wrapper — auth headers, retry on 429
    rate-limiter.ts     # Client-side sliding window rate limiter
  tools/
    tickets.ts          # Ticket tool handlers
    assets.ts           # Asset tool handlers
    kb.ts               # Knowledge base tool handlers
    people.ts           # People tool handlers
    applications.ts     # Applications tool handler
    utils.ts            # safeToolCall error wrapper
    schemas/            # Zod input schemas for each tool
tests/
  config.test.ts        # Config loading tests
  server.test.ts        # Server creation tests
  auth/                 # Auth client tests
  api/                  # API client + rate limiter + error scenario tests
  tools/                # Tool handler tests
  qa/                   # End-to-end MCP server tests
  fixtures/             # Realistic TDX API response fixtures

Authentication

The server uses TDX admin authentication (POST /api/auth/loginadmin) with BEID and Web Services Key. The JWT is cached in memory and refreshed automatically 5 minutes before expiry (tokens last 24 hours).

Rate limiting

TDX enforces per-endpoint rate limits with no response headers. The server tracks limits client-side using a sliding window algorithm. Limits vary by endpoint:

Endpoint Limit
Ticket search 30 / 60s
Ticket create 120 / 60s
People CRUD 45 / 60s
People lookup 75 / 10s
Most others 60 / 60s

On 429 responses, the server retries up to 3 times with backoff.

Tech stack

  • Runtime: Bun
  • Language: TypeScript (strict mode)
  • MCP SDK: @modelcontextprotocol/server
  • Validation: Zod
  • Linting/Formatting: Biome
  • Testing: bun:test

Recommended Servers

playwright-mcp

playwright-mcp

A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.

Official
Featured
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.

Official
Featured
Local
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.

Official
Featured
Local
TypeScript
VeyraX MCP

VeyraX MCP

Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.

Official
Featured
Local
graphlit-mcp-server

graphlit-mcp-server

The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.

Official
Featured
TypeScript
Kagi MCP Server

Kagi MCP Server

An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.

Official
Featured
Python
E2B

E2B

Using MCP to run code via e2b.

Official
Featured
Neon Database

Neon Database

MCP server for interacting with Neon Management API and databases

Official
Featured
Exa Search

Exa Search

A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.

Official
Featured
Qdrant Server

Qdrant Server

This repository is an example of how to create a MCP server for Qdrant, a vector search engine.

Official
Featured