TDX MCP Server
Related Servers
Alternatives to TDX MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceAn 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.1-
- FlicenseNot gradedqualityCmaintenanceMCP server for an AI IT helpdesk that exposes 29 tools, 10 resources, and 6 prompts for ticket management, knowledge base search, employee lookup, reporting, and Slack notifications, with a multi-agent conversation pipeline.-
- FlicenseNot gradedqualityNot gradedmaintenanceA comprehensive MCP server that provides 159 tools for interacting with the Freshservice ITSM platform, covering modules such as tickets, assets, and project management. It enables users to manage service desk operations and configuration through the Model Context Protocol.-
- FlicenseNot gradedqualityBmaintenanceMCP server that provides IT support tools to search known incidents, check ticket status, and create ticket drafts, enabling an AI assistant to help users with IT support queries.-
- AlicenseCqualityDmaintenanceMCP server that exposes the complete Libredesk REST API (54 endpoints) as tools, enabling natural language management of conversations, contacts, agents, teams, and more for the open-source customer support desk.543 npm4MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to interact with TeamDynamix ITSM operations including tickets, assets, KB, and more through safety-gated tools.182 npm2MIT
TDQS
Scored across 41 tools
Every tool has a clearly distinct purpose with no ambiguity. Tools are organized by resource type (account, asset, cmdb, group, kb, people, project, ticket) and action (get, search, create, update, delete, etc.), making it easy for an agent to distinguish between them. Even similar-sounding tools like 'tdx-asset-patch' and 'tdx-asset-update' are clearly differentiated by their descriptions (partial vs. full update).
Tool names follow a perfectly consistent pattern throughout: 'tdx-[resource]-[action]' with hyphens separating components. All tools use the same naming convention (e.g., tdx-asset-get, tdx-ticket-create, tdx-people-search), with no deviations in style or structure. This predictability makes the tool set highly readable and easy to navigate.
With 41 tools, the count is borderline high for typical MCP servers, which often have 3-15 tools for well-scoped purposes. While the tools cover a comprehensive set of operations for TDX (a service management platform), the number might feel heavy and could overwhelm agents or lead to complexity in tool selection. However, given the broad domain (multiple resource types like tickets, assets, projects), it's not extreme but leans toward the upper limit of appropriateness.
The tool set provides complete CRUD/lifecycle coverage for all major TDX domains (accounts, assets, configuration items, groups, knowledge base, people, projects, tickets). Each resource type includes get, search, create, update, and delete operations where applicable, plus additional actions like adding comments or relationships. There are no obvious gaps; agents can perform end-to-end workflows without dead ends.