abap-mcp
Related Servers
Alternatives to abap-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceOffline MCP server for SAP ABAP static analysis, ABAP Cloud readiness scoring, and RAP scaffolding. It enables AI agents to lint ABAP source, compare reworks, check released APIs, and generate RAP business objects without needing an SAP system.9104 npmMIT
- AlicenseAqualityAmaintenanceA local MCP server that connects to SAP ABAP systems via ADT HTTP API, enabling AI assistants to search, read, and manage ABAP objects securely without SAP GUI.5214 npm5MIT
- 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
- FlicenseBqualityNot gradedmaintenanceAn MCP server that enables AI assistants to interact with SAP systems via the ABAP Development Tools (ADT) REST API. It allows users to read ABAP source code, inspect DDIC objects, and execute SQL queries directly.66-

dassian-adtofficial
AlicenseNot gradedqualityDmaintenanceMCP server for SAP ABAP development via the ADT API. Connect AI assistants to your SAP system — read, write, test, and deploy ABAP code without SAP GUI.10MIT- 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.10070 npmMIT
TDQS
Scored across 18 tools
Each tool targets a distinct action+artifact: lint_abap vs check_rap_behavior vs check_cloud_readiness vs check_released_api are explicitly delineated, and the three scaffold_* tools (RAP BO, AI SDK, unit test) cover separate generation targets. The knowledge cluster (explain_abap_rule, list_abap_rules, explain_abap_release, search_sap_knowledge) is related but the descriptions add explicit routing rules ("for release-timeline questions prefer explain_abap_release"). Overlap is minimal and always resolved by the descriptions.
All 18 names use consistent snake_case with a verb-led prefix (compare_, fix_, explain_, list_, format_, get_, lint_, check_, plan_, scaffold_, search_). The pattern is predictable throughout — verb_abap_noun or verb_noun — with no camelCase or stylistic mixing.
18 tools is slightly on the heavy side, but each occupies a genuinely distinct slot in an offline ABAP development workflow (lint/format/fix, cloud assessment, migration planning, scaffolding, knowledge lookups). Nothing is redundant enough to remove, though the surface is broader than the typical 3-15 sweet spot.
The offline toolchain is unusually complete: static analysis, formatting, fixes, outline, cloud-readiness assessment, migration backlog, dependency graph, released-API lookup, RAP/BDEF checking, and scaffolding for BOs, AI-SDK classes and unit tests. Gaps are mostly intentional (no live SAP connection, no artifact CRUD — system access is deliberately delegated to a paired ADT MCP server), so the surface is cohesive for its stated offline scope.