1. Home
  2. SAP integration
  3. SAP MCP

SAP supports MCP servers for Business One, Integration Suite and its coding tools

Yes. SAP supports MCP servers, but each one covers a single product. SAP Business One 10.0 FP 2608 supports an open-source MCP server for its Service Layer. SAP Integration Suite turns your own APIs into MCP servers, and SAP's servers for CAP and UI5 help developers write code.

Checked 18 November 2026

MCP gives an AI agent one way to use SAP’s APIs

SAP’s explainer calls MCP an open standard that helps AI agents reach business apps and data safely. It works with APIs. In SAP’s words, MCP is “a complement to API management”. With a plain API, a developer must know each endpoint in advance, while an MCP server lists its tools so an agent can discover what it may call.

The protocol names three roles. A host is the AI app. A client is the connector inside it. A server offers tools. Tools are functions the AI model may run, and messages travel between the parts as JSON-RPC 2.0. The current version of the rules is dated 28 July 2026. Our article on what an MCP server is covers the protocol on its own.

SAP’s MCP servers, product by product

For your own agent, two of these are the routes into business data: the Business One server and the Integration Suite artifact. The CAP and UI5 servers help a developer build SAP apps.

Scroll the table sideways to see every column.

SAP product What SAP ships Status we found How it signs in
SAP Business One 10.0 An open-source MCP server for the Service Layer, with SAP sample code Added in FP 2608. SAP added its notes for that release on 3 August 2026 Not stated on the pages we could read. On the SAP side, the server signs in to the Service Layer with a session login or an access token
SAP Integration Suite An MCP Server artifact that turns an API into an MCP server, and an MCP Gateway SAP’s tutorial dates from 23 September 2026. Enhanced, Premium and Trial plans only Basic, OAuth 2.0, a client certificate, or tokens from an identity provider such as Microsoft Entra ID, Google or Okta
SAP CAP @cap-js/mcp-server, with the tools search_model and search_docs On SAP’s cap-js GitHub. SAP says the tools are not a stable API Works on your code project and searches CAP docs on your machine
SAP UI5 @ui5/mcp-server, with tools such as create_ui5_app and run_ui5_linter On SAP’s UI5 GitHub, copyright 2026 SAP SE Works on your UI5 project

None of the SAP pages we read on 18 November 2026 says whether these servers are in beta or generally available. The dates in the table are when SAP published each release note or page.

SAP’s prebuilt Joule Agents use MCP and the A2A protocol to work across systems, SAP says. They are agents, not a server your own agent connects to.

The Business One MCP server works through the Service Layer

SAP added the server in Business One 10.0 FP 2608. SAP’s release notes say Business One “now supports an open-source MCP (Model Context Protocol) Server for integrating AI agents with Service Layer”. The Service Layer is the web API other software uses to read and write Business One data.

On the SAP side, the server signs in to the Service Layer like any other client. That means a session login, after which each request carries the B1SESSION cookie, or an access token. Since FP 2602, the Service Layer checks the audience of tokens from single-page apps by default. The token must name the Service Layer client ID, or the call fails with a 401 error. An admin can switch the check off in b1s.conf for testing.

Give the server its own Business One user, never a superuser, whose rights SAP says cannot be limited.

This route matters because Business One’s own AI stops short of your data. SAP says the AI in the Business One Web client cannot read, create, change or delete Business One data. Our research note on SAP Business One and Joule covers the rest of SAP’s AI for Business One.

SAP’s sample code page sits on help.sap.com/docs, which loads by script. Our fetcher got no text from it on 18 November 2026, so this page does not list the sample server’s tools.

Integration Suite turns your own APIs into MCP servers

SAP says Integration Suite can expose your APIs as governed MCP servers. Its tutorial walks through five steps:

  1. Pick a source. The server can come from any HTTP endpoint, using its URL and its OpenAPI Specification.
  2. Pick the tools. The wizard lists every operation in the specification as a tool. You choose which ones the agent gets.
  3. Set the sign-in. Basic, OAuth 2.0, a client certificate, or tokens from an outside identity provider such as Microsoft Entra ID, Google or Okta.
  4. Add limits. Quota limits and Spike Arrest keep the systems behind the server from overload.
  5. Deploy. The tutorial runs the server on the Integration Cell runtime. SAP tells you to check which BTP regions offer that runtime.

The MCP Gateway is the layer above. SAP’s gateway tutorial, from 1 October 2026, says it governs who may use each tool. It checks sign-in and rights, limits the rate of calls and guards the data sent. It also gathers tools from SAP APIs, other vendors’ APIs, integration flows, data sources and outside MCP servers into one entry point.

Plans decide what you can use. The MCP Server artifact is on the Enhanced, Premium and Trial plans. For live use, the gateway tutorial names the Premium or Enhanced Edition in one place and the Enhanced Edition in another, so confirm the edition with SAP. SAP also says one governed surface links Joule with outside agents such as Microsoft Copilot, Claude and LangChain.

SAP’s CAP and UI5 servers help developers, not end users

CAP is SAP’s Cloud Application Programming Model. SAP’s tutorial from 12 August 2026 says that “In CAP, MCP is just another protocol”. So a team that builds its own CAP service can give it an MCP endpoint.

SAP’s cap-js/mcp-server is a different tool. It helps an AI coding assistant with a CAP project. Its search_model tool searches the names in the project’s compiled data model. Its search_docs tool searches CAP’s documentation on your own machine.

The UI5 server does the same job for UI5 apps. Its tools create a new UI5 app, run SAP’s UI5 linter and pull a project’s settings. Both repositories describe tools for building apps.

Community SAP MCP servers are not SAP’s

Several people publish SAP MCP servers of their own. Read each one’s repository before you use it. Two examples, from their own GitHub pages:

  • mcp-abap-adt, published by the GitHub user mario-andreschak. It lets an AI tool work with an SAP ABAP system over MCP. It says its 16 tools are read-only. It signs in with the system’s URL, a user name, a password and the SAP client number, and it needs the /sap/bc/adt service switched on.
  • mcp-integration-suite, published by the GitHub user 1nbuc. Its tools handle only Integration Suite packages, integration flows and message mappings. Its own page warns: “This server is still experimental. Use at your own risk!”

Neither one comes from SAP.

Five rules before an agent acts in SAP through MCP

The MCP rules and SAP’s own pages give a short checklist:

  • Sign-in is optional in MCP. The specification says authorization is optional. Check that each server you use asks for it.
  • Tokens must be meant for the server. MCP says a server must check that a token was issued for it. Business One’s Service Layer runs a like check on tokens from single-page apps, on by default since FP 2602.
  • A person can say no. The MCP rules say a human should be able to deny tool calls.
  • Tool descriptions are untrusted. MCP treats a tool’s description as untrusted unless it comes from a trusted server.
  • Know where the server runs. Anthropic’s MCP connector in its Messages API reaches only public HTTP servers. It cannot connect a local server that talks over standard input. Local servers of that kind read their credentials from the environment instead.

SAP builds the same idea into Joule Agents. Each agent has its own identity, and all traffic passes one gateway. So an agent can only do what the user behind it may do, SAP says.

Where a custom agent fits next to SAP’s servers

An MCP server hands an agent tools. It does not decide which order to draft or who approves it. That is the agent’s job. Our page on SAP AI agents covers those jobs, and SAP integration covers each SAP product’s API.

Our team has taken SAP Business One, SAP S/4HANA and SAP ECC live, and we can run an SAP implementation end to end. The first call is free.

Questions

Does SAP have an official MCP server?

Yes, SAP supports or publishes several, and each fits one product. SAP Business One 10.0 FP 2608 supports an open-source MCP server for the Service Layer, and SAP gives sample code for it. SAP Integration Suite can publish your own APIs as MCP servers. SAP's GitHub servers for CAP and UI5 help developers write code. We found no single SAP server that covers every SAP system.

What is MCP vs API?

An API is the door into a system. MCP is a shared way for AI agents to find and use those doors. SAP's own explainer calls MCP a complement to API management. With a plain API, a developer has to know each endpoint in advance. An MCP server lists its tools, so the agent can discover what it may call.

What is SAP BTP called now?

SAP's product page still says SAP Business Technology Platform, or SAP BTP. The same page says BTP capabilities are now a core part of SAP Business AI Platform. SAP also calls Integration Suite, where its MCP server tools live, part of that platform. So you may see both names on SAP pages for the same tools.

What does SAP stand for?

SAP's history page gives the founding name. Five former IBM employees started the company on 1 April 1972 as SystemAnalyse Programmentwicklung. In English, that is System Analysis Program Development. Today SAP sells several ERPs. SAP says Business One is for small and midsize firms, and S/4HANA Cloud is for firms of all sizes.

Can SAP be replaced by AI?

SAP's own pages describe AI that works inside the ERP. For SAP Cloud ERP, public and private, SAP's RISE page says embedded AI creates objects, triggers workflows and commits transactions under the same controls that apply to people. MCP fits that plan. The agent reaches SAP through a server that decides which actions are open, SAP's MCP explainer says.

Which SAP Integration Suite plans include the MCP server?

SAP's tutorial, updated on 2 November 2026, says the MCP Server artifact is only on the Enhanced, Premium and Trial plans. SAP's MCP Gateway tutorial names the Premium or Enhanced Edition for live use in its intro, and the Enhanced Edition alone in step 1, so confirm the edition with SAP. Both tutorials run on the Integration Cell runtime. SAP says setting up that runtime can take up to 30 minutes.

Is a community SAP MCP server safe to use?

Treat it like any outside code, because SAP does not ship it. The mcp-abap-adt server, for example, says its 16 tools are read-only, and it signs in with an SAP user name and password. The mcp-integration-suite server calls itself experimental. The MCP rules say a person should be able to deny tool calls. Try any server on a test copy of SAP first.

Sources

Every source behind a figure or a vendor fact on this page, with the day we read it.

Plan an MCP link to your SAP system

Bring your SAP product and release, and the jobs you want an agent to do. The first call is free.

Book an SAP MCP call