Skip to main content
Glama
rameshvaranganti

sap-integration-suite-mcp

by rameshvaranganti
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to sap-integration-suite-mcp

No user-submitted related servers found.

    Related Servers

    • SAP CPI MCP Server

      premsaidaggolu
      A
      license
      B
      quality
      B
      maintenance
      MCP server for monitoring and managing SAP Cloud Integration (CPI) tenants via OData APIs, supporting multi-tenant configurations and extensive tools for message logs, integration flows, deployments, and admin operations.
      46
      MIT

    • CI MCP Server

      sapien47
      A
      license
      Not graded
      quality
      C
      maintenance
      Exposes SAP Cloud Integration OData APIs as MCP tools, letting AI assistants list, inspect, create, update, and delete integration packages, iFlows, message processing logs, message stores, log files, security artifacts, and partner directory entries through natural language. All tools are declared in a single JSON config and served by odata-mcp-proxy with OAuth2 authentication via the BTP Destination Service.
      MIT

    • 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.
      13
      MIT

    • IBP MCP Server

      BinnyRD
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants such as Claude to read SAP IBP master data and key figures through IBP's standard OData APIs on SAP BTP, with read-only access enforced.
      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 8 tools

    Disambiguation3/5

    There is noticeable overlap between get_failed_messages and get_recent_failures, as both retrieve failure data, and get_message_details versus get_error_details could cause some confusion. Descriptions help distinguish them, but the boundaries are not entirely crisp.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern (get_failed_messages, search_messages, summarize_integration_health). No mixed conventions or vague verbs are present.

    Tool Count5/5

    Eight tools is well-scoped for a diagnostic monitoring server, and each tool appears to earn its place by covering a distinct aspect of message/error/health inspection. The count avoids both thinness and bloat.

    Completeness4/5

    The surface covers core read-only diagnostic needs: searching messages, inspecting failures, retrieving details and errors, checking iflow status, summarizing health, and analyzing failures. Minor gaps exist, such as unsupported package filtering in get_failed_messages and no direct payload retrieval, but these are largely intentional or workaroundable.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources