Skip to main content
Glama
abap-adt-mcp-gateway
by lusmjs

Related Servers

Alternatives to abap-adt-mcp-gateway

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      B
      maintenance
      Lets Claude and other MCP hosts do real ABAP development on SAP systems through ADT: search objects, read and write source, transports, activation, ABAP Unit, ATC, short dumps, debugger and SQL queries. 173 tools, multi-system (S/4HANA Cloud and on-prem), with server-side guard rails and an audit log.
      2
      250 npm
      16
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Multi-system MCP server for reading and writing ABAP source via SAP ADT, with write safety controls and a local web admin.
      2
      -
    • A
      license
      C
      quality
      D
      maintenance
      An MCP server that enables seamless communication between ABAP systems and MCP clients using the ABAP Development Tools (ADT) API. It provides tools for managing ABAP objects, handling transport requests, and performing code analysis directly through MCP-compatible interfaces.
      100
      MIT
    • 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
      -

    TDQS

    A4.2/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool targets a distinct stage of the workflow: discover systems, discover tools, invoke a tool. There is no plausible way to confuse listing systems with searching the contract or calling a tool, and the descriptions reinforce the boundary (find it here, then call it with GatewayCallTool).

    Naming Consistency5/5

    All three follow the same predictable Gateway+Verb+Noun pattern (GatewayListSystems, GatewayListTools, GatewayCallTool) with identical PascalCase and prefixing. The shared 'Gateway' prefix also clearly signals these are meta-tools rather than contract tools.

    Tool Count5/5

    A gateway exposing a 336-tool contract should have a minimal meta-surface, and three tools covers discovery, invocation and context. Each tool earns its place; adding more would bloat the advertised surface and defeat the gateway's purpose.

    Completeness4/5

    The lifecycle is closed: list systems, search the contract by group/name/verb/text, then call with schema-on-mismatch error recovery. Minor gaps exist — there is no way to pre-check whether a tool is permitted on a given system without attempting the call, and no dedicated schema/introspection tool separate from the search detail flag.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues