cpi-mcp-server
Provides an MCP server that enables AI agents to query SAP Cloud Integration (Integration Suite) tenant data—such as integration packages, flows, mappings, and runtime artifacts—by calling SAP CPI public OAuth-protected APIs using the client-credentials flow.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Uses OAuth client credentials (stronger than no auth) and documents required roles per tool, reducing over-permission. TLS is implied by HTTPS in example URLs, but enforcement/verification details are not explicitly stated. Client secret handling best-effort is suggested via environment variables; however, there is no explicit statement about logging/redaction practices. No evidence is provided about dependency health or vulnerability management.
⚡ Reliability
Best When
You need an MCP-compatible integration layer for read-only discovery/analysis of CPI tenant assets from an AI agent, where you can provision OAuth client credentials in BTP.
Avoid When
You cannot store/provision client credentials safely (client secret) or cannot connect to the SAP CPI OAuth/token endpoints from where the MCP server runs.
Use Cases
- • Agent-assisted browsing of SAP Cloud Integration artifacts (packages, flows, mappings)
- • Search and discovery of CPI objects by identifiers, versions, names, vendor, and status
- • Generating documentation or summaries of CPI tenant assets for dev/support workflows
- • Monitoring/inspection workflows using runtime artifact data (MonitoringDataRead)
Not For
- • Making arbitrary changes to SAP CPI (the described tools appear read-only)
- • Handling end-user interactive sign-in flows (the described auth is service-to-service)
- • Use cases requiring strict contractual uptime/SLA guarantees or strong published reliability metrics (not evidenced in provided content)
Interface
Authentication
The MCP server uses SAP CPI OAuth-protected public APIs via client credentials. It requires MCP_CPI_BASE_URL, MCP_CPI_TOKEN_URL, MCP_CPI_CLIENT_ID, MCP_CPI_CLIENT_SECRET. Required CPI API scopes/roles are documented per tool (e.g., WorkspacePackagesRead, MonitoringDataRead).
Pricing
No pricing model stated for the MCP server itself; costs would primarily come from SAP/BTP platform usage and your infrastructure to run the server.
Agent Metadata
Known Gotchas
- ⚠ Requires correct MCP_CPI_* configuration and valid SAP OAuth client credentials; failures will prevent tool execution.
- ⚠ For HTTP transport mode, the container listens on port 8080; misconfigured networking/ports may break remote MCP usage.
- ⚠ Role/scope requirements differ by tool; missing roles in SAP BTP will cause authorization failures for subsets of tools.
- ⚠ No explicit rate-limit or pagination behavior is documented in the provided content; agents may need to handle large result sets cautiously.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for cpi-mcp-server.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-30.