What is the SAP MCP Gateway?
The MCP Gateway is part of SAP Integration Suite on SAP BTP. It takes what you already expose - SAP APIs, non-SAP APIs, integration flows, data sources and external MCP servers - and presents it to AI agents as Model Context Protocol (MCP) tools, behind a single governed entry point. SAP calls it the natural evolution of the API Gateway into the agentic era.
It was announced at SAP TechEd in November 2025. SAP's own Integration Suite blog of July 2026 describes it as available now.
What it does
- APIs become tools. API specifications are translated into MCP schemas and enriched with natural-language descriptions. Backends connect through the API providers and BTP destinations you already use.
- One catalogue for developers. The Developer Hub lists MCP tools and servers next to APIs, so developers discover and subscribe to them the same way.
- Governed access. Rate limiting, IP blocking, OIDC authentication (XSUAA or a third-party identity provider) and payload protection. Each agent sees only the tools it is authorised to use.
- Every call is traced. Tool calls are logged with traceability and analytics.
- On-premise reach. SAP documents principal propagation through the gateway to S/4HANA on-premise, so a call runs as the user rather than as a technical account.
The SAP Architecture Center recommends it as the path for third-party agents and for pro-code and low-code agents on SAP BTP that need to reach SAP systems.
Where it is available
SAP states the MCP Gateway is included in the Premium and Enhanced editions of Integration Suite, and can be tried on the SAP BTP trial and the Free Service Plan. We have not found an official general-availability date, so confirm the status for your landscape with SAP.
What it does not do
SAP is explicit on this: MCP is a connectivity protocol, not a semantic layer. The gateway decides who may call which tool; it does not decide what a good tool is. A tool that returns a raw table of 400 fields is still a poor tool for a model, gateway or not. Designing tools that are small, well described and safe to call is still your work.
It is also not MCP Builder. MCP Builder is a Joule Studio feature for creating MCP servers; the gateway governs access to tools once they exist.
Where Boidra fits
Boidra does not change the MCP Gateway - it stays exactly as SAP ships it. We work on the two things around it:
- Tools worth exposing. We design and build MCP servers for SAP whose tools are scoped, described and safe for a model to call.
- One place to find and govern them. In the Boidra Platform, MCP servers exposed through the gateway sit in one catalogue with your custom agents and skills - reviewed before publishing, installable by role, and costed from their first call.
Frequently asked questions
What is the SAP MCP Gateway?
A capability of SAP Integration Suite that exposes SAP APIs, non-SAP APIs, integration flows, data sources and external MCP servers as Model Context Protocol tools that AI agents can call, behind one governed entry point. SAP describes it as the enterprise control plane for MCP.
Do I need to build my own MCP server?
Not for APIs and integration flows you already have. The gateway translates API specifications into MCP tool schemas, so existing APIs and iFlows can be exposed as MCP tools without writing a custom MCP application.
Which Integration Suite editions include it?
SAP states it is available in the Premium and Enhanced editions of Integration Suite, and on the SAP BTP trial and Free Service Plan (SAP Community, July 2026). Confirm commercial details for your contract with SAP.
Is the MCP Gateway the same as MCP Builder?
No. MCP Builder is a Joule Studio feature for creating MCP servers. The MCP Gateway is part of Integration Suite and governs access to tools. SAP has not published a statement on how the two connect, so treat them as separate products.