Skip to main content
Glama
PauloCalazans

SAP Integration Content MCP

by PauloCalazans
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to SAP Integration Content MCP

No user-submitted related servers found.

    Related Servers

    • CI MCP Server

      lemaiwo
      A
      license
      Not graded
      quality
      F
      maintenance
      Enables AI assistants to manage SAP Cloud Integration (CPI) landscapes through natural language by exposing CPI OData APIs as MCP tools.
      12
      MIT

    • MCP Integration Suite Server

      1nbuc
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with SAP Integration Suite for designing, creating, and managing integration artifacts including integration flows, message mappings, packages, and B2B trading partner relationships through AI-powered natural language commands.
      29
      -

    • mcp-sap-cpi

      Keelside
      A
      license
      A
      quality
      D
      maintenance
      Connects Claude to SAP Cloud Platform Integration (CPI) to diagnose failed messages, review iFlows, deploy artifacts, and check credentials directly from your conversation.
      13
      6
      MIT

    • SAP OData to MCP Server

      handeocakk
      A
      license
      Not graded
      quality
      D
      maintenance
      Transforms SAP S/4HANA or ECC systems into conversational AI interfaces by exposing OData services as dynamic MCP tools. Enables natural language interactions with ERP data for querying, creating, updating, and deleting business entities.
      26 npm
      1
      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 25 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action (e.g., package vs. flow vs. runtime artifact, create vs. update vs. delete). No two tools have overlapping purposes; descriptions clearly differentiate similar operations.

    Naming Consistency4/5

    Tools predominantly follow verb_noun pattern with underscores. However, there is minor inconsistency: some use 'iflow' (e.g., execute_iflow_design_guidelines) while others use 'integration_flow' (e.g., create_integration_flow). This is a small deviation from perfect uniformity.

    Tool Count3/5

    With 25 tools, the server is on the higher end of the typical range (3-15) but still within acceptable bounds for a comprehensive integration platform. The count feels slightly heavy but not excessive.

    Completeness4/5

    The tool surface covers the full lifecycle: CRUD for packages and flows, deployment/undeployment, configuration, resource management, and design guidelines. Minor gaps exist (e.g., no tool for monitoring logs or error details), but core workflows are well-supported.

    Maintenance

    ActivityMaintained
    ResponsivenessSyncing

    Resources