mcp-abap-adt
Related Servers
Alternatives to mcp-abap-adt
No user-submitted related servers found.
Related Servers
- 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-
- MIT
- 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.100MIT
- AlicenseCqualityDmaintenanceAn MCP server that enables seamless communication between ABAP systems and MCP clients using the ABAP Development Tools (ADT) API. It provides tools for managing ABAP objects, handling transport requests, and performing code analysis directly through MCP-compatible interfaces.100MIT
- AlicenseNot gradedqualityCmaintenanceEnables ABAP development on SAP systems by exposing ADT APIs as MCP tools for browsing, creating, updating, and testing ABAP objects.2MIT No Attribution
- AlicenseNot gradedqualityDmaintenanceMCP server for SAP ABAP development, enabling AI assistants to read, create, update, and delete ABAP objects via ADT APIs.MIT
TDQS
Scored across 256 tools
The per-type tool families (Get/Create/Update/Delete/Check/ActivateClass, -Program, -Table, etc.) are individually clear, but they overlap heavily with generic tools: GetObjectVersions/GetObjectVersionSource/GetObjectVersionDiff duplicate GetClassVersions/GetTableVersions/etc., and ActivateObjects duplicates every Activate* tool. Similarly GetObjectInfo, GetObjectsList, GetObjectsByType, GetPackageTree, GetPackageContents and GetObjectStructure all walk object trees, so an agent must guess which to call.
The surface follows a strong Verb+Noun CamelCase convention (GetX, CreateX, UpdateX, DeleteX, CheckX, ActivateX, RunX) repeated consistently across all object types. A few outliers invert the order or deviate (MemorySnapshotList/Get/Delta, AmdpDebugStart, DescribeByList), keeping it from a perfect score.
256 tools is an extreme mismatch for a single server: the per-type CRUD/check/activate/version quadrants multiply the surface far beyond what an agent can reliably select from. Many tools are near-duplicates of generic ones (version source/diff per type vs. the object-generic versions), so the count is inflated rather than earned.
Coverage of the ADT domain is extremely broad: CRUD, activation, syntax checks, version history/diff, transports, ATC, ABAP Unit, runtime/profiler, SQL preview and a full debugger surface are all present. Some object types are read-only (enhancements, transactions) and a few check/generic operations are missing per type, but the core lifecycle is covered.