ABAP-ADT-API MCP-Server
Related Servers
Alternatives to ABAP-ADT-API MCP-Server
No user-submitted related servers found.
Related Servers
- AlicenseCqualityNot gradedmaintenanceA Model Context Protocol server that facilitates seamless communication between ABAP systems and MCP clients for managing ABAP objects, transport requests, and code analysis. It acts as a wrapper for the ABAP ADT API to enhance the efficiency of ABAP development workflows.100-
- 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
- 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-
- AlicenseBqualityAmaintenanceA server that bridges the Model Context Protocol (MCP) with SAP ABAP systems, allowing tools like Cline to retrieve ABAP source code, table structures, and other development artifacts.1381186MIT
- 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
- AlicenseNot gradedqualityDmaintenanceA standalone MCP server for SAP ABAP development and customizing that connects directly to your SAP system via ADT REST API, enabling AI assistants to search, read, write, activate, transport, debug, and run quality checks on ABAP code, as well as manage customizing/IMG configurations with governed transport recording.MIT
TDQS
Scored across 127 tools
Most tools have distinct purposes, but some overlap exists, such as multiple debugger tools (e.g., debuggerSetBreakpoints, debuggerDeleteBreakpoints) and Git operations (e.g., gitPullRepo, pushRepo) that could be consolidated. However, descriptions generally clarify their specific functions, reducing confusion.
Naming conventions are mixed, with tools using camelCase (e.g., abapDocumentation), snake_case (e.g., create_transport), and inconsistent verb styles (e.g., activateByName vs. createObject). While readable, the lack of a uniform pattern detracts from predictability.
With 127 tools, the count is excessive for an MCP server, making it overwhelming and difficult to navigate. This many tools suggests poor scoping, as many functions could be grouped or omitted without losing core functionality.
The tool set comprehensively covers ABAP development and system management, including object lifecycle (create, activate, delete), debugging, testing, Git integration, and transport management. No obvious gaps are present for the domain.