Skip to main content
Glama
appmaster3000

sap-abap-mcp-server

by appmaster3000
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

Related Servers

Alternatives to sap-abap-mcp-server

No user-submitted related servers found.

    Related Servers

    • dassian-adt

      jaybinler
      A
      license
      Not graded
      quality
      C
      maintenance
      Connects AI assistants to SAP systems through the ABAP Development Tools API, exposing 85 tools that cover the full ABAP development lifecycle — reading and writing source, creating and activating objects, managing transports, running syntax/ATC checks and unit tests, querying tables, refactoring, remote debugging, tracing, and executing code — all without SAP GUI. Supports single- or multi-system landscapes with credentials supplied by the MCP client at launch.
      MIT

    • abap-config-mcp

      OCA-BE
      A
      license
      Not graded
      quality
      D
      maintenance
      A 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

    • ABAP-ADT-API MCP-Server

      dachienit
      A
      license
      C
      quality
      Not graded
      maintenance
      An MCP server that facilitates seamless interaction with SAP ABAP systems to manage development objects, transport requests, and source code. It provides a comprehensive suite of tools for performing syntax checks, object searches, and code modifications via the ADT API.
      100
      -
    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

    A3.9/5.0

    Scored across 51 tools

    Disambiguation4/5

    Most tools map cleanly to a specific resource or lifecycle step, and the debug, transport, DDIC, and repository tools are clearly separated. A few pairs overlap in intent—sap_connection_test/sap_rfc_ping, sap_read_table/sap_sql_query, sap_rfc_call/sap_bapi_call—but detailed descriptions and explicit cross-references keep misselection unlikely.

    Naming Consistency4/5

    All tools share the sAP_ prefix and most follow an action_noun pattern such as sap_get_source, sap_create_transport, or sap_debug_step. Read operations vary among get/list/read/search/browse, and a few names like sap_where_used, sap_connection_test, and sap_abap_docs break the dominant pattern, preventing a perfect score.

    Tool Count1/5

    51 tools is an extreme surface for a single MCP server and imposes a heavy tool-selection burden on an agent. The broad ABAP domain supports many capabilities, but the debugger, RFC/BAPI, monitoring, and repository subdomains could reasonably be split into more focused servers.

    Completeness4/5

    The core ABAP development lifecycle is thoroughly covered: repository search/read/create/write/activate/delete, transports, syntax/unit/ATC checks, DDIC and table access, a full debugger lifecycle, RFC/BAPI calls, jobs, dumps, and documentation. Notable gaps such as passing selection-screen parameters to reports or directly creating function modules are documented limitations with workarounds rather than dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources