cpi-mcp-server
A Go server over Cloud Integration's design-time content — integration packages and integration flows, listed and searched by id, version, name, vendor or mode.
Scoped to what a tenant contains rather than to what it is doing. get_integration_packages and get_integration_flows enumerate; search_integration_packages and search_integration_flows narrow by id, version, name, vendor or mode. That is the design-time half of Cloud Integration, which is the half you need when the question is what exists and where a flow came from rather than what failed last night.
Facts
Where it sits
Who is behind it
In the atlas: maintains 1, contributes to 1, wrote 1@vadimklimovmaintainer
Before choosing this
Conditions
PracticalFunctional boundary
Design-time only: no message monitoring, no deployment, no runtime status. That is a different server in this same section, and the two do not overlap.
PolicySAP API Policy 4.2026a§ 1.1, 1.2, 2.2.2from Agent access to your systemsAn MCP server uses SAP APIs to supply tools, resources or data to an agent.
- § 1.1 Published APIs. Published APIs are made available for the documented purposes identified by SAP, including integration, extensions and data exchange.
- § 1.2 Non-Published APIs. Customer and third-party applications must not access non-published APIs except where documentation permits it or SAP otherwise authorizes it.
- § 2.2.2 AI call sequences and data extraction. Outside SAP-endorsed architectures, data services or expressly identified pathways, the policy prohibits specified agentic API use and systematic or large-scale extraction.
MCP does not replace the API's documented-use boundary. Check that every endpoint is published for the intended use and whether the policy's AI-call or extraction provisions apply to the design.
SAP API Policy 4.2026a →What it declares
Every artifact
- Type
- MCP server
- Origin
- Independently maintained
As an MCP server
- Language
- Go
Connections
Giving an AI agent access to the systems you run over MCP
Download
README
quoted from vadimklimov/cpi-mcp-server under MIT, readMCP server for SAP Cloud Integration
The MCP server for SAP Cloud Integration provides AI-powered applications with access to integration packages and integration artifacts within an SAP Cloud Integration (a part of SAP Integration Suite) tenant.
Tools
The MCP server exposes the following tools:
| Tool | Description |
|---|---|
| get_integration_packages | Get all integration packages |
| search_integration_packages | Search integration packages by ID, version, name, vendor or mode |
| get_integration_flows | Get all integration flows |
| search_integration_flows | Search integration flows by ID, version or name |
| get_value_mappings | Get all value mappings |
| search_value_mappings | Search value mappings by ID, version or name |
| get_message_mappings | Get all message mappings |
| search_message_mappings | Search message mappings by ID, version or name |
| get_script_collections | Get all script collections |
| search_script_collections | Search script collections by ID, version or name |
| get_integration_runtime_artifacts | Get all integration runtime artifacts |
| search_integration_runtime_artifacts | Search integration runtime artifacts by ID, version, name, type or status |
Installation
The MCP server can be installed as a standalone binary or run inside a Docker container.
Standalone binary
Option 1: Download binary
Download a binary compatible with your operating system / architecture from the Releases page.
Option 2: Install from source
Use the go install command to compile and install the MCP server:
go install github.com/vadimklimov/cpi-mcp-server@latest
Option 3: Build from source
- Clone the repository and navigate into the created directory:
git clone https://github.com/vadimklimov/cpi-mcp-server.git
cd cpi-mcp-server
- Optionally, download dependencies (otherwise, dependencies will be downloaded automatically during the next step, build):
go mod download
go mod tidy
- Use the
go buildcommand to compile the MCP server.
Example of basic build:
go build
Example of build with version information:
go build \
-ldflags "-s -w -X github.com/vadimklimov/cpi-mcp-server/internal/appinfo.version=1.2.3" \
-o cpi-mcp-server \
.
Alternatively, use GoReleaser to build the MCP server using the provided GoReleaser configuration file.
Docker container
Option 1: Pull Docker image
- Use the
docker image pullcommand (ordocker pullshorthand) to pull the MCP server image:
docker pull vadimklimov/cpi-mcp-server
Option 2: Build Docker image
- Clone the repository and navigate into the created directory:
git clone https://github.com/vadimklimov/cpi-mcp-server.git
cd cpi-mcp-server
- Use the
docker buildcommand to build the Docker image using the provided Dockerfile.
The following build arguments are supported:
| Argument | Description |
|---|---|
| VERSION | MCP server version |
Example of basic build:
docker build .
Example of build with version information:
docker build \
--tag vadimklimov/cpi-mcp-server:1.2.3 \
--build-arg VERSION=1.2.3 \
.
Alternatively, use the docker bake command (a part of Docker Buildx) to build the Docker image using the provided Bake definition file.
The Bake definition file includes the following build targets:
| Target | Description | Default | Multi-platform build | Image tag |
|---|---|---|---|---|
| dev | Development build | yes | no | dev |
| snapshot | Snapshot build | no | yes | {VERSION}-snapshot |
| release | Release build | no | yes | {VERSION}, latest |
The following Bake variables are supported:
| Variable | Description | Default value | Used by target |
|---|---|---|---|
| VERSION | MCP server version | dev | dev, snapshot, release |
| COMMIT_SHA | Build revision (commit hash for build) | unknown | snapshot, release |
Note
For
snapshotandreleasebuilds, using Docker Bake is the recommended approach. The Bake definition file provides sensible defaults and adds additional image metadata.
Warning
Before running
snapshotorreleasebuilds, ensure that multi-platform build support is enabled in the Docker environment.
Warning
The
releasetarget automatically pushes the built image to the registry.
Example of basic build (uses the dev target by default):
docker bake
Example of build with version information:
export VERSION=1.2.3
docker bake
or
docker bake \
--set dev.tags=vadimklimov/cpi-mcp-server:1.2.3 \
--set dev.args.VERSION=1.2.3
Tip
Given that the project is managed with Git, it is recommended to use the current commit hash (an SHA-1 hash) as the build revision.
To retrieve the long (full) form of the current commit hash, run the
git rev-parse HEADcommand.To retrieve the short form of the current commit hash, run the
git rev-parse --short HEADcommand.
Tip
Since the project already uses Git tags for MCP server release versioning, it is recommended to use Git tags for build versioning as well.
To retrieve the most recent tag, run the
git describe --tags $(git rev-list --tags --max-count=1)command.
Configuration
For the MCP server to function correctly, configuration must be provided in environment variables.
Environment variables
The following environment variables are supported:
| Environment variable | Description | Required | Valid values | Default value |
|---|---|---|---|---|
| MCP_CPI_BASE_URL | Base URL | yes | ||
| MCP_CPI_TOKEN_URL | Token URL | yes | ||
| MCP_CPI_CLIENT_ID | Client ID | yes | ||
| MCP_CPI_CLIENT_SECRET | Client secret | yes | ||
| MCP_CPI_TRANSPORT | MCP transport | no | stdio, http | stdio |
| MCP_CPI_PORT | Port to use for HTTP transport | no | value in range 1024-65535 | 8080 |
| MCP_CPI_LOG_LEVEL | Log level | no | none, error, warn, info, debug | none |
| MCP_CPI_LOG_FILE | Path to log file | no | /path/to/log/file.log | /var/log/cpi-mcp-server.log |
| MCP_CPI_MAX_CONCURRENCY | Maximum concurrency | no | Number of logical CPUs | |
| MCP_CPI_TIMEOUT | Timeout (in seconds) | no | 60 |
Access to SAP Cloud Integration APIs
The MCP server uses the public APIs of SAP Cloud Integration to retrieve the required information. These APIs are OAuth-protected and support the client credentials flow. This authentication mechanism is employed by the MCP server to authenticate and authorize API calls made to the SAP Cloud Integration tenant.
To enable the MCP server to access the necessary APIs of the SAP Cloud Integration tenant, an OAuth client for it must be created in the SAP Business Technology Platform subaccount where the corresponding subscription for SAP Integration Suite has been created.
In a Cloud Foundry environment, a service instance represents an OAuth client - hence, a service instance and a service key for it must be created.
Step 1: Create a service instance
Create a service instance with the following configuration:
- Service:
SAP Process Integration Runtime - Plan:
api - Grant type:
Client Credentials
The following roles are required by the corresponding MCP server tools:
| Tool | Role |
|---|---|
| get_integration_packages | WorkspacePackagesRead |
| search_integration_packages | WorkspacePackagesRead |
| get_integration_flows | WorkspacePackagesRead |
| search_integration_flows | WorkspacePackagesRead |
| get_value_mappings | WorkspacePackagesRead |
| search_value_mappings | WorkspacePackagesRead |
| get_message_mappings | WorkspacePackagesRead |
| search_message_mappings | WorkspacePackagesRead |
| get_script_collections | WorkspacePackagesRead |
| search_script_collections | WorkspacePackagesRead |
| get_integration_runtime_artifacts | MonitoringDataRead |
| search_integration_runtime_artifacts | MonitoringDataRead |
Step 2: Create a service key
Create a service key with the following configuration for the service instance created in the previous step:
- Key type:
ClientId/Secret
OAuth client credentials and endpoints can be found in the oauth section of the service key:
| Configuration parameter | Service key attribute |
|---|---|
| Base URL | url |
| Token URL | tokenurl |
| Client ID | clientid |
| Client secret | clientsecret |
Examples
Minimum configuration (required environment variables only):
MCP_CPI_BASE_URL=https://{subdomain}.it-cpi{xxxxx}.cfapps.{region}.hana.ondemand.com/api/v1
MCP_CPI_TOKEN_URL=https://{subdomain}.authentication.{region}.hana.ondemand.com/oauth/token
MCP_CPI_CLIENT_ID=xxxxxxxxxx
MCP_CPI_CLIENT_SECRET=xxxxxxxxxx
Full configuration (all supported environment variables):
MCP_CPI_BASE_URL=https://{subdomain}.it-cpi{xxxxx}.cfapps.{region}.hana.ondemand.com/api/v1
MCP_CPI_TOKEN_URL=https://{subdomain}.authentication.{region}.hana.ondemand.com/oauth/token
MCP_CPI_CLIENT_ID=xxxxxxxxxx
MCP_CPI_CLIENT_SECRET=xxxxxxxxxx
MCP_CPI_MAX_CONCURRENCY=3
MCP_CPI_TIMEOUT=120
MCP_CPI_TRANSPORT=http
MCP_CPI_PORT=8080
MCP_CPI_LOG_LEVEL=debug
MCP_CPI_LOG_FILE=/var/log/cpi-mcp-server.log
Agentic tools configuration
Refer to the documentation of the IDE, code editor, AI assistant or other agentic tool you use that supports MCP for configuration details.
Local MCP server
The examples below illustrate the configuration required to add a local MCP server to the Claude Desktop. Refer to the documentation of the agentic tool relevant to your setup to adapt these examples.
Option 1: Standalone binary
Assuming the cpi-mcp-server binary is located in the /Users/demo/go/bin directory, add the following configuration to the claude_desktop_config.json file:
{
"mcpServers": {
"cpi": {
"command": "/Users/demo/go/bin/cpi-mcp-server",
"env": {
"MCP_CPI_BASE_URL": "https://{subdomain}.it-cpi{xxxxx}.cfapps.{region}.hana.ondemand.com/api/v1",
"MCP_CPI_TOKEN_URL": "https://{subdomain}.authentication.{region}.hana.ondemand.com/oauth/token",
"MCP_CPI_CLIENT_ID": "xxxxxxxxxx",
"MCP_CPI_CLIENT_SECRET": "xxxxxxxxxx"
}
}
}
}
Option 2: Docker container
Assuming the MCP server configuration (see Configuration) is defined in the cpi-mcp-server.env located in the /Users/demo/.config/mcp directory, add the following configuration to the claude_desktop_config.json file:
{
"mcpServers": {
"cpi": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"--env-file",
"/Users/demo/.config/mcp/cpi-mcp-server.env",
"vadimklimov/cpi-mcp-server"
]
}
}
}
Remote MCP server
The examples below illustrate the configuration required to add a remote MCP server to the Claude Code. Refer to the documentation of the agentic tool relevant to your setup to adapt these examples.
Step 1: Start the MCP server
Option 1: Standalone binary
Assuming the cpi-mcp-server binary is located in the /Users/demo/go/bin directory, use the following command to start the MCP server:
export MCP_CPI_BASE_URL=https://{subdomain}.it-cpi{xxxxx}.cfapps.{region}.hana.ondemand.com/api/v1
export MCP_CPI_TOKEN_URL=https://{subdomain}.authentication.{region}.hana.ondemand.com/oauth/token
export MCP_CPI_CLIENT_ID=xxxxxxxxxx
export MCP_CPI_CLIENT_SECRET=xxxxxxxxxx
export MCP_CPI_TRANSPORT=http
/Users/demo/go/bin/cpi-mcp-server
Option 2: Docker container
Assuming the MCP server configuration (see Configuration) is defined in the cpi-mcp-server.env located in the /Users/demo/.config/mcp directory, use the docker container run command (or docker run shorthand) to start the MCP server:
docker run \
--detach \
--name cpi-mcp-server \
--publish 8080:8080 \
--env-file /Users/demo/.config/mcp/cpi-mcp-server.env \
vadimklimov/cpi-mcp-server
Tip
When using the HTTP transport in the MCP server, the container listens on port 8080. The
-p(--publish) option of thedocker runcommand can be used to publish the container's port 8080 to a different host port (for example,-p 8888:8080).
Step 2: Add a remote MCP server to Claude Code
Option 1: Use Claude Code CLI
Use the claude mcp add command to add the remote MCP server:
claude mcp add --transport http cpi http://localhost:8080/mcp
Option 2: Manually edit configuration file
Add the following configuration to the .mcp.json file:
{
"mcpServers": {
"cpi": {
"type": "http",
"url": "http://localhost:8080/mcp"
}
}
}
Note
When running the MCP server on a remote host, ensure that the host name is set appropriately when adding it to the agentic tool.
Warning
MCP servers operating in remote mode must be configured to use HTTPS (encrypted transport protocol) to ensure secure communication between the client and the server. Use of HTTP is strongly discouraged, as it does not provide transport-level security.
Warning
The current implementation of the MCP server does not provide authorization capabilities. When operating the server in remote mode, appropriate access restriction mechanisms must be implemented to prevent unauthorized access to the server.
History
Features 1
Notes
Changelog
New features
- bb8ff7db5e53e806b4beeca75e87c60c1984cdc4 feat: implement initial version of MCP server
Others providing
Compare all 29 on the Agent access to your systems page →- mcp-integration-suitemcp-integration-suiteAn experimental Node MCP server covering the general CPI functions of the Integration Suite, which its author recommends running alongside the TPM server for Trading Partner Management.independent, btpMCP server for the general Integration Suite functions
- mcp-is-tpmmcp-is-tpmA Java MCP server for Trading Partner Management in the Integration Suite, where trading partners, their agreements and their B2B configuration live, paired by its author with the general server.independent, btpJava MCP server for Integration Suite Trading Partner Management
- calmcpcalmcpAn MCP server in front of the SAP Cloud ALM APIs: four read tools over tasks, projects, features, documents, tests and analytics, run over stdio locally or Streamable HTTP on Cloud Foundry.independent, btpMCP server with read tools over the SAP Cloud ALM APIs
- CostingGeek/sap-mcpCostingGeek/sap-mcpA Python server that fetches sales orders from SAP's business data graph and hands them to Claude Desktop — the only entry here pointed at that API rather than at one system's own services.independent, btpPython MCP server fetching sales orders from SAP's business data graph
- mcp-sap-focusedrunmcp-sap-focusedrunSAP Focused Run's Landscape Management Database as MCP tools — hosts, systems, databases, cloud tenants, technical instances, ABAP clients, software components and product versions.independent, btpMCP tools over SAP Focused Run's Landscape Management Database
- cloud-alm-itsm-mcpcloud-alm-itsm-mcpQueries installations through SAP Cloud ALM's ITSM API — filtered by system type or customer number, with OAuth token handling and caching done for you.independent, btpMCP server querying installations via the SAP Cloud ALM ITSM API
- hana-mcp-serverhana-mcp-serverSchema discovery and guard-railed SQL against SAP HANA and HANA Cloud, with an optional layer of business metadata so an agent reads a coded column the way the business does.independent, btpMCP server for schema discovery and guarded SQL on SAP HANA
- sap_analytics_cloud_mcpsap_analytics_cloud_mcpThe SAP Analytics Cloud REST API as ninety tools across eleven service areas — content, data import and export, user management, transport, scheduling and translation.independent, btpMCP server for the SAP Analytics Cloud REST API
- mcp-sap-cpimcp-sap-cpiThe runtime half of Cloud Integration: failed messages with their full processing logs and traces, artifact deployment, security material, and a health summary.independent, btpMCP server for Cloud Integration runtime: messages, logs, deployment
- AI Core MCP ServerAI Core MCP ServerAn MCP server that exposes SAP AI Core's APIs as tools, defined entirely in one JSON config file for a proxy, so deployments, configurations and scenarios are managed through an assistant.independent, btpSAP AI Core APIs as MCP tools from one JSON config file
- BTP CF MCP ServerBTP CF MCP ServerThe Cloud Foundry V3 API on SAP BTP as MCP tools — apps, orgs, spaces, services, routes and quotas — declared in one JSON config file and run by odata-mcp-proxy.independent, btpCloud Foundry V3 API on SAP BTP as MCP tools
- BTP MCP ServerBTP MCP ServerBTP Core Services as MCP tools, and the only server in this corner that renders dashboards inside the chat — a subaccount overview with drill-down, a geomap of data-centre locations, consumption and users.independent, btpBTP Core Services as MCP tools with in-chat dashboards
- btp-sap-odata-to-mcp-serverbtp-sap-odata-to-mcp-serverExposes every OData service on an S/4HANA or ECC system as MCP tools, in three discovery levels so a large catalogue does not have to be loaded at once.independent, btpExposes S/4HANA or ECC OData services as MCP tools
- CI MCP ServerCI MCP ServerAn MCP server that exposes SAP Cloud Integration's OData APIs as tools, defined entirely in one JSON config file, so an assistant works integration content, logs and configurations in natural language.independent, btpSAP Cloud Integration OData APIs as MCP tools
- odata-mcp-proxyodata-mcp-proxyA config-driven proxy that turns OData and REST endpoints into MCP tools from a JSON file — no code — and runs on BTP Cloud Foundry against BTP Destinations.independent, btpConfig-driven proxy turning OData and REST endpoints into MCP tools
- sap-pi-mcp-serversap-pi-mcp-serverThe only entry pointed at SAP PI and PO rather than at Cloud Integration — monitoring and Integration Directory metadata from the middleware that came before.independent, btpMCP server for SAP PI and PO monitoring and directory metadata
- sap-bdc-mcp-serversap-bdc-mcp-serverAn MCP server over SAP's BDC Connect SDK that creates, validates, publishes and deletes Databricks Delta shares as data products in SAP Business Data Cloud.independent, btpMCP server managing Delta shares in SAP Business Data Cloud
- @mariodefe/sap-datasphere-mcp@mariodefe/sap-datasphere-mcpForty-five tools across a Datasphere tenant — discovery, metadata, analytics, ETL extraction, database users, lineage and column profiling — with config-driven PII masking applied before anything reaches the model.independent, btpMCP server with forty-five tools across a Datasphere tenant
- midasol/sap-mcp-servermidasol/sap-mcp-serverA Python MCP server for SAP Gateway with four read-only tools that authenticate, query, fetch one entity and list services, and one of the few here that publishes its test results.independent, btpPython MCP server for SAP Gateway OData operations
- odata_mcp_goodata_mcp_goA Go binary that bridges any OData v2 or v4 service to MCP — and can collapse the whole service into one tool when the generated tool list is too large to be usable.independent, btpGo binary bridging any OData v2 or v4 service to MCP
- odata_mcpodata_mcpThe Python original: reads an OData v2 service's metadata and generates MCP tools from it, with the SAP-specific conversions the raw protocol leaves to you.independent, btpPython bridge generating MCP tools from OData v2 metadata
- sap-bdc-mcpsap-bdc-mcpDiscovery and contract tooling for SAP Business Data Cloud — ORD discovery, CSN contract checks and non-executing share planning — behind redaction, policy gates and bounded output.independent, btpMCP tooling for SAP Business Data Cloud discovery and contracts
- mcp-sap-datasphere-servermcp-sap-datasphere-serverThe read-only Datasphere server: explore spaces, list assets, preview rows, profile columns and summarise analytical models — and nothing that changes anything, by design.independent, btpRead-only MCP server for exploring SAP Datasphere
- sac-workbench-mcpsac-workbench-mcpAn unofficial MCP server that lets an assistant author in SAP Analytics Cloud: 178 tools sent as the requests the SAC web UI itself sends, from a Chrome session the server signs in once.independent, btpMCP server for authoring in SAP Analytics Cloud from an assistant
- MCP Server for SAP BTP AdministrationMCP Server for SAP BTP AdministrationSAP-hosted MCP endpoint that exposes BTP account administration — accounts, security, services and connectivity — as tools an AI client discovers and calls on your behalf.sap official, btpSAP-hosted MCP endpoint for BTP account administration
- SAP LeanIX MCP ServerSAP LeanIX MCP ServerHosted MCP endpoint onto an SAP LeanIX instance, exposing selected enterprise-architecture APIs as tools — fact sheets, applications, completeness and custom reports.sap official, btpHosted MCP endpoint onto an SAP LeanIX instance
- SAP-samples/hana-cli-claude-pluginSAP-samples/hana-cli-claude-pluginA Claude Code plugin that registers the MCP server of hana-cli, so Claude Code can work on SAP HANA Cloud and on-premise SAP HANA databases.sap official, btpClaude Code plugin registering hana-cli's MCP server
- SAP-samples/hana-developer-cli-tool-exampleSAP-samples/hana-developer-cli-tool-exampleA developer-centric command line for SAP HANA, built for local development outside SAP tooling and connecting to a local, cloud or remote HANA instance the same way.sap official, btpDeveloper-centric command line for SAP HANA
Details
Sources
Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.
Compatibility and provenance
History in the atlas
- The concern it answers is reaching into an SAP system from outside, split out of MCP servers on this day; the sentence on the edge is unchanged.
- Triaged out of data/crawled/mcp-candidates.json, the sap-ai-mcp-servers sweep. Written from the repository's own README. Filed on the BTP door: the Integration Suite is BTP services, which is the reasoning the door list has carried since it was written.
- First seen.
For your agent
- Ref
artifact:vadimklimov-cpi-mcp-server- JSON
- /artifacts/vadimklimov-cpi-mcp-server.json
- MCP
- Connecting an agent