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
- AlicenseBqualityCmaintenanceMCP 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.10090MIT
- 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 gradedqualityAmaintenanceEnables ABAP development on SAP systems by exposing ADT APIs as MCP tools for browsing, creating, updating, and testing ABAP objects.2MIT No Attribution
- AlicenseNot gradedqualityBmaintenanceMCP server for SAP ABAP development, enabling AI assistants to read, create, update, and delete ABAP objects via ADT APIs.MIT
TDQS
Scored across 193 tools
Tools are generally distinct by object type (class, interface, table, etc.) but there are several confusing overlaps: GetObjectVersions vs GetClassVersions, GetUnitTest vs GetUnitTestStatus vs GetUnitTestResult, and RunUnitTest vs CreateUnitTest are nearly identical. The low-level tools (GetObjectStructureLow, GetNodeStructureLow) add ambiguity despite descriptions.
Most tools follow a clear Get/Create/Update/Delete/Activate/Check + object pattern, but there are deviations like ListTransports, ReadFunctionInclude, DescribeByList, and GetSqlQuery. Also a mix of List and Get for similar operations, and some low-level suffixes (Low) break the pattern.
193 tools is extremely excessive for any MCP server, even a comprehensive ABAP development tool. Many tools are redundant (e.g., GetObjectVersions alongside type-specific version tools, multiple unit test status tools), and the surface could be reduced to ~50 tools without losing functionality.
The tool set covers the full lifecycle of ABAP development objects: create/read/update/delete for most types, plus activation, syntax checks, version history, diffs, unit testing, and runtime profiling. Minor gaps include missing update/delete for packages and some service definition operations, but the coverage is generally strong.