Skip to main content
Glama
Shreesha4994

SAP BTP Cloud Foundry MCP Server

by Shreesha4994
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to SAP BTP Cloud Foundry MCP Server

No user-submitted related servers found.

    Related Servers

    • MCP Integration Suite Server

      gymishra
      F
      license
      Not graded
      quality
      B
      maintenance
      An MCP server for SAP Integration Suite that enables managing integration packages, IFlows, message mappings, and TPM artifacts through natural language, with tools for creation, deployment, and monitoring.
      -

    • sap-cloud-erp-mcp

      aytacmehmet
      A
      license
      B
      quality
      C
      maintenance
      An MCP server that provides tools to list, get, create, and update SAP S/4HANA Cloud Public Edition business objects like purchase orders, sales orders, and production orders through the Model Context Protocol.
      58
      GPL 3.0

    • 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

      stiaansdw
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server for SAP Cloud Integration (CPI) that exposes OData APIs as MCP tools, allowing AI assistants to manage integration content, monitor message processing, and configure security artifacts through natural language.
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    B3.1/5.0

    Scored across 29 tools

    Disambiguation4/5

    Tools map to distinct Cloud Foundry resources and actions, with clear singular/plural list/get pairs (cf_app/cf_apps, cf_service/cf_services). Minor overlap exists between cf_deploy_workflow and the individual cf_push/cf_bind_service/cf_restart steps, and cf_target vs cf_get_target, but descriptions distinguish them.

    Naming Consistency5/5

    All tools use a consistent cf_ snake_case prefix with predictable verb_noun or noun patterns (cf_create_service, cf_apps, cf_set_env). There are no mixed conventions or chaotic naming styles.

    Tool Count3/5

    29 tools is heavy; many lifecycle pairs (bind/unbind, set/unset, start/stop) and CRUD operations (cf_app/cf_apps, cf_service/cf_services) could be consolidated. However, the breadth of Cloud Foundry operations makes the count borderline rather than clearly excessive.

    Completeness3/5

    Core app deployment, service binding, env management, scaling, and route mapping are covered. Missing delete space/org, route listing/deletion, service keys, user/role management, and events create notable gaps for full Cloud Foundry lifecycle management.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources