Skip to main content
Glama
ABRANJAN07

BTP MCP Server

by ABRANJAN07
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
BTP_SM_URLYesService Manager URL from Service Manager service key
BTP_CLIENT_IDYesClient ID from Service Manager service key
BTP_TOKEN_URLYesOAuth2 token URL from Service Manager service key
BTP_CLIENT_SECRETYesClient secret from Service Manager service key
BTP_SUBACCOUNT_IDYesSubaccount GUID from BTP Cockpit
CACHE_TTL_SECONDSNoOptional cache TTL in seconds300
BTP_DESTINATION_URLYesDestination service URL (region-specific)

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
{
  "listChanged": true
}
logging
{}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
extensions
{
  "io.modelcontextprotocol/ui": {}
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_btp_servicesA

Lists all SAP BTP services available in the global service catalog.

These are services that EXIST in BTP — not necessarily what your subaccount is running. Use list_btp_instances to see what is actually provisioned and running.

Optionally filter by keyword (searches name, description, and tags).

Examples of when to use this tool:

  • "What BTP services are available?"

  • "Is there an AI service in BTP?"

  • "Show me all messaging services"

  • "Does BTP have a workflow service?"

get_btp_service_plansA

Returns all available plans for a specific BTP service.

Plans differ in capacity, features, and cost. Some have a free tier. Use this to understand what options exist before creating an instance.

list_btp_instancesA

Lists all service instances currently provisioned in your BTP subaccount.

An instance is one running copy of a BTP service that you created. Shows the current state: SUCCEEDED (healthy), FAILED, or IN_PROGRESS.

Examples of when to use this tool:

  • "What service instances do I have running?"

  • "Is HANA Cloud already set up in my account?"

  • "Are there any failed instances?"

  • "What's the ID of my Destination service instance?"

get_btp_destinationsA

Lists all destinations configured in your BTP subaccount.

A destination is a saved connection to an external system. Instead of hardcoding URLs in your code, you define a named destination in BTP and reference it by name.

Filter options: proxy_type: "OnPremise" (via Cloud Connector) or "Internet" (cloud) auth_type: e.g. "OAuth2ClientCredentials", "BasicAuthentication"

Examples of when to use this tool:

  • "What destinations are configured in BTP?"

  • "Is there a destination for our S/4HANA system?"

  • "Show me all on-premise destinations"

  • "What authentication does the ERP destination use?"

recommend_btp_serviceA

Recommends the right BTP service(s) for a described use case. Also checks whether the recommended services are already running as instances in your subaccount.

Note: Entitlement checking is temporarily disabled. The 'is_entitled' field always shows null until re-enabled.

Examples of when to use this tool:

  • "What BTP service should I use for async messaging?"

  • "I need to store files in BTP — what service do I use?"

  • "How do I call an LLM from my CAP app?"

  • "What service handles OAuth2 auth in BTP?"

  • "I need to connect to an on-premise SAP system"

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

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

A4.2/5.0

Scored across 5 tools

Disambiguation5/5

Each tool targets a distinct aspect of BTP: destinations, service plans, instances, services catalog, and recommendations. No overlaps cause confusion.

Naming Consistency5/5

All tools follow the consistent 'verb_btp_noun' pattern, using snake_case with clear verbs (get, list, recommend).

Tool Count5/5

With 5 tools, the set is well-scoped for BTP subaccount management—neither sparse nor excessive.

Completeness3/5

Covers discovery and recommendations well but lacks CRUD operations for instances, destinations, or entitlements, leaving notable gaps.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources