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

      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.
      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
      -
    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.4/5.0

    Scored across 47 tools

    Disambiguation4/5

    Most tools are clearly separated by resource type (queues, messages, artifacts, packages, logs, keystore, etc.), but there is some overlap between get_* and search_* variants for the same entity (e.g., get_integration_packages vs search_integration_packages, get_integration_flows vs search_integration_flows) that could cause an agent to pick the wrong one. The destructive tools are well-marked, and the get/search distinction is the main source of ambiguity.

    Naming Consistency4/5

    The naming is overwhelmingly consistent with a get_/search_/upload_/deploy_/undeploy_/update_/retry_/move_/download_ verb + noun pattern. Minor deviations exist: get_message_processing_log_runs is a plural noun phrase that could be confused with get_message_processing_logs, and get_run_steps doesn't follow the get_<resource> pattern as clearly as others. Overall, the convention is predictable.

    Tool Count3/5

    47 tools is on the heavy side, but the server covers a broad SAP CPI domain (messaging, artifacts, packages, logs, partner directory, keystore, credentials, data stores, variables, mappings, scripts, value mappings). The count is justified by the breadth, though it pushes the upper bound of what is comfortable for an agent to navigate.

    Completeness4/5

    The tool surface covers the main CPI operations: listing/searching design-time and runtime artifacts, deploying/undeploying, downloading, checking deploy status, retrieving message processing logs and run steps, managing JMS messages, and inspecting configuration/security resources. Obvious gaps include no create/update/delete for packages, no direct artifact deletion, and no ability to send/test messages, but the core monitoring and deployment workflows are well covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources