Skip to main content
Glama
aytacmehmet

sap-cloud-erp-mcp

by aytacmehmet

Related Servers

Alternatives to sap-cloud-erp-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for SAP S/4HANA via the ADT API, enabling querying and reading SAP systems with production write protection.
      2 npm
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      MCP server for interacting with SAP S/4HANA OData services. It enables querying and controlled creation/update of sales orders, products, customers, and pricing conditions, with safety features like dry-run mode and ETag-based updates.
      -
    • A
      license
      C
      quality
      Not graded
      maintenance
      A Model Context Protocol server that facilitates seamless communication between ABAP systems and MCP clients for managing ABAP objects, transport requests, and code analysis. It acts as a wrapper for the ABAP ADT API to enhance the efficiency of ABAP development workflows.
      100
      -
    • A
      license
      C
      quality
      B
      maintenance
      A Model Context Protocol server that facilitates communication between ABAP systems and MCP clients, providing tools for managing ABAP objects, handling transport requests, and performing code analysis to enhance ABAP development workflows.
      100
      88 npm
      197
      MIT
    • 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

    TDQS

    B3.4/5.0

    Scored across 27 tools

    Disambiguation5/5

    Every tool targets a distinct SAP document/resource and action, such as sales orders, purchase orders, sales contracts, or production orders. The get/list/create/update/release verbs are applied consistently, so there is little risk of selecting the wrong tool.

    Naming Consistency5/5

    Tool names follow a strict s4_<resource>_<action> pattern with snake_case throughout. Actions are consistently list/get/create/update/release, making the API surface highly predictable.

    Tool Count3/5

    27 tools is on the heavy side, but the server covers multiple ERP domains: sales, purchasing, manufacturing, and logistics. Each tool is distinct and purposeful, though the count is above the ideal range for a tightly scoped server.

    Completeness2/5

    Several document lifecycles are incomplete: there is no purchase order list, no sales quotation create, no production order create, and no outbound delivery list. These are significant gaps that would block common ERP workflows, even though core sales order and purchase order operations are covered.

    Maintenance

    ActivitySlowing
    ResponsivenessSyncing