Skip to main content
Glama
Coaspe

sap-abap-mcp

by Coaspe
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to sap-abap-mcp

No user-submitted related servers found.

    Related Servers

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

    • abap-mcp-adt

      ChinhHN-DEV
      A
      license
      B
      quality
      C
      maintenance
      MCP server for SAP ABAP development that enables AI assistants and code editors to interact with SAP systems via ABAP Developer Toolkit (ADT) APIs, supporting read, create, update, and delete of ABAP objects.
      100
      90 npm
      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-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
    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.6/5.0

    Scored across 5 tools

    Disambiguation4/5

    Each tool occupies a distinct phase: discovery (search), introspection (describe), and execution split by risk class (read/write/destructive). The three invoke tools share a description template and differ only by side-effect profile, so an agent could occasionally confuse write vs destructive if capability metadata is unclear.

    Naming Consistency5/5

    All tool names use the same sap.capability.<action> dot-delimited convention, with snake_case for multiword actions. The pattern is predictable and consistent throughout.

    Tool Count5/5

    Five tools are well-scoped for a capability broker: one search, one describe, and three execution variants by risk category. No tool feels redundant or missing.

    Completeness5/5

    The surface covers discovery, schema introspection, and invocation for read, write, and destructive operations, which is full lifecycle for a capability gateway. No obvious capability-broker operation is absent.

    Maintenance

    ActivityActive
    ResponsivenessWithin a week

    Resources