SAP Integration Suite MCP Gateway: Governed AI-Agent Access to S/4HANA, Ariba and SuccessFactors
For integration architects and CoE leads who must let AI agents act on SAP systems — without bypassing the API governance they already built.
Every enterprise building AI agents eventually hits the same question: how do we let agents call SAP without creating a shadow integration layer? SAP's answer is to put MCP in front of the governed API layer you already run. In SAP Integration Suite, the MCP server capability is delivered through the MCP gateway, which sits alongside the API gateway and shares its security, traffic-management and routing capabilities.
1. How the MCP gateway works
Think of it as API Management for agents. An MCP client (Joule Studio agent, a pro-code agent, VS Code, Claude, Cursor) connects to an MCP endpoint hosted by Integration Suite. Each tool call flows through the gateway's policies to your backend:
Agent → MCP Gateway (policies) → MCP tool → API artifact / HTTP endpoint → Cloud Integration iFlow or S/4HANA API → response back to the agent.
MCP server artifacts run on the Integration Cell runtime, SAP's managed, cloud-native runtime for API and MCP server lifecycle management.
2. Ways to create an MCP server
From an API artifact — take a REST/OData API you already manage and expose selected operations as MCP tools. The API artifact must be deployed on the Integration Cell runtime.
From an HTTP endpoint with an OpenAPI specification — point at any endpoint, import its OpenAPI spec, and choose operations to expose.
From an RFC backend — useful for on-premise ECC or S/4HANA function modules reached through Cloud Connector.
Creation happens inside an integration package: Artifacts → Add → MCP Server.
3. Security you get out of the box
When an MCP server is created, Integration Suite applies a default processing template that includes:
Authentication of the consumer (OAuth client credentials via a service key).
Authorisation scope (for example API.invoke).
Traffic management — quota and spike arrest to protect backends from runaway agents.
You then deploy the server and publish it as a product in the Developer Hub, where consumers subscribe and receive credentials. This is the same governance model your API consumers already follow — which is exactly why CISOs accept it.
4. Design rules: curate, don't pass through
The biggest risk with "checkbox MCP" is exposing a 40-operation OData service to an LLM. Agents perform best with a small number of task-shaped tools. Our rules:
Five to ten tools per MCP server, each named as a business task (getPurchaseOrderStatus, not A_PurchaseOrder_GET).
Compose in Cloud Integration first. If an answer needs three entities (PO, GR, invoice), build one iFlow that returns a combined, flattened payload. The agent then makes one call instead of reasoning across three.
Read-only first. Launch with read tools. Add write tools only with business approval, idempotency and human-in-the-loop confirmation in the agent.
Trim payloads. Use mapping to remove fields the agent does not need — fewer tokens, less data exposure.
Write rich OpenAPI descriptions. The descriptions become the tool descriptions the agent reads.
5. Example scenarios
S/4HANA procurement agent — PO status, open GR/IR items and supplier delivery performance via composed iFlows.
SAP Ariba sourcing assistant — read sourcing events and supplier risk data through Ariba APIs wrapped as governed tools.
SuccessFactors HR helper — headcount and position data with field-level trimming to protect personal data.
Cloud Integration monitoring assistant — expose Message Processing Log queries so support teams can ask "which iFlows failed in the last hour and why?".
6. Where it fits with CAP MCP and Joule
Use CAP @mcp when the tool is custom business logic you own in a BTP extension. Use the Integration Suite MCP gateway when the tool wraps enterprise APIs and needs API-management policies, quotas and a developer portal. Many landscapes use both: CAP builds the logic, Integration Suite governs and publishes it. Bringing third-party MCP servers under the gateway's control plane ("MCP federation") has been discussed as a roadmap topic — verify the current status on the SAP Road Map Explorer before designing around it.
FAQ
Do I need API Management activated? Yes — Cloud Integration and API Management capabilities, plus the Integration Cell runtime, are prerequisites.
Which clients can consume it? Any MCP-compatible client: Joule Studio agents, pro-code agents, and developer tools.
Talk to us
Raven Infotech designs governed MCP layers on SAP Integration Suite for S/4HANA, Ariba and SuccessFactors landscapes. Request our MCP Gateway blueprint workshop — we'll map your top 10 agent use cases to curated, secured tools.
Comments