Skip to main content
Glama
Shreesha4994

SAP BTP Cloud Foundry MCP Server

by Shreesha4994

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
CF_ORGNoThe default organization (optional - can be specified in tool calls)
CF_SPACENoThe default space (optional - can be specified in tool calls)
CF_PASSWORDYesYour SAP BTP password
CF_USERNAMEYesYour SAP BTP username
CF_API_ENDPOINTYesThe Cloud Foundry API endpoint (e.g., https://api.cf.us10.hana.ondemand.com)

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
cf_loginB

Authenticate with Cloud Foundry using provided credentials. Use environment variables if no parameters provided.

cf_targetC

Switch to a different organization and/or space

cf_get_targetA

Get current Cloud Foundry target information (API endpoint, org, space, user)

cf_pushC

Deploy (push) an application to Cloud Foundry

cf_appB

Get detailed information about a specific application

cf_appsB

List all applications in the current space

cf_startB

Start a stopped application

cf_stopC

Stop a running application

cf_restartC

Restart an application

cf_restageC

Restage an application (re-run staging without changing code)

cf_scaleC

Scale an application (instances, memory, disk)

cf_delete_appC

Delete an application

cf_logsC

Get application logs

cf_set_envC

Set an environment variable for an application

cf_unset_envC

Unset an environment variable for an application

cf_get_envB

Get all environment variables for an application

cf_create_serviceC

Create a service instance

cf_delete_serviceB

Delete a service instance

cf_bind_serviceC

Bind a service instance to an application

cf_unbind_serviceC

Unbind a service instance from an application

cf_servicesA

List all service instances in the current space

cf_serviceC

Get detailed information about a service instance

cf_marketplaceC

List available services in the marketplace

cf_orgsB

List all organizations

cf_spacesB

List all spaces in the current organization

cf_create_spaceC

Create a new space

cf_map_routeC

Map a route to an application

cf_unmap_routeC

Unmap a route from an application

cf_deploy_workflowB

Complete deployment workflow: push app, bind services, and restart

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

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