ServiceServicetypeA 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 SAPoriginPublished 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 SuiteserviceSAP'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.
Rate limitingBTPCAPRate limitingcapabilityCapping 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 MCPBTPCAPServe your application over MCPcapabilityExposing 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 governanceBTPCAPTool governancecapabilityControlling 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 SuiteartifactSAP'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.
SAPSAPOrganisationMaintains this In the atlas: maintains 137, wrote 14@SAPmaintainer
Before choosing this
crawled
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.1Published APIs. Published APIs are made available for the documented purposes identified by SAP, including integration, extensions and data exchange.
§ 1.2Non-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.2AI 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.
PolicySAP API Policy 4.2026a§ 1.1, 1.2, 2.2.2, 3from Tool governanceAn agent tool calls SAP APIs, or a governance workflow assesses whether a proposed SAP API use is within the policy's documented-use boundary.
§ 1.1Published APIs. Published APIs are made available for the documented purposes identified by SAP, including integration, extensions and data exchange.
§ 1.2Non-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.2AI 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.
§ 3Monitoring and remedies. SAP states that it may monitor API use and take enforcement actions when use does not comply with the documentation and policy.
Technical controls decide what an agent can call; the SAP API Policy separately governs whether the API is published for the intended use and identifies special AI-call and extraction cases. An evidence-gathering tool can assess against that policy but cannot issue a binding compliance decision.
Selected source-API operations become tools; retrieval/create/update/delete depend on that API contract
stated by its maintainer“They are derived from API operations and can represent actions such as retrieving, creating, updating, or deleting data.” MCP Server,
stated by its maintainer“The MCP gateway acts as the runtime layer that exposes enterprise APIs, tools, and backend services as MCP-compatible endpoints for AI agents.” MCP Server,
Change application records from an agentCreate or update application records through an MCP client.Covers, under conditionsmanaged MCP gateway
What it does
API Management, on the assessed HTTP/OpenAPI source path, exposes selected API write operations as MCP tools.
Conditions
Activate API Management and the Integration Cell runtime; assign PI_Integration_Developer and create an integration package.; The selected Integration Suite service plan must include this feature.; For the assessed HTTP source path, supply OpenAPI 3.0.0–3.0.3 and a reachable custom application endpoint or supported destination.
Remaining work
Select the source API operations, configure the destination, tools/resources/prompts and security policies, deploy on Integration Cell and arrange client access.
Expose an application service to an AI agentLet an MCP client discover and query application data and invoke selected business operations.Covers, under conditionsmanaged MCP gateway
What it does
API Management, on the assessed HTTP/OpenAPI source path, creates an MCP server from a custom application HTTP endpoint and its OpenAPI specification.
Conditions
Activate API Management and the Integration Cell runtime; assign PI_Integration_Developer and create an integration package.; The selected Integration Suite service plan must include this feature.; For the assessed HTTP source path, supply OpenAPI 3.0.0–3.0.3 and a reachable custom application endpoint or supported destination.; MCP client access uses OAuth. Authentication and Authorization policies are mandatory and cannot be deleted; Authentication must be first in the request flow.
Remaining work
Select the source API operations, configure the destination, tools/resources/prompts and security policies, deploy on Integration Cell and arrange client access.
Invoke a business operation from an agentInvoke a selected application business operation through an MCP tool.Covers, under conditionsmanaged MCP gateway
What it does
API Management, on the assessed HTTP/OpenAPI source path, exposes selected application API operations as MCP tools.
Conditions
Activate API Management and the Integration Cell runtime; assign PI_Integration_Developer and create an integration package.; The selected Integration Suite service plan must include this feature.; For the assessed HTTP source path, supply OpenAPI 3.0.0–3.0.3 and a reachable custom application endpoint or supported destination.
Remaining work
Select the source API operations, configure the destination, tools/resources/prompts and security policies, deploy on Integration Cell and arrange client access.
Provide application context as MCP resourcesLet an MCP client retrieve application data or schema context through resource URIs.Covers, under conditionsmanaged MCP gateway
What it does
API Management, on the assessed HTTP/OpenAPI source path, supports URI-addressed resources for application data and context.
Conditions
Activate API Management and the Integration Cell runtime; assign PI_Integration_Developer and create an integration package.; The selected Integration Suite service plan must include this feature.; For the assessed HTTP source path, supply OpenAPI 3.0.0–3.0.3 and a reachable custom application endpoint or supported destination.; Only GET API resources can be listed as MCP resources; the HTTP configuration guide states a limit of 15 resources per server.; MCP client access uses OAuth. Authentication and Authorization policies are mandatory and cannot be deleted; Authentication is first in the request flow.
Remaining work
Choose eligible GET resources, configure their URI templates and schemas, secure access and deploy the MCP server on Integration Cell.
Publish reusable MCP promptsLet an MCP client discover and retrieve reusable, parameterized interaction templates.Covers, under conditionsmanaged MCP gateway
What it does
API Management, on the assessed HTTP/OpenAPI source path, supports parameterized MCP prompt templates.
Conditions
Activate API Management and the Integration Cell runtime; assign PI_Integration_Developer and create an integration package.; The selected Integration Suite service plan must include this feature.; For the assessed HTTP source path, supply OpenAPI 3.0.0–3.0.3 and a reachable custom application endpoint or supported destination.
Remaining work
Select the source API operations, configure the destination, tools/resources/prompts and security policies, deploy on Integration Cell and arrange client access.
Query application data from an agentRetrieve selected application records through MCP without changing those records.Shown workingmanaged MCP gateway
What it does
API Management, on the assessed HTTP/OpenAPI source path, exposes selected application API retrieval operations as MCP tools.
Conditions
Activate API Management and the Integration Cell runtime; assign PI_Integration_Developer and create an integration package.; The selected Integration Suite service plan must include this feature.; For the assessed HTTP source path, supply OpenAPI 3.0.0–3.0.3 and a reachable custom application endpoint or supported destination.
Remaining work
Select the source API operations, configure the destination, tools/resources/prompts and security policies, deploy on Integration Cell and arrange client access.
Query related data across APIs from an agentRetrieve related data from several application APIs through one composed interface exposed to an MCP client.Shown workingMCP gateway
What it does
API Management exposes selected operations from the composed graph through an Integration Suite MCP server.
Conditions
Activate API Management and Integration Cell and use a service plan supporting the MCP server artifact.; Provide the composed OData URL/OpenAPI file, select retrieval tools and configure the client subscription/credentials described in the tutorial.
Remaining work
Configure policies, publish/subscribe through Developer Hub and connect the intended client; the Atlas has not executed this sequence.
API Compositionby SAPOne 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.
Connections5
Group by
NodeRelationConditionBasis
Functional3
Rate limitingRate limitingcapabilityCapping requests per tenant or callerSAP and community, unassessed
→provides
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.
provides Rate limiting
Functional, stated
For
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.
Basis
“The Quota policy defines the number of request messages an application can submit to an API over a given period of time.”Quota — SAP Integration Suite documentation, SAP-docs/btp-integration-suite, checked “Once the counter reaches the Quota limit, all successive calls made to the API are rejected.”Quota — SAP Integration Suite documentation, SAP-docs/btp-integration-suite, checked “No counter is maintained for spike arrests, only the time that the last message was successfully passed through the Spike Arrest policy is maintained.”Spike Arrest — SAP Integration Suite documentation, SAP-docs/btp-integration-suite, checked “Do not use Spike Arrest policy to limit traffic from individual clients.”Spike Arrest — SAP Integration Suite documentation, SAP-docs/btp-integration-suite, checked “You can no longer create or update an API proxy with Concurrent Rate Limit policy.”Concurrent Rate Limit — SAP Integration Suite documentation, SAP-docs/btp-integration-suite, checked
stated
provides Rate limiting
Functional, stated
For
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.
Basis
“The Quota policy defines the number of request messages an application can submit to an API over a given period of time.”Quota — SAP Integration Suite documentation, SAP-docs/btp-integration-suite, checked “Once the counter reaches the Quota limit, all successive calls made to the API are rejected.”Quota — SAP Integration Suite documentation, SAP-docs/btp-integration-suite, checked “No counter is maintained for spike arrests, only the time that the last message was successfully passed through the Spike Arrest policy is maintained.”Spike Arrest — SAP Integration Suite documentation, SAP-docs/btp-integration-suite, checked “Do not use Spike Arrest policy to limit traffic from individual clients.”Spike Arrest — SAP Integration Suite documentation, SAP-docs/btp-integration-suite, checked “You can no longer create or update an API proxy with Concurrent Rate Limit policy.”Concurrent Rate Limit — SAP Integration Suite documentation, SAP-docs/btp-integration-suite, checked
Capping requests per tenant or caller
Serve your application over MCPServe your application over MCPcapabilityExposing application data and operations to agents over MCPSAP and community, narrow by design
→provides
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.
provides Serve your application over MCP
Functional, stated
For
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.
Basis
“In SAP Integration Suite, the MCP Server capability is realized through the MCP gateway.”MCP Server — SAP Integration Suite documentation, SAP-docs/btp-integration-suite, checked “Create an MCP server from any HTTP endpoint by providing the endpoint URL and an OpenAPI specification.”How Model Context Protocol (MCP) Server Enables AI Integration — SAP Integration Suite documentation, SAP-docs/btp-integration-suite, checked “Create an MCP server from an RFC-based backend by modeling and exposing RFC operations as MCP tools.”How Model Context Protocol (MCP) Server Enables AI Integration — SAP Integration Suite documentation, SAP-docs/btp-integration-suite, checked “You can create an MCP server directly from an existing API proxy deployed on the classic API Management runtime.”Create an MCP Server from an API Proxy — SAP Integration Suite documentation, SAP-docs/btp-integration-suite, checked “Activate API Management capability.”Create an MCP Server from an API Artifact — SAP Integration Suite documentation, SAP-docs/btp-integration-suite, checked “The MCP server can be only deployed and managed over Integration Cell runtime profile.”Create an MCP Server from an API Artifact, checked “Each MCP server supports up to 30 tools.”Create an MCP Server from an API Artifact, checked “SAP Integration Suite offers multiple API Management runtimes to address different deployment and operational needs.”API Management — SAP Integration Suite documentation, SAP-docs/btp-integration-suite, checked “Activate API Management capability.”Create an MCP Server from an HTTP Endpoint — SAP Integration Suite documentation, SAP-docs/btp-integration-suite, checked “Activate API Management capability.”Create an MCP Server by Referring to an RFC-Based Backend — SAP Integration Suite documentation, SAP-docs/btp-integration-suite, checked “Only APIs with OAuth-based authentication can be used to create an MCP server.”Create an MCP Server from an API Artifact, checked “The OpenAPI specification must be a version between 3.0.0 and 3.0.3.”Create an MCP Server from an HTTP Endpoint, checked “Each MCP server supports up to 50 tools.”Configure an MCP Server Created from an HTTP Endpoint, checked “Only OData and REST API artifacts deployed on the Integration Cell runtime can be discovered”Create an MCP Server from an API Artifact, checked “You can create an MCP server directly from an existing API proxy deployed on the classic API Management runtime.”Create an MCP Server from an API Proxy, checked “exposing selected RFC operations as MCP tools.”Create an MCP Server by Referring to an RFC-Based Backend, checked “They are derived from API operations and can represent actions such as retrieving, creating, updating, or deleting data.”MCP Server, checked “add or manage tools, resources, and prompts available to AI agents.”Configure an MCP Server Created from an HTTP Endpoint, checked “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.”Configure an MCP Server Created from an HTTP Endpoint, checked “Review the input schema and output schema derived from the API operation.”Configure an MCP Server Created from an HTTP Endpoint, checked “Defining prompts to guide how agents interact with these tools”Configure an MCP Server Created from an HTTP Endpoint, checked “The MCP gateway acts as the runtime layer that exposes enterprise APIs, tools, and backend services as MCP-compatible endpoints for AI agents.”MCP Server, checked “In *Create Tools*, select the API resource you want to expose as MCP tools.”Create an MCP Server from an API Artifact, checked “Select the API operations that you want to expose as tools based on the HTTP method and resource path”Configure an MCP Server Created from an HTTP Endpoint, checked “By default, Authentication and Authorization policies are applied to an MCP server. These policies are mandatory and cannot be deleted.”Configure an MCP Server Created from an HTTP Endpoint, checked “Create an MCP Server from any HTTP endpoint by providing its OpenAPI specification.”Create an MCP Server from an HTTP Endpoint, checked “Each MCP server supports up to 30 tools.”Create an MCP Server from an HTTP Endpoint, checked
stated
provides Serve your application over MCP
Functional, stated
For
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.
Basis
“In SAP Integration Suite, the MCP Server capability is realized through the MCP gateway.”MCP Server — SAP Integration Suite documentation, SAP-docs/btp-integration-suite, checked “Create an MCP server from any HTTP endpoint by providing the endpoint URL and an OpenAPI specification.”How Model Context Protocol (MCP) Server Enables AI Integration — SAP Integration Suite documentation, SAP-docs/btp-integration-suite, checked “Create an MCP server from an RFC-based backend by modeling and exposing RFC operations as MCP tools.”How Model Context Protocol (MCP) Server Enables AI Integration — SAP Integration Suite documentation, SAP-docs/btp-integration-suite, checked “You can create an MCP server directly from an existing API proxy deployed on the classic API Management runtime.”Create an MCP Server from an API Proxy — SAP Integration Suite documentation, SAP-docs/btp-integration-suite, checked “Activate API Management capability.”Create an MCP Server from an API Artifact — SAP Integration Suite documentation, SAP-docs/btp-integration-suite, checked “The MCP server can be only deployed and managed over Integration Cell runtime profile.”Create an MCP Server from an API Artifact, checked “Each MCP server supports up to 30 tools.”Create an MCP Server from an API Artifact, checked “SAP Integration Suite offers multiple API Management runtimes to address different deployment and operational needs.”API Management — SAP Integration Suite documentation, SAP-docs/btp-integration-suite, checked “Activate API Management capability.”Create an MCP Server from an HTTP Endpoint — SAP Integration Suite documentation, SAP-docs/btp-integration-suite, checked “Activate API Management capability.”Create an MCP Server by Referring to an RFC-Based Backend — SAP Integration Suite documentation, SAP-docs/btp-integration-suite, checked “Only APIs with OAuth-based authentication can be used to create an MCP server.”Create an MCP Server from an API Artifact, checked “The OpenAPI specification must be a version between 3.0.0 and 3.0.3.”Create an MCP Server from an HTTP Endpoint, checked “Each MCP server supports up to 50 tools.”Configure an MCP Server Created from an HTTP Endpoint, checked “Only OData and REST API artifacts deployed on the Integration Cell runtime can be discovered”Create an MCP Server from an API Artifact, checked “You can create an MCP server directly from an existing API proxy deployed on the classic API Management runtime.”Create an MCP Server from an API Proxy, checked “exposing selected RFC operations as MCP tools.”Create an MCP Server by Referring to an RFC-Based Backend, checked “They are derived from API operations and can represent actions such as retrieving, creating, updating, or deleting data.”MCP Server, checked “add or manage tools, resources, and prompts available to AI agents.”Configure an MCP Server Created from an HTTP Endpoint, checked “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.”Configure an MCP Server Created from an HTTP Endpoint, checked “Review the input schema and output schema derived from the API operation.”Configure an MCP Server Created from an HTTP Endpoint, checked “Defining prompts to guide how agents interact with these tools”Configure an MCP Server Created from an HTTP Endpoint, checked “The MCP gateway acts as the runtime layer that exposes enterprise APIs, tools, and backend services as MCP-compatible endpoints for AI agents.”MCP Server, checked “In *Create Tools*, select the API resource you want to expose as MCP tools.”Create an MCP Server from an API Artifact, checked “Select the API operations that you want to expose as tools based on the HTTP method and resource path”Configure an MCP Server Created from an HTTP Endpoint, checked “By default, Authentication and Authorization policies are applied to an MCP server. These policies are mandatory and cannot be deleted.”Configure an MCP Server Created from an HTTP Endpoint, checked “Create an MCP Server from any HTTP endpoint by providing its OpenAPI specification.”Create an MCP Server from an HTTP Endpoint, checked “Each MCP server supports up to 30 tools.”Create an MCP Server from an HTTP Endpoint, checked
Exposing application data and operations to agents over MCP
Tool governanceTool governancecapabilityControlling what an agent may call, with an audit trailSAP and community, unassessed
→provides
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.
provides Tool governance
Functional, stated
For
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.
Basis
“It provides capabilities such as security, traffic management, routing, and multi-protocol connectivity while enabling governed access to enterprise systems”MCP Server — SAP Integration Suite documentation, SAP-docs/btp-integration-suite, checked “Both gateways share common capabilities such as security, traffic management, and multi-protocol connectivity.”MCP Server — SAP Integration Suite documentation, SAP-docs/btp-integration-suite, checked “the *Policies* tab to configure traffic management and security policies”Create an MCP Server from an API Artifact — SAP Integration Suite documentation, SAP-docs/btp-integration-suite, checked
stated
provides Tool governance
Functional, stated
For
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.
Basis
“It provides capabilities such as security, traffic management, routing, and multi-protocol connectivity while enabling governed access to enterprise systems”MCP Server — SAP Integration Suite documentation, SAP-docs/btp-integration-suite, checked “Both gateways share common capabilities such as security, traffic management, and multi-protocol connectivity.”MCP Server — SAP Integration Suite documentation, SAP-docs/btp-integration-suite, checked “the *Policies* tab to configure traffic management and security policies”Create an MCP Server from an API Artifact — SAP Integration Suite documentation, SAP-docs/btp-integration-suite, checked
Controlling what an agent may call, with an audit trail
Lineage2
API CompositionAPI CompositionserviceBusiness data graph queried with OData V4 or GraphQLsap official, btp
←has part
through inverted from its part_of edge
has part API Composition
Lineage, derived, through inverted from its part_of edge
derived
has part API Composition
Lineage, derived, through inverted from its part_of edge
Business data graph queried with OData V4 or GraphQL
SAP Integration SuiteSAP Integration SuiteserviceIntegration service on BTP with Cloud Integration and API Managementsap official, btp
→part of
none
stated
part of SAP Integration Suite
Lineage, stated
Basis
“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.”Components of API Management — SAP Integration Suite documentation, SAP-docs/btp-integration-suite, checked “SAP Integration Suite brings together the features and functionality of various capabilities such as:”Capabilities of SAP Integration Suite — SAP Integration Suite documentation, SAP-docs/btp-integration-suite, checked “You've enabled API Management capability using SAP Integration Suite and have completed the setup.”Managing Cloud Foundry Microservices through API Management — SAP Integration Suite documentation, SAP-docs/btp-integration-suite, checked
Integration service on BTP with Cloud Integration and API Management
Powering Enterprise-Ready Agentic AI with SAP Integration SuitePowering Enterprise-Ready Agentic AI with SAP Integration SuitetalkA 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?talkDevtoberfest 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
Create an MCP Server for Enterprise AI AgentsCreate an MCP Server for Enterprise AI AgentstutorialWraps the preceding supply-risk graph from API Composition as an MCP server in Integration Suite, with API Management activated as a prerequisite. The walkthrough selects retrieval tools, deploys on Integration Cell, publishes a product in Developer Hub, creates an agent subscription and invokes the tools in MCP Inspector; its companion tutorial uses mock backends.Shyam, published 2026-09-23Shyam, SAP Developer Center
10 more
API Composition: Seamless Enterprise Data Access for Developers and AI AgentsAPI Composition: Seamless Enterprise Data Access for Developers and AI AgentsblogAPI 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
Turn SAP APIs into MCP Tools for AI Agents using SAP Integration Suite Free TrialTurn SAP APIs into MCP Tools for AI Agents using SAP Integration Suite Free TrialblogWalks through building an MCP server on SAP Integration Suite's free trial from an existing API artifact — the Business Partner API against a public S/4HANA Cloud sandbox — rather than from an HTTP endpoint with an OpenAPI specification or from RFC-enabled function modules, the creation wizard's other two source types, left unexplained here. Covers the API artifact's Content Modifier policy that injects the Business Accelerator Hub API key before the backend call, and the "Trust Upstream MCP Authorization" setting that lets the MCP server delegate authorization checks to that source API instead of duplicating them. Ends by fetching an OAuth token from a Process Integration Runtime service key and pointing an MCP client at the deployed server over streamable HTTP.published 2026-07-13claudiacsrosalino, SAP Community
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 GraphblogA 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 experiencesblogWalks 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 SuiteseriesIntroduces 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 APIsblogWalks 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-ontalkA 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
Configure an MCP Server Created from an HTTP EndpointConfigure an MCP Server Created from an HTTP EndpointdocDocuments configuring API Management’s HTTP-source MCP server tools, resources, prompts and policies. Resources are selected from GET operations and have URI templates/content types; prompts define User/Assistant messages with optional arguments, alongside MCP policy configuration.SAP, SAP Help Portal
Modern integration at TÜV Rheinland: APIs, events and cloud transformationModern integration at TÜV Rheinland: APIs, events and cloud transformationtalkTÜ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 capabilitiestalkSAP'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 providing24
Rate limitingRate limitingcapabilityCapping 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/commonpackageSix 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 limitsfrom CAP
cds-rate-limitcds-rate-limitcds-pluginA 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 applicationsfrom CAP
Serve your application over MCPServe your application over MCPcapabilityExposing 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
abap-ai/mcpabap-ai/mcpmcp-serverAn MCP server SDK written in ABAP to run natively on the ABAP stack, so an ABAP system can expose its own prompts, resources and tools to an agent from inside itself.independent, abapMCP server SDK written in ABAPfrom ABAP
abap-ai/mcp2abap-ai/mcp2mcp-serverA stateless rewrite of the ABAP MCP server SDK: one ABAP server contract answering both the 2026-07-28 protocol draft and the legacy 2025 versions, with no sessions and no SSE.independent, abapStateless ABAP MCP server SDK for the 2026-07-28 protocol draftfrom ABAP
abap-agent-runtimeabap-agent-runtimemcp-serverAn ABAP-native MCP endpoint inside the SAP system: an agent reads the screen of an opted-in abap2UI5 app as structured data, fills its fields and fires its events as the logged-on SAP user.community org, abapABAP-native MCP endpoint that drives opted-in abap2UI5 appsfrom ABAP
com.sap.cds:cds-adapter-mcpcom.sap.cds:cds-adapter-mcppackageThe 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 serverfrom CAP
@cap-js/mcp@cap-js/mcpcds-pluginA 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 agentsfrom CAP
@gavdi/cap-mcp@gavdi/cap-mcpcds-pluginGenerates 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 actionsfrom CAP
btp-cf-mcpbtp-cf-mcpmcp-serverAn MCP server over an SAP BTP account and its Cloud Foundry runtime that acts as the person who logged in, so their own global-account and space roles decide what an agent can see.independent, btpMCP server for SAP BTP and Cloud Foundry acting as the logged-in userfrom BTP/BAIP
MarkWuRY168/SAP_MCPMarkWuRY168/SAP_MCPmcp-serverPublishes SAP system functions as MCP tools from configuration tables held inside the SAP system, so adding a tool is a configuration change rather than a code change.independent, abapMCP server publishing SAP functions as tools from config tablesfrom ABAP
@neoimpulse/cap-js-mcp@neoimpulse/cap-js-mcpcds-pluginAn 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 toolsfrom CAP
@odatano/core-mcp@odatano/core-mcpmcp-serverMCP 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 toolsfrom CAP
@odatano/nightgate-mcp@odatano/nightgate-mcpmcp-serverMCP 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 layerfrom CAP
@shahid.la/cds-db-nlquery-mcp@shahid.la/cds-db-nlquery-mcpmcp-serverMCP 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 schemafrom CAP
Skybuffer AI MCP serverSkybuffer AI MCP servermcp-serverAn ABAP add-on that serves SAP business data, transactions and development context as MCP tools from an ICF node inside SAP ECC and S/4HANA, each call running as the signed-in user under PFCG authorization checks.independent, abapABAP add-on serving business data and transactions as MCP toolsfrom ABAP
cap-mcp-plugincap-mcp-plugincds-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-mcpfrom CAP
Tool governanceTool governancecapabilityControlling 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-plugincds-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 agentfrom CAP
arc-mcp-hubarc-mcp-hubmcp-serverA hub on SAP BTP that puts several arc-1 instances, one per SAP system, behind one login and a route each, exchanging the caller's token through a destination so each system still sees the real user.independent, btpHub on SAP BTP putting several arc-1 instances behind one loginfrom BTP/BAIP
SuperClaude for SAPSuperClaude for SAPskillA Claude Code plugin that installs and wires its own ABAP MCP server, then puts a two-layer write guard between the agent and any system profile marked QA or production.independent, abapClaude Code plugin with an ABAP MCP server and write guardsfrom ABAP
bw-modeling-mcpbw-modeling-mcpmcp-serverReads, creates and modifies BW/4HANA modelling objects through the same internal APIs Eclipse BWMT and the BW/4HANA Cockpit use — and can run centrally on BTP with each caller reaching BW as themselves.independent, btpMCP server for BW/4HANA modelling objectsfrom BTP/BAIP
Maherd18/sap-mcp-serverMaherd18/sap-mcp-servermcp-serverAn MCP server for ABAP development over the ADT resources: eight tools, each checked against a JSON policy file before the call reaches the system, with activation and transport release held for a person to approve.independent, abapPolicy-checked MCP server for ABAP development over ADTfrom ABAP
SAP API Policy Evidence SkillSAP API Policy Evidence SkillskillAssesses 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 Policyfrom BTP/BAIP
cds-agentscds-agentspackageTurns 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 frameworksfrom CAP
pyrfc-mcppyrfc-mcpmcp-serverAn MCP server for calling an SAP system's RFC-enabled function modules from an agent, built so that discovering a function does not authorise calling it: a read or a write is denied unless the function name matches an allowlist the server is configured with.independent, abapMCP server calling RFC-enabled function modules behind an allowlistfrom ABAP
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 atlas11
[{"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
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.
