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 via ADT, retrieving source code, table structures, and other development information through read-only tools.16125 npmMIT
- AlicenseCqualityDmaintenanceEnables interaction with SAP ABAP systems via ADT APIs, allowing management of ABAP objects, transport requests, and code analysis through MCP clients.10088 npmMIT
- 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-
- AlicenseNot gradedqualityAmaintenanceEnables ABAP development on SAP systems by exposing ADT APIs as MCP tools for browsing, creating, updating, and testing ABAP objects.2MIT 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-
- AlicenseBqualityCmaintenanceA lightweight MCP adapter providing unified access to SAP ABAP metadata, source code, and diagnostics through ADT services.24125 npm3MIT
TDQS
Scored across 23 tools
Most tools are clearly separated by artifact type (class, program, interface, table, etc.), and the remediation/creation tools are distinct from retrieval. However, GetStructure, GetTable, and GetTypeInfo have overlapping territory around ABAP data types, so an agent could occasionally select the wrong getter.
Tool names follow a consistent PascalCase verb-noun pattern, with Get* for retrieval and verbs like Run, Check, Find, Remediate, Create, and Release for actions. Even multi-word CDS tools follow the same convention.
23 tools is on the heavy side, largely because there are 15 Get* retrieval variants for different ABAP artifact types. The count is not unreasonable for the domain, but it exceeds the 3-15 well-scoped range.
The set covers a coherent clean-core workflow: search, retrieve source, run ATC checks, find violations, remediate, create CDS wrappers/extensions, and release them. The main gaps are general-purpose create/update/delete operations for non-CDS ABAP objects, but those appear outside the server's intended focus.