abap-mcp
Related Servers
Alternatives to abap-mcp
No user-submitted related servers found.
Related Servers
AlicenseAqualityBmaintenanceProvides AI coding agents a full abap2UI5 development loop—writing ABAP classes, validating views, deploying, and running apps headless with screenshots—all locally without an SAP system.973 npm1MIT- AlicenseBqualityCmaintenanceEnables AI coding assistants to connect directly to SAP ABAP systems via ABAP Development Tools, so they can retrieve and manage source code for programs, classes, interfaces, functions, tables, and CDS views. Also supports RAP development, running unit tests and coverage checks, inspecting transports and version history, and working across multiple SAP systems.65MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to perform ABAP Development Tools operations on SAP ERP (ECC and S/4HANA) systems, including source code editing, object activation, syntax checks, and ABAP unit tests.14 npmMIT
- AlicenseAqualityDmaintenanceEnables AI agents to read, write, activate, and transport ABAP code in SAP systems via ABAP ADT REST API, without needing SAP GUI.24576 npmMIT
- AlicenseNot gradedqualityCmaintenanceGives AI agents controlled, full-CRUD access to real ABAP repositories through ADT on SAP ECC/S/4HANA on-premise and BTP ABAP Cloud systems, so analysis and changes are grounded in system data. Supports where-used and dependency analysis, object metadata and repository navigation, transports, and iterative creation, reading, updating, and deletion of classes, interfaces, function groups/modules, programs, DDIC, and CDS/view/service artifacts.2,637 npmApache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to work a full SAP ABAP developer seat over the Model Context Protocol — searching, reading, creating, editing, activating, syntax-checking, unit-testing, transporting and debugging ABAP objects through the ADT REST surface in a target ABAP system. Runs on SAP BTP Cloud Foundry behind browser OAuth with role-gated read/write access, package allowlists and destination-held backend credentials, so no credentials reach the developer's machine.3MIT
TDQS
Scored across 5 tools
list_objects (enumerate) and outline_object (describe one object) are clearly distinct, and run_tests is unambiguous. The only real overlap is check_conventions vs lint, both static-quality checks, though the descriptions differentiate them (Clean ABAP style-guide findings vs abaplint syntax/type/naming analysis).
Four of five tools follow a predictable verb_noun snake_case pattern (list_objects, outline_object, check_conventions, run_tests). 'lint' is a bare verb that breaks the pattern slightly but is still conventional and readable.
Five tools is a lean but reasonable surface for a read-only ABAP analysis server, and each tool has a distinct role. It sits slightly on the thin side, but nothing feels redundant or missing at the count level.
The analysis workflow (discover, outline, style-check, lint, test) is well covered for a read-only server. Minor gaps remain: no way to fetch an object's raw source and no object/code search, which agents can partially work around via outline_object and lint's source argument.