Skip to main content
Glama
ethanhan2014

sap-s4hana-odata-mcp

by ethanhan2014
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to sap-s4hana-odata-mcp

No user-submitted related servers found.

    Related Servers

    • sap-mcp-server

      Volshin
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables natural language querying of SAP business partner data by exposing OData APIs as MCP tools for LLM agents.
      -

    • S/4HANA MCP Server

      ilia-inovaflow
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables interaction with SAP S/4HANA systems, providing 38 tools to search and manage business partners, products, pricing, purchase orders, supplier invoices, service entry sheets, journal entries, and cost centers via OData V2/V4 and SOAP.
      MIT

    • sap-mcp-server

      pratri
      A
      license
      A
      quality
      C
      maintenance
      Enables local LLMs to query SAP S/4HANA OData services through typed tools for business partners, sales orders, and purchase orders, returning cleaned, compact data and allowing raw read-only access to other endpoints.
      5
      MIT

    • SAP S/4HANA MCP Server

      Nidhideep
      F
      license
      A
      quality
      D
      maintenance
      Enables interaction with SAP S/4HANA systems via OData, allowing service discovery, metadata exploration, field value retrieval, and CRUD operations through natural language.
      4
      5
      -

    • sap-cpi-mcp

      linusdevx
      A
      license
      B
      quality
      A
      maintenance
      Enables querying and managing SAP Cloud Platform Integration resources such as packages, integration flows, message processing logs, security material, and artifact lifecycle through the CPI OData v2 API.
      47
      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.7/5.0

    Scored across 2 tools

    Disambiguation5/5

    list_business_partners and get_business_partner are clearly distinct: one handles collection-level querying with filters/pagination, the other handles single-record retrieval by ID. There is no overlap or ambiguity between them.

    Naming Consistency5/5

    Both tools follow the same verb_noun convention: list/get + business_partner, with plural for the collection and singular for the individual resource. The naming is clean, predictable, and consistent.

    Tool Count3/5

    Two tools is borderline for the server's stated scope. It is sufficient for a minimal business partner lookup server, but the generic 'sap-s4hana-odata-mcp' name suggests a broader OData surface, so the tool count feels thin at the low end.

    Completeness3/5

    The tool set covers basic read/query needs for business partners via list and get, but it lacks create/update/delete operations and exposes no other S/4HANA entities. Agents needing write capabilities or non-business-partner data will hit dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources