mcp-sap-cpi
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CPI_CLIENT_ID | Yes | The client ID from the service key | |
| CPI_TOKEN_URL | Yes | The OAuth token URL from the service key | |
| CPI_TENANT_URL | Yes | The SAP CPI tenant URL from the service key | |
| CPI_CLIENT_SECRET | Yes | The client secret from the service key |
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
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_failed_messagesA | List failed messages from SAP CPI message processing logs. Returns messageId, status, artifact name, error, and timestamp. |
| get_message_detailsA | Get full message processing log details for a specific CPI message ID. |
| get_trace_logA | Get step-by-step trace log for a CPI message (only available when trace is enabled on the iFlow). |
| list_packagesB | List all integration packages in the SAP CPI tenant. |
| list_artifactsA | List all artifacts (iFlows, mappings, scripts) in a specific integration package. |
| get_artifactB | Get metadata and configuration details for a specific artifact. |
| deploy_artifactB | Deploy an artifact version to the SAP CPI runtime. |
| undeploy_artifactB | Undeploy an artifact from the SAP CPI runtime. |
| list_credentialsA | List all user credential (basic auth) aliases configured in SAP CPI. |
| list_keystoresA | List all keystore entries in SAP CPI, including alias and expiry date. |
| list_oauth_credentialsA | List all OAuth2 client credential configurations in SAP CPI. |
| get_runtime_artifactsA | List all deployed runtime artifacts in SAP CPI with their deployment status (STARTED, STOPPED, ERROR). |
| get_system_statusA | Get overall SAP CPI system health — active alerts and system status summary. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.