cpp-espace-mcp
Related Servers
Alternatives to cpp-espace-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server for interacting with QUADS infrastructure systems via API, enabling resource management and automation through LLM applications.MIT
- FlicenseNot gradedqualityCmaintenanceMCP server that provides live facility data access and operational tools, enabling the AI agent to query sensor readings, HVAC status, energy usage, alerts, and execute confirmed maintenance actions.-
- FlicenseNot gradedqualityCmaintenanceAn MCP server that connects Claude Desktop to the IT Asset Tracker backend, giving Claude access to 70+ tools for managing assets, users, requests, and reports.-
- AlicenseNot gradedqualityFmaintenanceMCP server that enables Claude to interact with Google Workspace services including Drive, Docs, Sheets, Slides, Calendar, Gmail, and Contacts.564 npm38MIT
- AlicenseAqualityCmaintenanceMCP Server for the Slack API, enabling Claude to interact with Slack workspaces.870,822 npmMIT
- -licenseNot gradedqualityAmaintenanceMCP Server for the Slack API, enabling Claude to interact with Slack workspaces.70,822 npm90,629MIT
TDQS
Scored across 31 tools
Each tool is clearly named with a distinct resource and action, avoiding overlap. Sub-resources like work-order tasks, costs, attachments are explicitly separated, making it easy for an agent to select the correct tool.
All tools follow a consistent verb-noun pattern using lowercase with hyphens (e.g., get-work-order, create-work-order, list-events). There are no deviations or mixed conventions, ensuring predictability.
With 31 tools, the count is on the higher side, but the domain covers work orders, events, maintenance, and equipment, each with several sub-resources. The tools are well-scoped to the domain, though some consolidation of related getters could reduce the count.
Work orders have full CRUD plus sub-resource operations, but events, maintenance, and equipment only have read operations (get/list) with no create, update, or delete. This leaves notable gaps for managing these core entities.