SAP CPI MCP Server
Related Servers
Alternatives to SAP CPI MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceAn MCP server for SAP Cloud Integration (CPI) that exposes OData APIs as MCP tools, allowing AI assistants to manage integration content, monitor message processing, and configure security artifacts through natural language.MIT
- FlicenseNot gradedqualityBmaintenanceAn MCP server for SAP Integration Suite that enables managing integration packages, IFlows, message mappings, and TPM artifacts through natural language, with tools for creation, deployment, and monitoring.-
- AlicenseBqualityFmaintenanceEnables monitoring and management of SAP Cloud Integration (CPI) through its OData APIs, covering message processing logs, integration packages, deployment, security material, and more.44MIT
- AlicenseNot gradedqualityCmaintenanceMCP server for SAP on-premise via ADT, enabling multi-system connection, code navigation, data queries, and debugging through natural language. Includes a web admin and runtime diagnostics.MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to interact with SAP Cloud Integration (CPI) by exposing CPI APIs as MCP tools for inspecting metadata, runtime artifacts, message logs, and failed messages.3-
- AlicenseCqualityNot gradedmaintenanceAn MCP server that facilitates seamless interaction with SAP ABAP systems to manage development objects, transport requests, and source code. It provides a comprehensive suite of tools for performing syntax checks, object searches, and code modifications via the ADT API.100-
TDQS
Scored across 46 tools
Most tools have clearly distinct purposes (e.g., get_mpl_details vs. get_mpl_error_information). However, generic OData tools like cpi_query and cpi_write overlap with many specific tools, creating potential confusion about which to use.
Tool names consistently use snake_case with a verb_noun pattern (list_, get_, create_, deploy_, etc.). The cpi_ prefixed tools and where_used are minor deviations but remain readable.
46 tools is very high, exceeding the typical well-scoped range. Even for a broad domain, this count makes the set difficult to navigate and would benefit from consolidation.
The server covers the main lifecycle areas: monitoring, design-time configuration, deployment, security artifacts, and runtime data. Minor gaps exist (e.g., no dedicated update for integration packages), but the generic OData tools fill these.