calmcp
Related Servers
Alternatives to calmcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceA config-driven MCP server that exposes OData and REST APIs as MCP tools, enabling AI assistants to query, manage, and monitor SAP backends through natural language.170 npm33MIT
- AlicenseNot gradedqualityBmaintenanceMCP server for SAP Cloud ALM, providing 54 tools across 9 services to manage features, tasks, test cases, documents, projects, and more via natural language.33 npm6GPL 3.0
- AlicenseBqualityBmaintenanceA local MCP server that connects to SAP ABAP systems via ADT HTTP API, enabling AI assistants to search, read, and manage ABAP objects securely without SAP GUI.5417 npm8MIT
- AlicenseBqualityDmaintenanceMCP server for SAP ABAP development that enables AI assistants and code editors to interact with SAP systems via ABAP Developer Toolkit (ADT) APIs, supporting read, create, update, and delete of ABAP objects.100MIT
- FlicenseNot gradedqualityBmaintenanceAn MCP server for AI assistants to create and manage SAP Solution Manager Focused Build Requirements and navigate the Solution Documentation process hierarchy via SAP OData API.-
- FlicenseBqualityNot gradedmaintenanceAn MCP server that enables AI assistants to interact with SAP systems via the ABAP Development Tools (ADT) REST API. It allows users to read ABAP source code, inspect DDIC objects, and execute SQL queries directly.66-
TDQS
Scored across 4 tools
calm_list, calm_analytics, and calm_get are largely distinguishable by cardinality (collection vs single entity), but calm_list and calm_analytics both accept count_only and group_by and both cover tasks/defects, so 'how many defects?' can plausibly route to either. The descriptions do add guidance (project-scoped OData vs tenant-wide provider, sorting ignored), which keeps it workable but not frictionless. calm_resources is clearly separate as a discovery helper.
All four tools share the calm_ prefix and snake_case, giving a predictable namespace. Three names imply an action (list/get/analytics) while calm_resources is a plain noun, a minor deviation but still readable and consistent with the rest.
Four parameterized tools cover a very broad domain (tasks, projects, features, tests, landscape, hierarchy) via a resource argument, which is a sensible, compact design rather than an explosion of per-resource tools. The count is on the lean side for such a wide surface, but each tool earns its place.
Read coverage is strong—list, filtered query, aggregation, single-entity fetch, and a discovery catalog—but the surface is entirely read-only, with no create, update, or delete operations for tasks, defects, features, or documents. Agents can inspect CALM thoroughly but cannot act on it, and there is no cross-resource text search.