mcp-sap-cpi
Provides tools for monitoring and managing SAP Cloud Platform Integration (CPI) artifacts, including message monitoring (failed messages, details, trace logs), integration content management (list packages, artifacts, deploy/undeploy iFlows), security artifacts (credentials, keystores, OAuth2), and runtime status checks.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-sap-cpi Show me the last 10 failed messages in CPI"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
mcp-sap-cpi
An open-source MCP (Model Context Protocol) server that connects Claude to SAP Cloud Platform Integration (CPI). Ask Claude to diagnose failed messages, review iFlows, deploy artifacts, check credentials, and more — directly from your conversation.
What it does
Category | Tools |
Message Monitoring | List failed messages, get full MPL details, retrieve trace logs |
Integration Content | Browse packages, list artifacts, deploy/undeploy iFlows |
Security Artifacts | List credentials, keystores, OAuth2 configurations |
Runtime Status | Check deployed artifact status, system health summary |
Related MCP server: SAP CPI MCP Server
Requirements
Node.js 18+
SAP CPI tenant (Integration Suite or standalone CPI)
BTP service key with Process Integration Runtime role (
it-rtplan)
Installation
npm install -g mcp-sap-cpiOr run without installing:
npx mcp-sap-cpiConfiguration
1. Get your BTP service key
In SAP BTP Cockpit:
Go to your subaccount → Services → Instances and Subscriptions
Create a service instance:
Process Integration Runtime→ planit-rtCreate a service key → copy the JSON
From the service key JSON, extract:
url→CPI_TENANT_URLtokenurl→CPI_TOKEN_URLclientid→CPI_CLIENT_IDclientsecret→CPI_CLIENT_SECRET
2. Set environment variables
Create a .env file (or set in your Claude Desktop config — see below):
CPI_TENANT_URL=https://<tenant>.it-cpi.cfapps.<region>.hana.ondemand.com
CPI_TOKEN_URL=https://<subdomain>.authentication.<region>.hana.ondemand.com/oauth/token
CPI_CLIENT_ID=sb-<your-client-id>
CPI_CLIENT_SECRET=<your-client-secret>3. Register with Claude Desktop
Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"sap-cpi": {
"command": "npx",
"args": ["mcp-sap-cpi"],
"env": {
"CPI_TENANT_URL": "https://<tenant>.it-cpi.cfapps.<region>.hana.ondemand.com",
"CPI_TOKEN_URL": "https://<subdomain>.authentication.<region>.hana.ondemand.com/oauth/token",
"CPI_CLIENT_ID": "your-client-id",
"CPI_CLIENT_SECRET": "your-client-secret"
}
}
}
}4. Register with Claude Code
claude mcp add sap-cpi npx mcp-sap-cpi \
-e CPI_TENANT_URL=https://<tenant>.it-cpi.cfapps.<region>.hana.ondemand.com \
-e CPI_TOKEN_URL=https://<subdomain>.authentication.<region>.hana.ondemand.com/oauth/token \
-e CPI_CLIENT_ID=your-client-id \
-e CPI_CLIENT_SECRET=your-client-secretTools Reference
Message Monitoring
get_failed_messages
List failed messages from the Message Processing Log.
Parameter | Type | Required | Description |
| number | No | Max results (default: 20) |
| string | No | Filter by iFlow name |
| string | No | ISO date — messages after this date |
Example prompt: "Show me the last 10 failed messages in CPI"
get_message_details
Get full MPL details for a specific message.
Parameter | Type | Required | Description |
| string | Yes | The CPI message GUID |
Example prompt: "Get details for message ID abc-123-def"
get_trace_log
Get step-by-step payload trace for a message (requires trace mode enabled on the iFlow).
Parameter | Type | Required | Description |
| string | Yes | The CPI message GUID |
Example prompt: "Show me the trace log for message abc-123-def"
Integration Content
list_packages
List all integration packages in the tenant.
Example prompt: "What integration packages do I have in CPI?"
list_artifacts
List all artifacts in a package.
Parameter | Type | Required | Description |
| string | Yes | The integration package ID |
Example prompt: "List all iFlows in the HR_Integration package"
get_artifact
Get metadata and configuration for a specific artifact.
Parameter | Type | Required | Description |
| string | Yes | The artifact ID |
| string | Yes |
|
deploy_artifact
Deploy an artifact version to the runtime.
Parameter | Type | Required | Description |
| string | Yes | The artifact ID |
| string | No | Default: |
Example prompt: "Deploy the Employee_Sync iFlow"
undeploy_artifact
Undeploy an artifact from the runtime.
Parameter | Type | Required | Description |
| string | Yes | The artifact ID |
Security Artifacts
list_credentials
List all user credential (basic auth) aliases.
Example prompt: "What credentials are configured in CPI?"
list_keystores
List all keystore entries with alias and expiry date.
Example prompt: "Are any of my CPI certificates expiring soon?"
list_oauth_credentials
List all OAuth2 client credential configurations.
Runtime Status
get_runtime_artifacts
List all deployed runtime artifacts with status (STARTED, STOPPED, ERROR).
Example prompt: "Which iFlows are currently in ERROR state?"
get_system_status
Get a summary of deployed artifact health.
Example prompt: "Give me a CPI system health check"
Example conversations
Diagnose a failed message:
"Why did my HR_Employee_Sync iFlow fail? Show me the last error."
Check certificates:
"List all keystore entries in CPI and flag any expiring within 90 days."
Deploy after a fix:
"Deploy the Order_Processing iFlow to the runtime."
Audit credentials:
"What OAuth2 credentials are configured in my CPI tenant?"
System overview:
"Give me a health check — how many iFlows are running vs in error?"
Local development
git clone https://github.com/prudvigit/mcp-sap-cpi.git
cd mcp-sap-cpi
npm install
cp .env.example .env
# fill in your CPI credentials in .env
npm run devRoadmap
Value mapping query tool
Alert management tools
iFlow content download (for AI-assisted review)
Integration with tics-sap-ai-suite
License
MIT
Available Tools
13 toolsdeploy_artifactB
Deploy an artifact version to the SAP CPI runtime.
Inputs: artifactId (required), artifactType.
get_artifactB
Get metadata and configuration details for a specific artifact.
Inputs: artifactId (required), artifactType (required).
get_failed_messagesA
List failed messages from SAP CPI message processing logs. Returns messageId, status, artifact name, error, and timestamp.
Inputs: top, fromDate, artifactName.
get_message_detailsA
Get full message processing log details for a specific CPI message ID.
Inputs: messageId (required).
get_runtime_artifactsA
List all deployed runtime artifacts in SAP CPI with their deployment status (STARTED, STOPPED, ERROR).
Inputs: no named parameters.
get_system_statusA
Get overall SAP CPI system health — active alerts and system status summary.
Inputs: no named parameters.
get_trace_logA
Get step-by-step trace log for a CPI message (only available when trace is enabled on the iFlow).
Inputs: messageId (required).
list_artifactsA
List all artifacts (iFlows, mappings, scripts) in a specific integration package.
Inputs: packageId (required).
list_credentialsA
List all user credential (basic auth) aliases configured in SAP CPI.
Inputs: no named parameters.
list_keystoresA
List all keystore entries in SAP CPI, including alias and expiry date.
Inputs: no named parameters.
list_oauth_credentialsA
List all OAuth2 client credential configurations in SAP CPI.
Inputs: no named parameters.
list_packagesB
List all integration packages in the SAP CPI tenant.
Inputs: no named parameters.
undeploy_artifactB
Undeploy an artifact from the SAP CPI runtime.
Inputs: artifactId (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 13 tools
Each tool targets a distinct resource and action: message logs (list failed, get details, get trace), packages, artifacts (list, get, deploy, undeploy), credentials (basic vs OAuth), runtime artifacts, and system status. No meaningful overlap; descriptions clearly differentiate the purposes.
All tools follow a consistent verb_noun snake_case pattern (get_*, list_*, deploy_artifact, undeploy_artifact). The verbs are limited to clear, common actions, and there are no style inconsistencies or vague names.
13 tools is well within the ideal range for a domain-specific server. Each tool covers a distinct aspect of SAP CPI management (monitoring, artifact lifecycle, credentials, system status) without redundancy or bloat.
Core workflows are covered: message monitoring, artifact discovery/deployment, credential listing, and system health. Minor gaps exist such as no explicit start/stop for runtime artifacts or the ability to update/delete credentials, but these are not critical for typical monitoring and deployment tasks.
Maintenance
Related MCP Connectors
Connect Claude to your Platform7n workspaces: chat, links, work and decks. One-click OAuth.
Connect Claude to your Platform7n workspaces: chat, links, work and decks. One-click OAuth.
1Read and write Sage Intacct from Claude or ChatGPT. Write tools are flagged for approval.
Create contacts, move deals, send proposals and invoices, read your inbox, from Claude or ChatGPT.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables interaction with SAP Integration Suite for designing, creating, and managing integration artifacts including integration flows, message mappings, packages, and B2B trading partner relationships through AI-powered natural language commands.32-
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to interact with SAP Cloud Integration (CPI) by exposing CPI APIs as MCP tools for inspecting metadata, runtime artifacts, message logs, and failed messages.3-
- FlicenseBqualityCmaintenanceEnables managing SAP Cloud Integration iFlows, packages, configurations, deployments, and runtime artifacts via natural language through the OData API.25-
- FlicenseNot gradedqualityCmaintenanceEnables operating an SAP Integration Suite Cloud Integration tenant from Claude Code, with tools to read packages, iFlows, and logs, and to create, clone, configure, validate, and deploy artifacts, as well as invoke iFlows and inspect step payloads.1-