SAP MCP Server – lokale Variante
Related Servers
Alternatives to SAP MCP Server – lokale Variante
No user-submitted related servers found.
Related Servers
- FlicenseAqualityCmaintenanceEnables MCP clients to connect to SAP S/4HANA on-premise systems, providing developer-grade read and write access to ABAP source, DDIC objects, table data, syntax/ATC checks, debugging, and transport management.51-
- 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.5459 npm8MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to securely connect with SAP ABAP and BTP services, allowing execution of function modules, BAPIs, table reads, and various BTP operations through MCP.1Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to securely access and query SAP BTP OData backends via MCP, with XSUAA authentication and principal propagation.31 npmISC
- AlicenseBqualityDmaintenanceA lightweight MCP adapter providing unified access to SAP ABAP metadata, source code, and diagnostics through ADT services.24226 npm3MIT
- AlicenseAqualityBmaintenanceEnables MCP clients to connect to SAP ABAP systems and retrieve development information such as source code and table structures.23226 npmMIT
TDQS
Scored across 19 tools
Several tools have near-identical purposes: smart-data-analysis, business-process-insights, business-intelligence-insights, and predictive-analytics-engine all claim to analyze SAP data and produce insights, and kpi-dashboard-builder overlaps heavily with ui-dashboard-composer (both create KPI dashboards). The query-routing tools (sap-smart-query, natural-query-builder, search-sap-services) also blur together, and the UI builders (ui-report-builder, ui-data-grid, ui-form-generator, ui-workflow-builder) are hard to distinguish without reading full descriptions.
Naming mixes verb_noun patterns (search-sap-services, get-entity-schema, execute-entity-operation) with noun-phrase tool names ending in -builder, -engine, -insights, and -stream (ui-report-builder, predictive-analytics-engine, business-intelligence-insights, realtime-data-stream). A few names even embed a different prefix convention (sap-smart-query) while others use natural-query-builder, so no single predictable pattern exists.
At 19 tools the set is heavy for a server whose real job is SAP OData discovery and CRUD, and much of that count comes from redundant analytics/insight and UI-building tools that duplicate each other's function. Trimming the overlapping insight and dashboard tools would leave a tighter, more usable surface.
The core OData lifecycle is reasonably covered (search services, discover entities, get schema, execute CRUD operations, plus authentication). However, gaps remain around batch/transaction operations, explicit session lifecycle/logout, and error or metadata diagnostics, while the analytics half of the surface is padded with overlapping tools rather than filling those gaps.