ABAP Transport Analyzer MCP Server
Related Servers
Alternatives to ABAP Transport Analyzer MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables AI agents to read, write, activate, and transport ABAP code in SAP systems via ABAP ADT REST API, without needing SAP GUI.24551 npmMIT
- AlicenseAqualityBmaintenanceEnables AI agents to check real-time SAP object release status for ABAP Cloud and Clean Core, and find successor objects, via MCP or REST API.785 npm28MIT
- 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.3,446 npmApache 2.0
- AlicenseAqualityBmaintenanceEnables AI agents to securely read and write SAP ABAP development objects via the ADT REST API, enforcing policy-based guardrails such as package/namespace allow-lists, read-only mode, human approvals, and audit logging.82MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to work with SAP ABAP systems through the ADT REST API, supporting repository search, source code read/write, activation, syntax checks, and transport request management.1Apache 2.0
- 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
TDQS
Scored across 2 tools
The two tools are clearly distinct: one retrieves metadata (description, owner, status, objects), the other performs deep change analysis (diffs, risk factors). There is no overlap or ambiguity between them.
Both tool names follow the same verb_noun pattern: get_transport_metadata and analyze_transport_changes. The verbs are specific and consistent, making the naming predictable and readable.
With only 2 tools, the server feels slightly thin. While each tool is meaningful and covers a distinct aspect of transport analysis, the count is at the low end of what is typically expected for a tool server.
For the stated purpose of analyzing ABAP transports, the two tools cover the full workflow: retrieving metadata and performing detailed change analysis with risk detection. There are no obvious gaps for this narrow domain.