Skip to main content
Glama
rohitvardhanbattula

mcp-abap-abap-adt-api

by rohitvardhanbattula
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to mcp-abap-abap-adt-api

No user-submitted related servers found.

    Related Servers

    • 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
      112 npm
      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
      384 npm
      MIT

    • 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
      -

    • sap-mcp

      vcd94xt10z
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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.
      3 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    C2.2/5.0

    Scored across 127 tools

    Disambiguation2/5

    With 127 tools covering overlapping domains like transport, debugging, ATC, and traces, many tools have unclear boundaries (e.g., hasTransportConfig vs getTransportConfiguration, codeCompletion vs codeCompletionFull, loadTypes vs objectTypes). The sheer volume makes it difficult for an agent to reliably select the correct tool.

    Naming Consistency2/5

    The naming uses a mix of verb-first (createTransport, getObjectSource, runClass), noun-first (transportInfo, objectStructure, debuggerVariables), and inconsistent prefixes (set, create, has, get, delete). There is no uniform pattern, and 'unLock' vs 'unPublishServiceBinding' and the typo 'adtCompatibiliyGraph' add to inconsistency.

    Tool Count1/5

    127 tools is far beyond the typical MCP server scope and falls into the extreme category. Even for a broad ABAP ADT API, exposing every operation without grouping or filtering creates an overwhelming surface.

    Completeness4/5

    The server covers a wide range of ABAP development workflows including object CRUD, transports, syntax checking, debugging, refactoring, ATC, tracing, and Git operations. Minor gaps exist, such as missing delete operations for transport configs or explicit object assignment to transports, but most primary workflows are supported.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources