Step-by-Step Guide To Connecting The MCP Server For SAP BTP Administration

Introduction

SAP Business Technology Platform (BTP) has long required administrators to juggle the BTP Cockpit, the btp CLI, and various service-specific dashboards to manage their cloud landscape. Whether creating subaccounts, assigning entitlements, configuring trust, or setting up connectivity, the operational overhead is real.

The MCP Server for SAP BTP Administration changes that equation. It exposes BTP account administration operations as tools that any compatible AI assistant can discover and invoke on your behalf — replacing repetitive GUI navigation and CLI scripting with plain natural language.

The MCP Server for SAP BTP Administration

SAP has introduced a dedicated MCP Server for SAP BTP Administration that aggregates four key administration domains behind a single endpoint:

Domain	What You Can Do
Accounts	Manage global account structure, create and configure subaccounts and directories, view account hierarchy
Security	Manage users, role collections, trust configurations, and authorizations at the global account and subaccount level
Services	Manage entitlements and quotas, subscribe to applications, configure service plans
Connectivity	Set up destinations, manage Cloud Connector tunnels, configure backend connectivity

You do not need to configure individual operations. The AI assistant dynamically discovers the available tools and determines which ones to call based on your natural language request.

Example prompts you can use:

“Create a new subaccount in the EU10 region for our development team.”
“Show me which services are currently entitled in our production subaccount.”
“Assign the Viewer role collection to user john.doe@company.com in subaccount Prod.”
“List all role collections that have critical warning indicators.”

Compatible AI Clients

Any AI client that supports the MCP standard can connect to the MCP Server for SAP BTP Administration. SAP officially lists the following compatible clients:

Claude Code — Anthropic's agentic coding and task-execution assistant
GitHub Copilot in VS Code — Microsoft's AI pair programmer, now with MCP tool support
OpenCode — An open-source, terminal-based AI coding agent

The standard MCP transport (HTTP/SSE or stdio) means the ecosystem will continue to grow as more clients adopt the protocol.

The MCP Server for SAP BTP Administration is available at the following endpoint:

Authentication modeURL

Single Sign-On	https://sso.mcp.btp.cloud.sap/mcp
Direct Connection	https://proxy.c-769d49e.kyma.ondemand.com/mcp

For SSO, you must also provide the OAuth client ID when registering the server: e789ba01-5612-47ee-bfe7-79e26411c1ca

Caution

The MCP Server operates with the full scope of your SAP user identity. If your trial account is registered under the same email address as your productive accounts, the server will have access to all global accounts associated with that identity. To restrict access to a trial account only, register it under a separate email address.

Follow the instructions for your AI client.

Claude Code Single Sign-On

Open a terminal and run the following command:

claude mcp add –transport http BTP-Administration \

  “https://sso.mcp.btp.cloud.sap/mcp” \

  –client-id e789ba01-5612-47ee-bfe7-79e26411c1ca

You only need to run this command once. The server remains registered across sessions.

Start Claude Code: claude
Type /mcp at the prompt and select the server you registered.
Complete the SAP login in the browser that opens, then return to your terminal.

Claude Code Direct Connection

Compute the Base64 encoding of your credentials in the format <username>:<password> and set it as an environment variable along with your IAS tenant subdomain.

macOS and Linux:

export BTP_CREDENTIALS=$(echo -n “<your-username>:<your-password>” | base64)

export BTP_ORIGIN=“<your-ias-tenant-subdomain>”

Windows (PowerShell):

$Env:BTP_CREDENTIALS = [Convert]::ToBase64String([Text.Encoding]::UTF8.GetBytes(‘<your-username>:<your-password>'))

$Env:BTP_ORIGIN = ‘<your-ias-tenant-subdomain>'

claude mcp add –transport http BTP-Administration \

  “https://proxy.c-769d49e.kyma.ondemand.com/mcp” \

  –header ‘Authorization: Basic ${BTP_CREDENTIALS}' \

  –header ‘X-Platform-Origin: ${BTP_ORIGIN}'

Start Claude Code: claude

Github Copilot in VS Code Single Sign-On

Open or create .vscode/mcp.json in your project and add the following entry:

{

  “mcpServers”: {

    “BTP Administration”: {

      “type”: “streamableHttp”,

      “url”: “https://sso.mcp.btp.cloud.sap/mcp”

    }

  }

}

When VS Code prompts for the OAuth client ID, enter e789ba01-5612-47ee-bfe7-79e26411c1ca. VS Code stores this value and will not ask again.
Complete the SAP login in the browser that opens, then return to VS Code.

Github Copilot in VS Code Direct Connection

Before configuring VS Code, compute the Base64 encoding of your credentials in the format <username>:<password>.
macOS and Linux:
```
echo -n “<your-username>:<your-password>” | base64
```
Windows (PowerShell):
```
[Convert]::ToBase64String([Text.Encoding]::UTF8.GetBytes(‘<your-username>:<your-password>'))
```
Copy the output — you will enter it in the next step.

Open or create .vscode/mcp.json and add the following. VS Code prompts for credentials once per session and does not store them on disk.

{

  “inputs”: [

    {

      “id”: “btp-credentials”,

      “type”: “promptString”,

      “description”: “Base64-encoded BTP credentials (<username>:<password>)”,

      “password”: true

    },

    {

      “id”: “btp-origin”,

      “type”: “promptString”,

      “description”: “IAS tenant subdomain”

    }

  ],

  “mcpServers”: {

    “BTP Administration”: {

      “type”: “streamableHttp”,

      “url”: “https://proxy.c-769d49e.kyma.ondemand.com/mcp”,

      “headers”: {

        “Authorization”: “Basic ${input:btp-credentials}“,

        “X-Platform-Origin”: “${input:btp-origin}“

      }

    }

  }

}

OpenCode Single Sign-On

Open your opencode.json configuration file and add the following entry under the mcp key:

{

  “mcp”: {

    “BTP Administration”: {

      “type”: “remote”,

      “url”: “https://sso.mcp.btp.cloud.sap/mcp”,

      “oauth”: {

        “clientId”: “e789ba01-5612-47ee-bfe7-79e26411c1ca”

      }

    }

  }

}

Start OpenCode. Complete the SAP login in the browser that opens, then return to OpenCode.

OpenCode Direct Connection

Compute the Base64 encoding of your credentials in the format <username>:<password> and set it as an environment variable along with your IAS tenant subdomain.

macOS and Linux:

export BTP_CREDENTIALS=$(echo -n “<your-username>:<your-password>” | base64)

export BTP_ORIGIN=“<your-ias-tenant-subdomain>”

Windows (PowerShell):

$Env:BTP_CREDENTIALS = [Convert]::ToBase64String([Text.Encoding]::UTF8.GetBytes(‘<your-username>:<your-password>'))

$Env:BTP_ORIGIN = ‘<your-ias-tenant-subdomain>'

Add the following to your opencode.json:

{

  “mcp”: {

    “BTP Administration”: {

      “type”: “remote”,

      “url”: “https://proxy.c-769d49e.kyma.ondemand.com/mcp”,

      “headers”: {

        “Authorization”: “Basic {env:BTP_CREDENTIALS}”,

        “X-Platform-Origin”: “{env:BTP_ORIGIN}”

      }

    }

  }

}

9998212163412465-Df168527-0Aa0-42Db-A12E-E8F746Ab83D6-Image_Task_01M11Ntqgck02W6Q0A843Cpbfh_0.Png

Above Image Sources : Image prompt used & generated from SAP AI Core Model Gemini 3.5 Flash

Report any Issues for BTP MCP

If the steps above do not resolve your issue, create a support request using SAP component BC-CP-ADMINMCP. See Getting Support to know more.

Source link