Skip to main content
Glama
linusdevx

sap-cpi-mcp

by linusdevx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to sap-cpi-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-cpi

      jmatiasschneider
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables operating an SAP Integration Suite Cloud Integration tenant from Claude Code, with tools to read packages, iFlows, and logs, and to create, clone, configure, validate, and deploy artifacts, as well as invoke iFlows and inspect step payloads.
      1
      -

    • 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
    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 47 tools

    Disambiguation3/5

    Many tools come in get/search pairs that are distinct but easy to confuse, and several resource groups (JMS brokers vs JMS resources vs messaging queues; keystore entries vs certificate resources vs credentials) overlap conceptually. The descriptions clarify most boundaries, but with 47 tools an agent could easily select the wrong variant.

    Naming Consistency4/5

    Tool names mostly follow a consistent snake_case verb_noun pattern (get_, search_, upload_, deploy_, update_, etc.). There are minor deviations such as get_run_steps vs get_message_processing_log_runs, and get_ vs search_ both being used for list/fetch operations, but overall the convention is predictable.

    Tool Count2/5

    47 tools is a heavy surface for an MCP server. While the domain is broad, many tools are simple get/search variants of similar entity types, and the count exceeds what most agents need in a single namespace, increasing selection and prompt-overhead risk.

    Completeness4/5

    The server covers a broad lifecycle: design-time artifact listing/search/download/upload/deploy/undeploy, runtime monitoring, MPLs, traces, logs, Partner Directory, keystore/credentials, data stores, variables, and JMS messaging. Missing create/update/delete for many entity types (packages, mappings, scripts) feels like a gap, but those are likely read-only OData surfaces, and the core operation workflows are not dead-ended.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources