Skip to main content
Glama
JayGandhi285

sap-abap-mcp

by JayGandhi285
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to sap-abap-mcp

No user-submitted related servers found.

    Related Servers

    • abap-mcp

      joaodelapace
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that connects AI assistants to SAP systems via the ADT REST API, enabling read, write, syntax-check, and activation of ABAP code directly from the chat.
      3
      MIT

    • SAP ADT MCP Server

      ethanhan2014
      F
      license
      B
      quality
      Not graded
      maintenance
      An 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
      -

    • sap-abap-mcp

      Coaspe
      A
      license
      A
      quality
      A
      maintenance
      A 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.
      5
      214 npm
      5
      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

    B3.2/5.0

    Scored across 7 tools

    Disambiguation2/5

    Several tools have fuzzy boundaries: sap_se16_browse and sap_rfc_read_table both read table data, while sap_navigate, sap_execute_command, and sap_get_page all retrieve rendered SAP pages and can be used to reach transactions. An agent would need to read descriptions very carefully to reliably pick the right tool.

    Naming Consistency3/5

    All tools share a sap_ prefix and snake_case style, which helps, but the internal pattern is inconsistent: sap_navigate is a bare verb, sap_se16_browse leads with a transaction code, and sap_rfc_read_table mixes technical context with the action. It is readable but not a uniform verb_noun convention.

    Tool Count4/5

    Seven tools is a reasonable size for an SAP interaction server and not bloated overall. However, the set could be tightened because some tools are near-duplicates in functionality, such as the two table-reading paths and the multiple page-fetching mechanisms.

    Completeness3/5

    Core workflows like login, navigation, table reads, and running reports are covered, but there is no logout or explicit session-management tool, and report output is only exposed as raw page text. Agents can work around some gaps via execute_command or get_page, but the surface is not fully lifecycle-complete.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources