AI & Analytics Legends The knowledge platform for SAP Analytics Sign inSign up
Guide

SAP Integration Suite MCP: servers, gateway and requirements

SAP Integration Suite MCP: servers, gateway and requirements — Analytics Legends section illustration for SAP analytics market intelligence (Datasphere, BDC, SAC, BW/4HANA)

As of 2026-10-18

Edited by , sole editor and publication director — 27 years in the SAP ecosystem. How these pages are produced, and where automation is used.

SAP Integration Suite MCP is the official, SAP-maintained route for exposing enterprise APIs to AI agents. It has two parts in our catalogue (18 October 2026): the MCP Server artefact, built inside Integration Suite, and the MCP Gateway, a control plane for authentication, rate limiting and monitoring. The gateway needs the Premium or Enhanced edition and the Integration Cell runtime.

The MCP Server artefact

An MCP Server in Integration Suite is an artefact that exposes enterprise APIs and data to AI agents as governed MCP tools, resources and prompts. It can be built on your own APIs or on third-party MCP servers. Our concept notes add that it can be created from API artefacts, OpenAPI-described HTTP endpoints or RFC backends, and published through the Developer Hub.

That matters because it reuses what an integration team already governs. You do not stand up a new Node service; you expose an interface that already has an owner. The catalogue does not state the artefact's maturity status or licensing, so confirm both with SAP before planning.

In practice the work splits between roles: an integration developer models the tool surface, a security owner approves the backend identity, and an agent owner registers the server with Joule or another client. Agreeing that split before the first artefact is built avoids a gateway full of unowned tools.

The MCP Gateway

The gateway puts SAP and non-SAP APIs, integration flows and external MCP servers behind one governed entry point, with authentication, rate limiting and monitoring. Its transport is HTTP. Requirements are the Premium or Enhanced edition and the Integration Cell runtime, so this is an architectural commitment, not a toggle.

SAP's API policy, as summarised in our concept notes, restricts agentic use of SAP APIs to SAP-endorsed pathways and names the Integration Suite MCP gateway, SAP-provided MCP servers via Joule Studio and A2A as endorsed. That is the reason architects end up here for production work on systems of record.

Wiring it to assistants

An MCP server deployed on the Integration Cell runtime can be registered in Joule Work Desktop (part of SAP's Early Adopter Care programme, not generally available) so Joule can call its tools during conversations. Separately, Joule Studio (classic edition) lets you attach MCP servers to a Joule agent so it can reach external applications from the Joule chat. Other MCP clients can connect to the gateway endpoint, subject to its authentication.

What to check before production

Identity: decide whether tool calls carry the end user or a technical identity towards the backend; for on-premise S/4HANA our notes record principal propagation through Cloud Connector. Scope: expose the narrowest API subset per MCP server, and prefer read tools first. Rate limiting: set limits per client, since agents can loop. Monitoring: confirm that tool calls appear in the logs your operations team already watches. Contract: version tool descriptions as you would an API, because the model reads them as instructions. Cost: the Premium or Enhanced edition and the Integration Cell runtime have commercial and operational implications that the catalogue does not quantify.

What it does not do

It is not a drop-in for every SAP product. Where a product has its own MCP server, such as the BTP administration server or LeanIX, those are separate. For products with no official server, such as SAC, Datasphere or SuccessFactors, you model the APIs yourself behind the gateway.

For market data around SAP integration work, such as firms, rates and opportunities, the Analytics Legends MCP offers read-only public tools. It does not connect to your Integration Suite tenant.

The catalogue also gives no performance, latency or scale figures for the gateway, and no statement of which SAP backends are validated. Treat those as items for a proof of concept with your own landscape, not as assumptions.

What we cannot assert

Status, licence and pricing of the MCP Server artefact and the Gateway are not stated in the catalogue.

Frequently asked

What do I need to use the Integration Suite MCP Gateway?

The Premium or Enhanced edition and the Integration Cell runtime, per the catalogue entry.

Is Integration Suite MCP an official SAP product?

Yes, both the MCP Server artefact and the Gateway are SAP-maintained according to SAP Help and the SAP Developers tutorial.

Can Joule use servers built in Integration Suite?

Yes. An MCP server on the Integration Cell runtime can be registered in Joule Work Desktop, and Joule Studio can attach MCP servers to agents.

Does it work with non-SAP MCP servers?

The gateway can front external MCP servers, and an MCP Server artefact can be built on third-party ones, per the catalogue.

Engage the editor

This guide is written by . 27 years of SAP — Datasphere, Business Data Cloud, SAC Planning, Joule. Freelance or permanent · Hybrid / remote · Anywhere in EMEA. Available from 19 October 2026.

Profile and contact

What this page is built on

External sources

Read next

Guides that answer with this page

These guides cite this page as one of the sources their answer rests on.