MCP for SAP — Adoption & Integration Strategy

The question this card answers

MCP (Model Context Protocol) collapses AI-to-tool integration from N×M bespoke connectors to N+M: each tool is wrapped once as an MCP server, each AI host implements one MCP client. That arithmetic is real, but in an SAP landscape it is no longer the deciding factor. Since April 2026 the deciding factor is which pathway is allowed, and since the MCP spec revision of 2026-07-28 the second factor is which server you can operate for years. This card is the adoption strategy; C164 covers the mechanics (roles, identity chain, configuration) and C132 the boundary with A2A.

The rule that changed the game: SAP API Policy v.4.2026a

The SAP API Policy is part of the Documentation of every SAP solution. Section 1 separates Published APIs (on SAP Business Accelerator Hub or in product documentation) from non-published ones, which customer and third-party applications must not call except where the documentation allows it — custom-developed ABAP interfaces in private cloud and on-premise remain permitted. Section 2.2.2 is the one every MCP project must read: except through and within the limits of SAP-endorsed architectures, data services or service-specific pathways, SAP prohibits API use for interaction with (semi-)autonomous or generative AI systems that plan, select or execute sequences of API calls, and for large-scale extraction. Section 3 lets SAP throttle or suspend access and forbids circumventing controls through proxies or gateways.

Why it matters

• Since SAP API Policy v.4.2026a, agentic use of SAP APIs is prohibited outside SAP-endorsed pathways — the first MCP design question is legal, not technical.
• SAP now delivers official MCP servers in four families (Integration Suite gateway, remote SAP-operated servers, developer-tooling servers, CAP adapter); community servers carry no SAP support.
• The N×M → N+M argument only pays off when several AI clients will reuse the same tools — for a single internal agent a direct function call stays cheaper.

Key points

• MCP turns N assistants × M tools into N+M integrations; the payoff comes from reuse across heterogeneous AI clients.
• SAP API Policy v.4.2026a §1: only Published APIs for documented use; custom ABAP interfaces remain allowed in private cloud and on-premise.
• §2.2.2: agentic (plan/select/execute) use of SAP APIs only through SAP-endorsed architectures or pathways; §3: no circumvention via proxies or gateways.
• Endorsed routes cited in SAP's clarifications: Integration Suite MCP gateway, SAP-provided MCP servers via Joule Studio, A2A.
• Official SAP MCP families: Integration Suite MCP Server artifacts, remote SAP-operated servers (BTP administration), development servers (ADT, CAP, UI5, Fiori, MDK), CAP @cap-js/mcp adapter.
• Community servers: security review, owner and exit plan like any third-party integration; watch for shared technical users.
• Register servers in SAP AI Agent Hub (inventory of agents, LLMs and MCP servers) and version tool contracts.

Terms used on this page

MCP (Model Context Protocol)

Open JSON-RPC 2.0 protocol, published by Anthropic in November 2024 and governed since December 2025 under the Linux Foundation's Agentic AI Foundation, through which AI hosts call tools, read resources and use prompts exposed by servers.

Published API

SAP API listed on SAP Business Accelerator Hub or in product documentation; the only kind the SAP API Policy allows for documented use.

SAP-endorsed pathway

Architecture, data service or service-specific route SAP expressly identifies for agentic or large-scale API use (API Policy §2.2.2).

MCP gateway

SAP Integration Suite runtime that serves MCP Server artifacts with OAuth, traffic management and monitoring.

Official vs community MCP server

Official = delivered or operated by SAP with SAP support; community = open-source or partner code with no SAP support, to be reviewed like any third-party integration.

SAP AI Agent Hub

SAP LeanIX-based command center that discovers and governs AI agents, LLMs and MCP servers across SAP and third-party platforms.

Build-once-serve-many

Adoption test: build an MCP server only when several AI clients will reuse the same tools.

Sources

1. SAP API Policy v.4.2026a (PDF)
2. ERP Today — What Customers Need to Know About SAP's API Policy (Sep 2026)
3. SAP Help — SAP Integration Suite: MCP Server
4. CAP documentation — Model Context Protocol Adapter (API Policy note)
5. SAP Community — Public Release of the MCP server for SAP BTP administration
6. SAP Help — ADT: Security Considerations and Recommendations for the ADT MCP Server
7. SAP Help — SAP AI Agent Hub (SAP LeanIX)
8. SAP News — New agentic capabilities on SAP BTP (TechEd, Nov 2025)
9. Model Context Protocol — specification changelog 2026-07-28
10. Model Context Protocol — Introduction
11. Anthropic — Introducing the Model Context Protocol
12. a2a-protocol.org — A2A Specification (protocol boundary with MCP)