clm-mcp
Related Servers
Alternatives to clm-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceExposes RFQ, travel, and hospitality operations as MCP tools backed by a GraphQL API.MIT
- FlicenseAqualityDmaintenanceExposes the OpenProject REST API as MCP tools for project management, including creating and managing projects, work packages, relations, attachments, users, notifications, watchers, boards, and reference data.37-
- FlicenseNot gradedqualityDmaintenanceEnables merchants to connect their PostEx account to MCP clients, exposing tools to book and cancel COD orders, track parcels, generate load sheets and airway bills, and check settlement status using their own PostEx token.2-
- AlicenseAqualityCmaintenanceEnables local MCP clients to securely inspect and operate a project's HTTP API, with generated tools for todos, dashboards, announcements, finances, materials, and related workflows using scoped API keys.142MIT
- FlicenseAqualityDmaintenanceMCP server that exposes tools for monitoring supply chain disruptions, including vessel positions, port weather, congestion, and news. Includes an AI agent that synthesizes these sources to assess route risks.5-
- AlicenseBqualityBmaintenanceEnables MCP clients to query and update projects, boards, and tasks with the user's permissions, including comments, checklists, time logging, dashboards, and evidence attachments.22MIT
TDQS
Scored across 82 tools
Multiple tool boundaries are unclear: the regular and Smart Shipment wizard step tools differ only by prefix, clm_shipment_command_delete_draft_shipment is described as a status transition that collides with clm_shipment_command_update_shipment_status, and the generic clm_invoke overlaps with many concrete write tools. Agents would need to read long descriptions very carefully to reliably pick the intended tool.
The naming follows a strong clm_<domain>_command_<verb>_<object> pattern for writes and clm_list_/clm_get_/clm_count_ for reads, with consistent snake_case throughout. Minor deviations include clm_whoami, the generic clm_invoke/list/describe tools, and the misleading delete_draft_shipment name that does not match its described behavior.
With 82 tools, the surface is far beyond a well-scoped MCP server, and it includes near-duplicate wizard variants, many overlapping status/comment/update commands, and a generic invoke escape hatch. This imposes a severe context and selection burden on agents and is an extreme count for practical use.
The set provides broad lifecycle coverage for shipments, equipment, incidents, lean cards, material handovers, reports, and user filters, with no obvious dead ends for the main workflows. The main gaps are first-class reference-data lookups such as listing teams, zones, materials, and vehicles, though the generic invoke/describe tools can partly work around these.