calmcp
Related Servers
Alternatives to calmcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceA 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.112 npm32MIT
- AlicenseNot gradedqualityAmaintenanceMCP server for SAP Cloud ALM, providing 54 tools across 9 services to manage features, tasks, test cases, documents, projects, and more via natural language.865 npm5GPL 3.0
- AlicenseAqualityAmaintenanceA 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.5266 npm5MIT
- 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.100163 npmMIT
- 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_get (single entity), calm_list (collection query), and calm_analytics (tenant-wide aggregates) have broadly distinct roles, and calm_resources is a clear discovery helper. However, calm_list and calm_analytics overlap meaningfully — both expose count_only and group_by and both can count records — so an agent could reasonably pick either for a counting task.
All four tools share a consistent 'calm_' prefix, which gives a predictable family feel. The suffixes mix verb-style (get, list) with noun-style (analytics, resources), so it is not a strict verb_noun pattern, but it remains readable and predictable.
Four generic meta-tools efficiently cover a very broad SAP Cloud ALM surface (tasks, projects, defects, test cases, etc.) by parameterizing resources. It leans slightly thin — only one tool handles the discovery/catalog role — but each tool earns its place.
For a query/read-oriented surface, coverage looks strong: single fetch, collection listing with full OData params, tenant-wide analytics, and a resource/code-list discovery helper with recipes. The main gap is the absence of any mutation operations (create/update/delete), which is likely intentional but limits lifecycle coverage.