Skip to main content
Glama
Hollway

mcp-abap-abap-adt-api

by Hollway
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to mcp-abap-abap-adt-api

No user-submitted related servers found.

    Related Servers

    • ADT MCP Server

      YahorNovik
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with SAP ABAP systems through ABAP Development Tools (ADT), providing access to repository objects, source code, where-used analysis, and SQL queries with support for both on-premise and BTP systems.
      3
      -

    • MCP-ADT

      rafaelssclaudio
      A
      license
      C
      quality
      C
      maintenance
      Facilitates interaction with SAP ABAP systems via ADT APIs, enabling object management, transport handling, and code analysis.
      100
      72
      MIT

    • sap-adt-mcp

      engoetz
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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.
      Apache 2.0

    • abap-adt-mcp

      abap0917
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to read, write, activate, and transport ABAP code in SAP systems via ABAP ADT REST API, without needing SAP GUI.
      24
      611
      MIT
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 177 tools

    Disambiguation3/5

    Many tools have clearly distinct purposes, and the descriptions are thorough. However, there are redundant tools like unitTestRun vs runTests and activateByName vs activateSafe vs activateObjects, which overlap in function and require reading descriptions to choose correctly. With 177 tools, some clusters (source read/edit, debugger, ATC) risk confusion despite good documentation.

    Naming Consistency4/5

    The vast majority follow a consistent camelCase convention with verbs first (getObjectSource, setTextElements, activateSafe). Minor deviations exist: noun-based tools like revisions, dumps, systemUsers, and inconsistent prefixes (hasTransportConfig vs transportConfigurations vs getTransportConfiguration) create slight irregularity, but the overall pattern is predictable.

    Tool Count1/5

    At 177 tools, the count is far beyond the 25+ threshold and even the 50+ extreme-mismatch line. While the ADT API is broad, the sheer number makes the server unwieldy for an agent to navigate, and many tools could be consolidated (e.g., multiple debugger step/attach tools, several ATC worklist variants).

    Completeness5/5

    The surface covers nearly every ADT domain: source CRUD, DDIC (domains, data elements, structures, tables), transports, git, debugging, ATC, traces, refactoring, function modules, unit tests, and data querying. Lifecycle operations are present for most object types, with activation verification and rollback awareness. No obvious critical gaps for the stated purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources