SAP MCP Gateway and Joule Studio MCP servers: what they expose, what access they need, how to connect

SAP's route is build-it-yourself: an MCP Gateway in Integration Suite hosts MCP servers over the APIs you choose, read or write, with OAuth. SAP has no public endpoint. Verified 21 Oct 2026.

There is no ready-made SAP endpoint to paste into Claude or ChatGPT. Your SAP BTP team builds and governs each MCP server, and SAP documents Microsoft Copilot Studio as the client.

Official MCP Gateway (SAP Integration Suite, remote, customer-built) · read and write, per the APIs you expose

Hosting: Remote, inside your own SAP BTP subaccount: the MCP Gateway in SAP Integration Suite hosts the MCP servers you create, over Streamable HTTP. SAP publishes no shared URL and no open-source repo.
Auth: OpenID Connect and OAuth 2.0, enforced by the gateway, with users resolved through SAP Cloud Identity Services (IAS). SAP's Copilot Studio pattern uses the authorization code flow with a user-delegated token.
Read / write: Read and write, depending on which SAP APIs and integration flows your team exposes. SAP's examples include read lookups and writes such as creating an expense report.
Works with: Microsoft Copilot Studio is the documented client; SAP says any MCP-compatible agent can use the tools. Claude.ai, Claude Code and ChatGPT steps are not documented by SAP.
Plan requirement: SAP BTP with SAP Integration Suite and the MCP Gateway capability; SAP says MCP feature availability depends on the service plan. SAP's reference architectures don't label the MCP Gateway GA or beta, and SAP doesn't document Joule Studio licensing on the pages we checked.
Last changed: 2026-10-14: SAP's A2A and MCP interoperability reference architecture updated
Verification: Verified 21 Oct 2026 by theFinanceStack · confidence: medium

What can an agent do with SAP through MCP?

It can call whichever SAP APIs, integration flows or external MCP servers your BTP team has published through the MCP Gateway, so it can read and, if you expose write APIs, create or change records in S/4HANA and other SAP systems.

SAP does not ship a fixed finance tool list.

Where it runs

Option	What it does
MCP Gateway	A managed layer in SAP Integration Suite. It turns APIs you select, from SAP or other systems, into MCP servers under one governed entry point. SAP's reference architecture names S/4HANA, SuccessFactors, Concur, Customer Experience and Business Data Cloud as targets.
Joule Studio	Separately, it can generate SAP-managed MCP servers for Joule agents from SAP's API catalog.

How writes behave

SAP doesn't document whether gateway tools post or draft.
A create or update call through a standard API generally commits when it runs. Treat every exposed write API as posting immediately unless you have confirmed it creates a draft.
SAP warns that writes over raw transactional APIs risk incorrect business transactions.

Money

SAP doesn't publish a list of tools that move money.
Check every exposed API for payments, approvals and releases before going live.

Can

Read SAP data through exposed APIs; SAP's examples include purchase order status and approvers, inventory levels and reimbursement status (gateway)
Write to SAP through exposed APIs; SAP's examples include creating an expense report, submitting a request and approvals (gateway)
Expose SAP and non-SAP APIs, integration flows and custom MCP servers through one governed entry point, with rate limiting and monitoring (gateway, per SAP)
Give Joule agents SAP-generated MCP servers, with SAP handling upgrades and patching (Joule Studio)

Cannot

Connect without setup: SAP publishes no public MCP endpoint, so nothing works until your BTP team builds a server
Add business context on its own: SAP says MCP "does not add business context or improve the accuracy of AI results"
Act beyond the signed-in user's SAP roles in the delegated pattern; per SAP, the backend enforces that user's authorizations
Delegate to SAP's own agents from outside SAP yet: SAP says its Agent Gateway, the recommended A2A route, is not yet generally available

What access does it get?

In SAP's documented pattern the agent acts as the signed-in SAP user: a user-delegated OAuth token is resolved through SAP Cloud Identity Services and the backend applies that user's existing roles. SAP publishes no named MCP scopes.

Where	Scopes and permissions (as documented)	Admin requirement
MCP Gateway in SAP Integration Suite (remote, in your BTP subaccount)	Not documented by the vendor as named MCP scopes. OpenID Connect and OAuth 2.0 at the gateway; the token maps to an SAP user whose roles apply. For custom servers SAP asks for an RFC 8693 token exchange that grants only the minimum permissions per tool.	A BTP subaccount with Integration Suite and the MCP Gateway enabled, plus admin access to SAP Cloud Identity Services and your corporate identity provider (e.g. Entra ID) to set up trust.
Joule Studio SAP-managed MCP servers (for Joule agents)	Not documented by the vendor. SAP says authentication and governance are built in.	Joule Studio on SAP BTP; SAP doesn't document Joule Studio licensing or roles on the pages we checked.

How do I connect it?

Your SAP BTP team builds the server and the trust setup first; SAP's documented client is Microsoft Copilot Studio. SAP lists these prerequisites: a BTP subaccount with Integration Suite and the MCP Gateway capability enabled; the SAP APIs you want as OData/REST services or integration flows; and admin access to your identity provider (e.g. Entra ID) and SAP Cloud Identity Services. SAP describes three configuration areas: SAP BTP (the gateway and server), the identity providers (trust and app registrations), then the agent client.

SAP doesn't document Claude.ai as a client as of 21 Oct 2026; its May 2026 Anthropic announcement covers plans for Claude inside Joule. SAP says gateway tools are available to any MCP-compliant agent, so the standard Claude mechanic would be Customize › Connectors › Add custom connector with your gateway URL (Team/Enterprise: an Owner adds it). SAP doesn't document the OAuth client registration (redirect URI, client ID and secret in SAP Cloud Identity Services) for Claude.

What should a finance team watch for?

The biggest watch-point: your team decides which APIs become tools, and SAP ships no fixed tool list. A write or payment API exposed by mistake is live for every agent that connects.

SAP warns that connecting raw transactional APIs through MCP risks high token use and, for writes, incorrect business transactions. It advises starting read-only and enabling writes once confidence is established.
Expose the narrowest APIs you need, prefer user-delegated sign-in over shared service accounts (SAP's own advice) and leave payment, release and approval APIs off unless a person approves each call. For custom servers SAP requires an RFC 8693 token exchange "scoped to the minimum permissions required by the specific tool", keeping the original user context for audit.
SAP says MCP-level rate limits must not exceed the underlying SAP API quotas, and advises per-consumer limits where several agents share one MCP entry point.
For customer-built servers, SAP puts security, availability, upgrades and compliance on the customer, and notes a coming MCP revision with breaking changes.
SAP says an MCP server should never store long-lived credentials; keep secrets in SAP Credential Store or a similar vault and rotate them.
Supplier names, invoice texts and notes are free text the agent reads. An injected instruction there could push it to approve, post or pay, so keep human approval on for every write.
SAP's MCP pages don't address AI training or retention; check your SAP agreement and your AI provider's terms.

How could finance teams and accounting firms use it?

Start with read-only APIs for questions and reporting, as SAP recommends, and add drafting uses only where a person approves the change in SAP.

Inside a company

Ask for purchase order status and the current approver before chasing a supplier.
Summarise revenue variance by region (an SAP example) or check inventory levels for a month-end discussion, through read-only APIs.
Prepare an expense report or request through a write API, then have the owner review and approve it in SAP.
Answer one reporting question from SAP data and a non-SAP API exposed through the same gateway.

At an accounting firm

Answer a client's questions from their own S/4HANA data. SAP doesn't document adviser access; in its pattern the adviser would need an identity in the client's identity provider (e.g. Entra ID) and an SAP user with limited roles.
Review which APIs a client has exposed as MCP tools and flag any that post or pay, as part of a controls engagement.
Draft variance commentary from read-only data for partner review.
Check reimbursement or approval status during a client meeting instead of waiting for an export.

Anything that posts to the ledger, approves or pays stays with a person who approves it in SAP.

Want SAP connected to Claude for your team?

We configure scoped connections and a review step before anything changes your books. Fixed fee.

Book a 30-minute setup call

Change log

Date	Change	Source
2026-10-14	A2A and MCP interoperability reference architecture updated; MCP availability depends on service plan	architecture.learning.sap.com/docs/ref-arch/76ec36
2026-06-18	Copilot Studio and MCP Gateway reference architecture updated: OAuth authorization code flow, Streamable HTTP	architecture.learning.sap.com/docs/ref-arch/d2e34e
2026-06-08	Third-party MCP access reference architecture updated: MCP Gateway and Joule Studio MCP servers described	architecture.learning.sap.com/docs/ref-arch/137800
2026-05-12	SAP and Anthropic announce plans to bring Claude into Joule and the SAP Business AI Platform, with agents reaching SAP systems via MCP	news.sap.com/2026/05/sap-anthropic-to-bring-claude-sap-busin

FAQ

Is this official?

Yes. The MCP Gateway is part of SAP Integration Suite and is described in SAP's own reference architectures. Your team builds the servers on it. SAP doesn't host a single shared endpoint.

Is it free?

SAP doesn't list a separate MCP price. You need SAP BTP with Integration Suite, and SAP says MCP feature availability depends on your service plan. SAP doesn't document Joule Studio licensing on the pages we checked.

Does it change data in SAP?

It can. Any write API your team exposes becomes a tool. SAP doesn't document whether these post or draft. A standard create call generally commits when it runs. SAP warns that writes risk incorrect business transactions and advises starting read-only.

Is my data used to train models?

SAP's MCP pages don't say. Check your SAP agreement and your AI provider's terms; the model sees whatever the exposed APIs return.

Can my accountant use it on my behalf?

SAP doesn't address this. In the delegated pattern each call runs as the signed-in SAP user, so an adviser would need their own SAP user with suitably limited roles.

Something wrong or out of date? Tell us and we'll email you when it's fixed.

Sources

Verified by theFinanceStack, 21 Oct 2026. Vendor list on the CFO Software Market Map courtesy of Jason Staats; AI connectivity data by theFinanceStack. Not tax, compliance or financial advice.