mcp-abap-adt
Related Servers
Alternatives to mcp-abap-adt
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables MCP clients to connect to SAP ABAP systems and retrieve development information such as source code and table structures.23277 npmMIT
- AlicenseCqualityDmaintenanceEnables interaction with SAP ABAP systems via ADT APIs, allowing management of ABAP objects, transport requests, and code analysis through MCP clients.100211 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables DeepSeek Harness to connect to SAP ABAP systems via ADT, providing read-only access to ABAP objects, source code, and data, with optional write capabilities controlled by explicit permissions.18 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables ABAP development on SAP systems by exposing ADT APIs as MCP tools for browsing, creating, updating, and testing ABAP objects.34 PyPI2MIT No Attribution
- 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-
- FlicenseNot gradedqualityCmaintenanceConnects to SAP ABAP Development Tools (ADT) via MCP, enabling AI assistants to manage SAP systems through natural language.-
TDQS
Scored across 16 tools
Most tools map clearly to a distinct ABAP object type, and SearchObject is distinct from the Get* retrievers. Mild ambiguity exists among GetStructure, GetTable, and GetTypeInfo, since structure and table type information can overlap conceptually.
All tools follow a consistent VerbObject pattern using capital camelCase (GetFunction, GetClass, SearchObject). The naming is uniform and predictable across the entire set.
Sixteen tools is slightly above the typical 3-15 sweet spot, but ABAP has many distinct object types and each tool targets a specific object, so none feel redundant. The count is reasonable for a read-only ABAP repository browser.
The server provides broad read coverage across source objects, metadata, table contents, and search. The obvious limitation is that it is entirely read-only with no create/update/activate tools, which would be a significant gap if the intended domain is full ABAP ADT development rather than source retrieval.