ServiceServiceA BTP service you subscribe to and bind, rather than install. It has plans and regions, not versions, and may deliver a product that lives outside the atlas.See every one →What this type is →by SAPby SAPPublished by SAP itself. A visible facet, never an input to a reading — a dormant official plugin reads exactly like a dormant independent one.See every one →
API Management
API proxies in front of backend services, with security and traffic management policies attached to them, and Developer Hub where consumers subscribe.
API Management puts an API proxy in front of a backend service, and policies attached to the proxy decide who may call it and how often: authentication and authorisation, quota, surge protection, IP filtering, JSON and XML threat protection. The backend can sit in the cloud, in a private cloud or on premise, and the apim-as-route-service plan binds a proxy to a Cloud Foundry application's route, so the policies run even when the application's own URL is called. Consumers find an API in Developer Hub, read its documentation, test it and subscribe. It is activated as a capability inside SAP Integration SuiteSAP Integration SuiteSAP's integration service on BTP: Cloud Integration for orchestration, API Management in front of it, and an MCP gateway that serves a managed API to agents.sap official, btp and runs on one of three runtimes: Classic API Management, Integration Cell, or the customer-managed Edge Integration Cell.
Where it sits
Lives in
Provides
Rate limitingCAPBTPRate limitingCapping how many requests a service will accept per tenant or per caller, so one consumer cannot exhaust a shared deployment, whether enforced by a policy in front of the application or inside its own process.Serve your application over MCPCAPBTPServe your application over MCPExposing selected application data and business operations to an AI agent through the Model Context Protocol. An application may also integrate remote services through [service integration](capability:service-integration), connecting its exposed contract with [agent access to your systems](capability:agent-systems-access). Development assistance belongs to [agent access to your code](capability:agent-code-access).Tool governanceCAPBTPTool governanceControlling what an agent may call, with which authorisations, and leaving an audit trail of what it did. The authorisation question that MCP exposure raises but does not answer.
Part of
SAP Integration SuiteSAP Integration SuiteSAP's integration service on BTP: Cloud Integration for orchestration, API Management in front of it, and an MCP gateway that serves a managed API to agents.
Serves
Designs
Multitenant SaaS Application using CAPMultitenant SaaS Application using CAPAPI policies per plan
Who is behind it
SAPSAPMaintains this
In the atlas: maintains 137, wrote 14@SAPmaintainer
In the atlas: maintains 137, wrote 14@SAPmaintainer
Before choosing this
Conditions
PolicySAP API Policy 4.2026a§ 1.1, 1.2, 2.2.2from Serve your application over MCPAn MCP server exposes an SAP API, or uses SAP APIs to supply tools, resources or data to an agent.
- § 1.1 Published APIs. Published APIs are made available for the documented purposes identified by SAP, including integration, extensions and data exchange.
- § 1.2 Non-Published APIs. Customer and third-party applications must not access non-published APIs except where documentation permits it or SAP otherwise authorizes it.
- § 2.2.2 AI call sequences and data extraction. Outside SAP-endorsed architectures, data services or expressly identified pathways, the policy prohibits specified agentic API use and systematic or large-scale extraction.
MCP does not replace the API's documented-use boundary. Check that every endpoint is published for the intended use and whether the policy's AI-call or extraction provisions apply to the design.
SAP API Policy 4.2026a →LicenceSAP Developer License Agreement 3.2 CAP§ 1, 3from Serve your application over MCPA covered CAP plugin or application exposes SAP product data or covered customer-application functionality through MCP.
- § 1 License. Productive customer applications are limited to SAP BTP or another SAP-licensed platform, and mass extraction to a non-SAP product is restricted except where solely required for SAP interoperability.
- § 3 Artificial Intelligence Training. The agreement prohibits use of the covered materials and customer applications for training artificial-intelligence models or systems.
The CAP developer agreement can apply alongside the API Policy. Ordinary agent inference is not automatically AI training; section 3 becomes relevant when covered materials or applications are used to train, develop or refine a model or system.
SAP Developer License Agreement 3.2 CAP →What it declares
Every artifact
- Type
- Service
- Origin
- By SAP
As a service
- Plans
- 2
- Regions
- 3
- Support component
- OPU-APIOPU-API-OD-ANOPU-API-OD-DTOPU-API-OD-RT
For serve your application over MCP
- Exposure source
- API artifactAPI proxyHTTP/OpenAPI endpointRFC backend
- Exposed operations
- Selected source-API operations become tools; retrieval/create/update/delete depend on that API contract
- Context delivery
- MCP resourcesMCP promptsTool input/output schemas
- Execution path
- Remote backend calls
- Exposure control
- API operation selection
Parts and add-ons
Parts 1
API CompositionOne API over the business data in a landscape: a business data graph queried with OData V4 or GraphQL, instead of each source system's own API.
Connections
Group by
NodeRelationBasis
Functional
Rate limitingRate limitingCapping requests per tenant or callerSAP and community, unassessed
provides
stated
provides Rate limiting
Two policies attached to an API proxy, in front of the application and outside its process. Quota counts the requests an application submits to an API over a period and rejects every call once the counter reaches the limit. Spike Arrest keeps no counter: it spaces requests by the time the last one passed, on each API Management server separately, and SAP's page says to set it to what the backend can handle and not to use it to limit individual clients. A third policy, Concurrent Rate Limit, is decommissioned and can no longer be added to a proxy.
“The Quota policy defines the number of request messages an application can submit to an API over a given period of time.”“Once the counter reaches the Quota limit, all successive calls made to the API are rejected.”“No counter is maintained for spike arrests, only the time that the last message was successfully passed through the Spike Arrest policy is maintained.”“Do not use Spike Arrest policy to limit traffic from individual clients.”“You can no longer create or update an API proxy with Concurrent Rate Limit policy.”
Capping requests per tenant or caller
Serve your application over MCPServe your application over MCPExposing application data and operations to agents over MCPSAP and community, narrow by design
provides
stated
provides Serve your application over MCP
Creates an MCP server from an Integration Cell OData/REST API artifact, a classic API proxy, an HTTP OpenAPI endpoint or an RFC backend, with selected operations exposed through the MCP gateway. MCP deployment requires Integration Cell even when a source proxy runs on the classic runtime; API-artifact sources must use OAuth and the HTTP specification must be OpenAPI 3.0.0–3.0.3. The gateway routes backend API calls, and selected API operations become tools with input/output schemas. Resources have URI/MIME schemas, prompts guide agent interactions with tools, and HTTP-endpoint configuration requires Authentication and Authorization policies. The API-artifact and HTTP-endpoint creation guides state a limit of 30 tools per MCP server, while the HTTP-endpoint configuration guide states 50.
“In SAP Integration Suite, the MCP Server capability is realized through the MCP gateway.”“Create an MCP server from any HTTP endpoint by providing the endpoint URL and an OpenAPI specification.”“Create an MCP server from an RFC-based backend by modeling and exposing RFC operations as MCP tools.”“You can create an MCP server directly from an existing API proxy deployed on the classic API Management runtime.”“Activate API Management capability.”“The MCP server can be only deployed and managed over Integration Cell runtime profile.”“Each MCP server supports up to 30 tools.”“SAP Integration Suite offers multiple API Management runtimes to address different deployment and operational needs.”“Activate API Management capability.”“Activate API Management capability.”“Only APIs with OAuth-based authentication can be used to create an MCP server.”“The OpenAPI specification must be a version between 3.0.0 and 3.0.3.”“Each MCP server supports up to 50 tools.”“Only OData and REST API artifacts deployed on the Integration Cell runtime can be discovered”“You can create an MCP server directly from an existing API proxy deployed on the classic API Management runtime.”“exposing selected RFC operations as MCP tools.”“They are derived from API operations and can represent actions such as retrieving, creating, updating, or deleting data.”“add or manage tools, resources, and prompts available to AI agents.”“Review the resource schema derived from the API operation. The resource schema defines the URI template used to access the resource and the MIME type of the content returned.”“Review the input schema and output schema derived from the API operation.”“Defining prompts to guide how agents interact with these tools”“The MCP gateway acts as the runtime layer that exposes enterprise APIs, tools, and backend services as MCP-compatible endpoints for AI agents.”“In *Create Tools*, select the API resource you want to expose as MCP tools.”“Select the API operations that you want to expose as tools based on the HTTP method and resource path”“By default, Authentication and Authorization policies are applied to an MCP server. These policies are mandatory and cannot be deleted.”“Create an MCP Server from any HTTP endpoint by providing its OpenAPI specification.”“Each MCP server supports up to 30 tools.”
Exposing application data and operations to agents over MCP
Tool governanceTool governanceControlling what an agent may call, with an audit trailSAP and community, unassessed
provides
stated
provides Tool governance
An agent's calls pass through the MCP gateway, which shares security, traffic management and multi-protocol connectivity with the API gateway that other API consumers go through, so an MCP server takes the same kinds of policy as a managed API.
“It provides capabilities such as security, traffic management, routing, and multi-protocol connectivity while enabling governed access to enterprise systems”“Both gateways share common capabilities such as security, traffic management, and multi-protocol connectivity.”“the *Policies* tab to configure traffic management and security policies”
Controlling what an agent may call, with an audit trail
Lineage
API CompositionAPI CompositionBusiness data graph queried with OData V4 or GraphQLsap official, btp
has part
derived
has part API Composition
Business data graph queried with OData V4 or GraphQL
SAP Integration SuiteSAP Integration SuiteIntegration service on BTP with Cloud Integration and API Managementsap official, btp
part of
stated
part of SAP Integration Suite
“The API Management capability within SAP Integration Suite allows you to utilize SAP's internal API providers as well as external APIs, regardless of whether they are SAP-related or not.”“SAP Integration Suite brings together the features and functionality of various capabilities such as:”“You've enabled API Management capability using SAP Integration Suite and have completed the setup.”
Integration service on BTP with Cloud Integration and API Management
Download
Learn more
Readings
- Powering Enterprise-Ready Agentic AI with SAP Integration SuitePowering Enterprise-Ready Agentic AI with SAP Integration SuiteA Devtoberfest 2026 session (INT-31) from SAP Integration Suite product management on the MCP gateway. The demo creates an MCP server in a design package from an API already deployed on the tenant, exposes two of its 300-odd resources as tools, attaches authentication and quota policies on a policies tab, and publishes the deployed endpoint as an AI product in Developer Hub of API Management, where an agent subscribes and receives a token, URL, key and secret; the calls then show up in monitoring, in message processing logs and in the analytics dashboard, which is the MCP exposure and the tool governance the edges rest on. Three AI features inside Cloud Integration follow: a content migration agent that converts a PI/PO Java mapping into a Groovy script and generates a second integration flow for its lookup, memory profiling during a flow simulation, and root-cause analysis on a failed message processing log.SAP Developers, published 2026-10-07SAP Developers, YouTube — SAP Developers playlists
- 🔴 Your Agent Wants to Call SAP. Now What?🔴 Your Agent Wants to Call SAP. Now What?Devtoberfest 2026 session INT-23, on what belongs between an agent and an SAP system. A solution advisor and an enterprise architect point Joule Desktop extensions at MCP servers built on API Management inside SAP Integration Suite, and ask it for business partners, orders and line items from an S/4HANA demo system; asked for the ten largest customers it answers from a sample of 200 orders rather than reading the whole table. They then open the API proxy behind it, where a spike arrest policy caps the backend at ten calls per second and the MCP server is configured to expose only the GET resources of the business-partner API so that an agent cannot create one, which is where the edges to Serve your application over MCP and Rate limiting hold. For totals across all sales orders they send the agent to SAP Business Data Cloud instead of the transactional system, since it aggregates and is read-only, and back through Integration Suite for writes such as journal entries.SAP Developers, published 2026-09-30SAP Developers, YouTube — SAP Developers playlists
- API Composition: Seamless Enterprise Data Access for Developers and AI AgentsAPI Composition: Seamless Enterprise Data Access for Developers and AI AgentsAPI Composition (formerly Graph, a capability of API Management) curates business data graphs from existing SAP and non-SAP API providers, so a query can navigate and expand relationships across systems through one composed API rather than hand-written integration code. Palak walks through combining SAP S/4HANA warehouse-stock data with Everstream Analytics risk data into one API, then exposing that composed API as an MCP server so an AI agent calls it with the same semantic context — the scenario behind API Management's MCP servers coverage.published 2026-07-27Palak, SAP Community
7 more
- Graph on Integration Suite: Simplifying Multi-API Data Retrieval with Unified Business Data GraphGraph on Integration Suite: Simplifying Multi-API Data Retrieval with Unified Business Data GraphA hands-on walkthrough of Graph, the API Management feature of SAP Integration Suite also called Business Data Graphs, which exposes several OData APIs as one connected data model behind a single OData V4 or GraphQL endpoint. It covers enabling the capability and its Graph.KeyUser and GraphNavigator.Viewer role collections, creating BTP destinations and a service key for an S/4HANA system, then building a Business Data Graph over the Sales Order and Business Partner APIs so a mirrored SoldToParty association returns both in one call, in place of the two OData requests a Cloud Integration Content Enricher would otherwise merge.published 2026-01-09azhariqbal, SAP Community
- SAP PI Migration to BTP Integration Suite Patterns and learning experiencesSAP PI Migration to BTP Integration Suite Patterns and learning experiencesWalks through the integration patterns an SAP PI migration project moved onto SAP Cloud Integration iFlows — API Management proxies fronting calls into on-premise SAP systems over XI/SOAP via Cloud Connector, SFTP transfers, and eventing routes — and the operational lessons from running it: sizing JMS queues, choosing exactly-once JMS queues over Cloud Integration's Data Store for XI receiver adapters and at-least-once JMS for XI sender adapters, and workarounds for gaps in the migration tooling. The API Management proxies handle JWT validation against a non-SAP identity provider, IP filtering and OData-to-OpenAPI conversion in front of the iFlows.saikrishna_kalivarapu2, published 2024-12-04saikrishna_kalivarapu2, SAP Community
- Information Map – Introduction Series: Graph in SAP Integration SuiteInformation Map – Introduction Series: Graph in SAP Integration SuiteIntroduces Graph, an enhancement to API Management within SAP Integration Suite that gives developers a single API onto an organisation's business systems, modelled as one semantically connected business data graph, later renamed API Composition. Splits the work between an administrator, who enables SAP BTP destinations to the backend systems and builds the business data graph, and a developer, who explores it in the Graph Navigator tool and builds an application against the resulting Graph API.published 2024-02-21Palak, SAP Community
- Edge Integration Cell : Design, deploy and manage APIsEdge Integration Cell : Design, deploy and manage APIsWalks through creating an API artifact in API Management on the customer-managed Edge Integration Cell runtime, including the option to generate the artifact by importing an OpenAPI specification rather than from a URL or by hand. It then attaches an Authentication policy and a Quota step capped at four calls per minute, deploys, and shows both the resulting 401 and the quota-breach error in the Monitor logs. The author frames it as the first of a series on Edge Integration Cell's policies.published 2023-11-15Ashutosh Kumar Singh, SAP Community
- MCP Gateway in Practice: Architecture, configuration, and hands-onMCP Gateway in Practice: Architecture, configuration, and hands-onA Devtoberfest 2026 integration-track session (INT-21) on the MCP gateway of SAP Integration Suite: curated enterprise APIs served to agents as MCP tools over JSON-RPC, behind the authentication, authorization and traffic policies an API artifact already carries, with the existing API layer left in place. The hands-on half composes S/4HANA plant, material-stock and supplier data with a non-SAP location-risk source into one business data graph, downloads its OpenAPI specification, creates an MCP server artifact with tools, prompts and a surge-protection policy over that endpoint, and publishes it as a product in Developer Hub of API Management, where an agent developer subscribes and gets OAuth credentials. An MCP client then asks for 15 brake pads and ranks plants by stock, location risk and distance from Walldorf, which is what the agent access to your systems edge rests on; the Q&A covers principal propagation to the backend, how errors reach the model, and which Integration Suite editions carry the gateway.SAP DevelopersSAP Developers, YouTube — SAP Developers playlists
- Modern integration at TÜV Rheinland: APIs, events and cloud transformationModern integration at TÜV Rheinland: APIs, events and cloud transformationTÜV Rheinland's migration from SAP Process Orchestration to SAP Integration Suite with API-led connectivity and event-driven architecture, told through business cases. The abstract names what was used: the SAP Integration Suite, Event Mesh capability, API Management, generative AI for faster development and SAP Cloud ALM for monitoring. It states nothing about how any of them was used, so the edges rest on the names and on the Platform migration the story starts from. A TechEd 2026 session (Wednesday 28 October, Berlin), written here from SAP's abstract; the recording is not yet published.Manisha Debnath, Udo Paltzer, SAP TechEd — session catalogue
- Road map for SAP Integration Suite: What ships next across all capabilitiesRoad map for SAP Integration Suite: What ships next across all capabilitiesSAP's road map for SAP Integration Suite across its capability areas: API Management, event-driven integration, business process and trading partner integration, and hybrid runtimes for SAP and third-party systems. The abstract promises recent deliveries and the planned innovations that make the platform agent-ready within SAP Business AI Platform; it names the areas and no shipping item, so the edges rest on the product and the one area it names by a product name. A TechEd 2026 session (Thursday 29 October, Berlin; also IN804V, virtual), written here from SAP's abstract; the recording is not yet published.Shilpa Vij, Udo Paltzer, SAP TechEd — session catalogue
Others providing
Rate limitingRate limitingCapping how many requests a service will accept per tenant or per caller, so one consumer cannot exhaust a shared deployment, whether enforced by a policy in front of the application or inside its own process.SAP and community, unassessed
- @cap-js-community/common@cap-js-community/commonSix independent features for CAP services in one package: replication cache, migration check, rate limiting, a Redis client broker, a local HTML5 repository and a CDM builder.community org, capSix CAP features in one package, from replication cache to rate limits
- cds-rate-limitcds-rate-limitA CAP plugin that applies a rate-limit pattern inside the CAP Node.js runtime, capping how many requests a caller gets where tenant and user are already resolved rather than at an approuter or gateway.independent, capRate-limit pattern for CAP Node.js applications
Serve your application over MCPServe your application over MCPExposing selected application data and business operations to an AI agent through the Model Context Protocol. An application may also integrate remote services through service integration, connecting its exposed contract with agent access to your systems. Development assistance belongs to agent access to your code.SAP and community, narrow by design
- com.sap.cds:cds-adapter-mcpcom.sap.cds:cds-adapter-mcpThe MCP protocol adapter for CAP Java, serving an @mcp-annotated Application Service as an MCP server with three generated tools, describe, query and call, and data changes only through unbound actions.sap official, capMCP adapter turning a CAP Java service into an MCP server
- @cap-js/mcp@cap-js/mcpA CAP plugin that serves an @mcp-annotated service over MCP with three generated tools, describe, query and call_action, and writes its endpoint into the local agent's configuration in development.sap official, capExposes CAP services as MCP servers for AI agents
- @gavdi/cap-mcp@gavdi/cap-mcpGenerates an MCP server from the CDS model — annotated entities become resources and annotated actions become tools, so an agent reaches the service without a second server being written.independent, capGenerates an MCP server from annotated CDS entities and actions
- @neoimpulse/cap-js-mcp@neoimpulse/cap-js-mcpAn MCP server inside a CAP application, with default tools that read the running model and query entities, plus configurable application tools, prompts and resources.independent, capMCP server inside a CAP application with model and query tools
- @odatano/core-mcp@odatano/core-mcpMCP server exposing ODATANO — the Cardano-to-OData bridge built on CAP — to an agent, so the chain is reachable as tools rather than as a REST client.independent, capMCP server exposing the ODATANO Cardano-to-OData bridge as tools
- @odatano/nightgate-mcp@odatano/nightgate-mcpMCP server exposing NIGHTGATE, the Midnight blockchain attestation layer, as agent tools — the companion to the CAP indexer plugin of the same name.independent, capMCP server exposing the NIGHTGATE Midnight attestation layer
- @shahid.la/cds-db-nlquery-mcp@shahid.la/cds-db-nlquery-mcpMCP server that answers plain-English questions against the entities in db/schema.cds — it discovers the schema, generates CQN-backed SQL with real joins, and returns rows.independent, capMCP server answering plain-English questions against a CDS schema
- cap-mcp-plugincap-mcp-pluginGenerates an MCP server from a CDS model: annotated entities become MCP resources, functions and actions become tools, and services can expose reusable prompt templates. A fork of @gavdi/cap-mcp that adds an OAuth proxy, IAS client registration and draft-lifecycle tools.independent, capMCP server generated from a CDS model, forked from @gavdi/cap-mcp
Tool governanceTool governanceControlling what an agent may call, with which authorisations, and leaving an audit trail of what it did. The authorisation question that MCP exposure raises but does not answer.SAP and community, unassessed
- a2a-plugina2a-pluginExposes an annotated CDS service as an Agent-to-Agent protocol agent — @a2a opts the service in, @a2a.Skill declares what it offers, and an agent handler answers.independent, capExposes an annotated CDS service as an Agent-to-Agent agent
- SAP API Policy Evidence SkillSAP API Policy Evidence SkillAssesses whether a described SAP API usage aligns with the SAP API Policy, gathering live evidence from SAP's own sources and returning a sourced assessment with a stated confidence — and routing the legal questions away from itself.independent, btpSkill assessing API usage against the SAP API Policy
- cds-agentscds-agentsTurns a CAP service into a tool layer for agent frameworks — a CAPToolkit bound to a named service, with a tool strategy controlling how much of it becomes callable.independent, capToolkit turning a CAP service into tools for agent frameworks
Details
Sources
Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.
Compatibility and provenance
discovered viaAdded by hand
first seen in the atlas
ecosystem and domainbtp, integration-and-messaging
History in the atlas
- [{"key":"mcp_exposure_source","value":"Integration Cell OData/REST API artifact, classic API proxy, HTTP OpenAPI 3.0.0–3.0.3 or selected RFC backend"},{"key":"mcp_operations","value":"Selected source-API operations become tools; retrieval/create/update/delete depend on that API contract"},{"key":"mcp_context","value":"Resource URI/MIME schemas, prompt templates and API-operation tool input/output schemas"},{"key":"mcp_execution_path","value":"MCP gateway routes backend API calls; MCP server deployment is Integration Cell-only even when the source proxy uses the classic runtime"},{"key":"mcp_exposure_control","value":"Select API operations/resources for tools and configure resources/prompts; HTTP-endpoint configuration requires Authentication and Authorization policies"}]
- API artifact; API proxy; HTTP/OpenAPI endpoint; RFC backend
- MCP resources; MCP prompts; Tool input/output schemas
- Remote backend calls
- API operation selection
- A deployment with a hard tool-count requirement needs its limit confirmed: the API-artifact and HTTP-endpoint creation guides state 30 tools, while the HTTP-endpoint configuration guide states 50.
- Creates an MCP server from an Integration Cell OData/REST API artifact, a classic API proxy, an HTTP OpenAPI endpoint or an RFC backend, with selected operations exposed through the MCP gateway. MCP deployment requires Integration Cell even when a source proxy runs on the classic runtime; API-artifact sources must use OAuth and the HTTP specification must be OpenAPI 3.0.0–3.0.3. The gateway routes backend API calls, and selected API operations become tools with input/output schemas. Resources have URI/MIME schemas and prompts use templates. HTTP-endpoint configuration requires Authentication and Authorization policies.
- Removed; the documented 30/50 MCP tool-limit discrepancy is retained on provides[mcp-servers].what_it_does.
- Creates an MCP server from an Integration Cell OData/REST API artifact, a classic API proxy, an HTTP OpenAPI endpoint or an RFC backend, with selected operations exposed through the MCP gateway. MCP deployment requires Integration Cell even when a source proxy runs on the classic runtime; API-artifact sources must use OAuth and the HTTP specification must be OpenAPI 3.0.0–3.0.3. The gateway routes backend API calls, and selected API operations become tools with input/output schemas. Resources have URI/MIME schemas, prompts guide agent interactions with tools, and HTTP-endpoint configuration requires Authentication and Authorization policies. The API-artifact and HTTP-endpoint creation guides state a limit of 30 tools per MCP server, while the HTTP-endpoint configuration guide states 50.
- capability:mcp-servers, capability:tool-governance
- First seen.
For your agent
- Ref
artifact:btp-api-management- JSON
- /artifacts/btp-api-management.json
- MCP
- Connecting an agent