{"ref":"artifact:btp-api-management","page":"/artifacts/btp-api-management","json":"/artifacts/btp-api-management.json","generated":"2026-10-26","drafted_with_ai":true,"entity":{"id":"btp-api-management","name":"API Management","artifact_type":"service","ecosystem":"btp","serves_ecosystems":["cap"],"domain":"integration-and-messaging","origin_ring":"sap-official","description":{"one_line":"API proxies in front of backend services, with security and traffic management policies attached to them, and Developer Hub where consumers subscribe.","short":"API proxies with security and traffic policies and Developer Hub","what_it_solves":"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 Suite](artifact:btp-integration-suite) and runs on one of three runtimes: Classic API Management, Integration Cell, or the customer-managed Edge Integration Cell."},"links":{"homepage":"https://help.sap.com/docs/integration-suite/isuite-integrations-and-apis/build-your-integrations-and-apis?version=CLOUD","docs":"https://github.com/SAP-docs/btp-integration-suite/blob/main/docs/ISuite_Integrations_APIs/api-management-de3fea6.md"},"source_available":false,"provides":[{"capability":"capability:rate-limiting","what_it_does":"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.","sources":[{"url":"https://raw.githubusercontent.com/SAP-docs/btp-integration-suite/33f339544cd06d3c4e272fe8ef57c7248f68c6a2/docs/ISuite_Integrations_APIs/quota-1f742c1.md","title":"Quota — SAP Integration Suite documentation, SAP-docs/btp-integration-suite","checked":"2026-09-20","quote":"The Quota policy defines the number of request messages an application can submit to an API over a given period of time."},{"url":"https://raw.githubusercontent.com/SAP-docs/btp-integration-suite/33f339544cd06d3c4e272fe8ef57c7248f68c6a2/docs/ISuite_Integrations_APIs/quota-1f742c1.md","title":"Quota — SAP Integration Suite documentation, SAP-docs/btp-integration-suite","checked":"2026-09-20","quote":"Once the counter reaches the Quota limit, all successive calls made to the API are rejected."},{"url":"https://raw.githubusercontent.com/SAP-docs/btp-integration-suite/33f339544cd06d3c4e272fe8ef57c7248f68c6a2/docs/ISuite_Integrations_APIs/spike-arrest-bf441dc.md","title":"Spike Arrest — SAP Integration Suite documentation, SAP-docs/btp-integration-suite","checked":"2026-09-20","quote":"No counter is maintained for spike arrests, only the time that the last message was successfully passed through the Spike Arrest policy is maintained."},{"url":"https://raw.githubusercontent.com/SAP-docs/btp-integration-suite/33f339544cd06d3c4e272fe8ef57c7248f68c6a2/docs/ISuite_Integrations_APIs/spike-arrest-bf441dc.md","title":"Spike Arrest — SAP Integration Suite documentation, SAP-docs/btp-integration-suite","checked":"2026-09-20","quote":"Do not use Spike Arrest policy to limit traffic from individual clients."},{"url":"https://raw.githubusercontent.com/SAP-docs/btp-integration-suite/33f339544cd06d3c4e272fe8ef57c7248f68c6a2/docs/ISuite_Integrations_APIs/concurrent-rate-limit-8f22baa.md","title":"Concurrent Rate Limit — SAP Integration Suite documentation, SAP-docs/btp-integration-suite","checked":"2026-09-20","quote":"You can no longer create or update an API proxy with Concurrent Rate Limit policy."}]},{"capability":"capability: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.","sources":[{"url":"https://raw.githubusercontent.com/SAP-docs/btp-integration-suite/33f339544cd06d3c4e272fe8ef57c7248f68c6a2/docs/ISuite_Integrations_APIs/mcp-server-9eb9239.md","title":"MCP Server — SAP Integration Suite documentation, SAP-docs/btp-integration-suite","checked":"2026-09-20","quote":"In SAP Integration Suite, the MCP Server capability is realized through the MCP gateway."},{"url":"https://raw.githubusercontent.com/SAP-docs/btp-integration-suite/33f339544cd06d3c4e272fe8ef57c7248f68c6a2/docs/ISuite_Integrations_APIs/how-model-context-protocol-mcp-server-enables-ai-integration-572e7fd.md","title":"How Model Context Protocol (MCP) Server Enables AI Integration — SAP Integration Suite documentation, SAP-docs/btp-integration-suite","checked":"2026-09-20","quote":"Create an MCP server from any HTTP endpoint by providing the endpoint URL and an OpenAPI specification."},{"url":"https://raw.githubusercontent.com/SAP-docs/btp-integration-suite/33f339544cd06d3c4e272fe8ef57c7248f68c6a2/docs/ISuite_Integrations_APIs/how-model-context-protocol-mcp-server-enables-ai-integration-572e7fd.md","title":"How Model Context Protocol (MCP) Server Enables AI Integration — SAP Integration Suite documentation, SAP-docs/btp-integration-suite","checked":"2026-09-20","quote":"Create an MCP server from an RFC-based backend by modeling and exposing RFC operations as MCP tools."},{"url":"https://raw.githubusercontent.com/SAP-docs/btp-integration-suite/33f339544cd06d3c4e272fe8ef57c7248f68c6a2/docs/ISuite_Integrations_APIs/create-an-mcp-server-from-an-api-proxy-40b31a0.md","title":"Create an MCP Server from an API Proxy — SAP Integration Suite documentation, SAP-docs/btp-integration-suite","checked":"2026-09-20","quote":"You can create an MCP server directly from an existing API proxy deployed on the classic API Management runtime."},{"url":"https://raw.githubusercontent.com/SAP-docs/btp-integration-suite/33f339544cd06d3c4e272fe8ef57c7248f68c6a2/docs/ISuite_Integrations_APIs/create-an-mcp-server-from-an-api-artifact-9f18140.md","title":"Create an MCP Server from an API Artifact — SAP Integration Suite documentation, SAP-docs/btp-integration-suite","checked":"2026-09-20","quote":"Activate API Management capability."},{"url":"https://raw.githubusercontent.com/SAP-docs/btp-integration-suite/33f339544cd06d3c4e272fe8ef57c7248f68c6a2/docs/ISuite_Integrations_APIs/create-an-mcp-server-from-an-api-artifact-9f18140.md","title":"Create an MCP Server from an API Artifact","quote":"The MCP server can be only deployed and managed over Integration Cell runtime profile.","checked":"2026-10-12"},{"url":"https://raw.githubusercontent.com/SAP-docs/btp-integration-suite/33f339544cd06d3c4e272fe8ef57c7248f68c6a2/docs/ISuite_Integrations_APIs/create-an-mcp-server-from-an-api-artifact-9f18140.md","title":"Create an MCP Server from an API Artifact","quote":"Each MCP server supports up to 30 tools.","checked":"2026-10-12"},{"url":"https://raw.githubusercontent.com/SAP-docs/btp-integration-suite/33f339544cd06d3c4e272fe8ef57c7248f68c6a2/docs/ISuite_Integrations_APIs/api-management-de3fea6.md","title":"API Management — SAP Integration Suite documentation, SAP-docs/btp-integration-suite","checked":"2026-09-20","quote":"SAP Integration Suite offers multiple API Management runtimes to address different deployment and operational needs."},{"url":"https://raw.githubusercontent.com/SAP-docs/btp-integration-suite/33f339544cd06d3c4e272fe8ef57c7248f68c6a2/docs/ISuite_Integrations_APIs/create-an-mcp-server-from-an-http-endpoint-b59f141.md","title":"Create an MCP Server from an HTTP Endpoint — SAP Integration Suite documentation, SAP-docs/btp-integration-suite","checked":"2026-09-20","quote":"Activate API Management capability."},{"url":"https://raw.githubusercontent.com/SAP-docs/btp-integration-suite/33f339544cd06d3c4e272fe8ef57c7248f68c6a2/docs/ISuite_Integrations_APIs/create-an-mcp-server-by-referring-to-an-rfc-based-backend-cbb8b78.md","title":"Create an MCP Server by Referring to an RFC-Based Backend — SAP Integration Suite documentation, SAP-docs/btp-integration-suite","checked":"2026-09-20","quote":"Activate API Management capability."},{"url":"https://raw.githubusercontent.com/SAP-docs/btp-integration-suite/33f339544cd06d3c4e272fe8ef57c7248f68c6a2/docs/ISuite_Integrations_APIs/create-an-mcp-server-from-an-api-artifact-9f18140.md","title":"Create an MCP Server from an API Artifact","quote":"Only APIs with OAuth-based authentication can be used to create an MCP server.","checked":"2026-10-12"},{"url":"https://raw.githubusercontent.com/SAP-docs/btp-integration-suite/33f339544cd06d3c4e272fe8ef57c7248f68c6a2/docs/ISuite_Integrations_APIs/create-an-mcp-server-from-an-http-endpoint-b59f141.md","title":"Create an MCP Server from an HTTP Endpoint","quote":"The OpenAPI specification must be a version between 3.0.0 and 3.0.3.","checked":"2026-10-12"},{"url":"https://help.sap.com/docs/integration-suite/isuite-integrations-and-apis/f58f7b04b86246419563fba744f073bd","title":"Configure an MCP Server Created from an HTTP Endpoint","quote":"Each MCP server supports up to 50 tools.","checked":"2026-10-12"},{"url":"https://raw.githubusercontent.com/SAP-docs/btp-integration-suite/33f339544cd06d3c4e272fe8ef57c7248f68c6a2/docs/ISuite_Integrations_APIs/create-an-mcp-server-from-an-api-artifact-9f18140.md","title":"Create an MCP Server from an API Artifact","quote":"Only OData and REST API artifacts deployed on the Integration Cell runtime can be discovered","checked":"2026-10-12"},{"url":"https://raw.githubusercontent.com/SAP-docs/btp-integration-suite/33f339544cd06d3c4e272fe8ef57c7248f68c6a2/docs/ISuite_Integrations_APIs/create-an-mcp-server-from-an-api-proxy-40b31a0.md","title":"Create an MCP Server from an API Proxy","quote":"You can create an MCP server directly from an existing API proxy deployed on the classic API Management runtime.","checked":"2026-10-12"},{"url":"https://raw.githubusercontent.com/SAP-docs/btp-integration-suite/33f339544cd06d3c4e272fe8ef57c7248f68c6a2/docs/ISuite_Integrations_APIs/create-an-mcp-server-by-referring-to-an-rfc-based-backend-cbb8b78.md","title":"Create an MCP Server by Referring to an RFC-Based Backend","quote":"exposing selected RFC operations as MCP tools.","checked":"2026-10-12"},{"url":"https://raw.githubusercontent.com/SAP-docs/btp-integration-suite/33f339544cd06d3c4e272fe8ef57c7248f68c6a2/docs/ISuite_Integrations_APIs/mcp-server-9eb9239.md","title":"MCP Server","quote":"They are derived from API operations and can represent actions such as retrieving, creating, updating, or deleting data.","checked":"2026-10-12"},{"url":"https://help.sap.com/docs/integration-suite/isuite-integrations-and-apis/f58f7b04b86246419563fba744f073bd","title":"Configure an MCP Server Created from an HTTP Endpoint","quote":"add or manage tools, resources, and prompts available to AI agents.","checked":"2026-10-12"},{"url":"https://help.sap.com/docs/integration-suite/isuite-integrations-and-apis/f58f7b04b86246419563fba744f073bd","title":"Configure an MCP Server Created from an HTTP Endpoint","quote":"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.","checked":"2026-10-12"},{"url":"https://help.sap.com/docs/integration-suite/isuite-integrations-and-apis/f58f7b04b86246419563fba744f073bd","title":"Configure an MCP Server Created from an HTTP Endpoint","quote":"Review the input schema and output schema derived from the API operation.","checked":"2026-10-12"},{"url":"https://help.sap.com/docs/integration-suite/isuite-integrations-and-apis/f58f7b04b86246419563fba744f073bd","title":"Configure an MCP Server Created from an HTTP Endpoint","quote":"Defining prompts to guide how agents interact with these tools","checked":"2026-10-12"},{"url":"https://raw.githubusercontent.com/SAP-docs/btp-integration-suite/33f339544cd06d3c4e272fe8ef57c7248f68c6a2/docs/ISuite_Integrations_APIs/mcp-server-9eb9239.md","title":"MCP Server","quote":"The MCP gateway acts as the runtime layer that exposes enterprise APIs, tools, and backend services as MCP-compatible endpoints for AI agents.","checked":"2026-10-12"},{"url":"https://raw.githubusercontent.com/SAP-docs/btp-integration-suite/33f339544cd06d3c4e272fe8ef57c7248f68c6a2/docs/ISuite_Integrations_APIs/create-an-mcp-server-from-an-api-artifact-9f18140.md","title":"Create an MCP Server from an API Artifact","quote":"In *Create Tools*, select the API resource you want to expose as MCP tools.","checked":"2026-10-12"},{"url":"https://help.sap.com/docs/integration-suite/isuite-integrations-and-apis/f58f7b04b86246419563fba744f073bd","title":"Configure an MCP Server Created from an HTTP Endpoint","quote":"Select the API operations that you want to expose as tools based on the HTTP method and resource path","checked":"2026-10-12"},{"url":"https://help.sap.com/docs/integration-suite/isuite-integrations-and-apis/f58f7b04b86246419563fba744f073bd","title":"Configure an MCP Server Created from an HTTP Endpoint","quote":"By default, Authentication and Authorization policies are applied to an MCP server. These policies are mandatory and cannot be deleted.","checked":"2026-10-12"},{"url":"https://raw.githubusercontent.com/SAP-docs/btp-integration-suite/33f339544cd06d3c4e272fe8ef57c7248f68c6a2/docs/ISuite_Integrations_APIs/create-an-mcp-server-from-an-http-endpoint-b59f141.md","title":"Create an MCP Server from an HTTP Endpoint","quote":"Create an MCP Server from any HTTP endpoint by providing its OpenAPI specification.","checked":"2026-10-12"},{"url":"https://raw.githubusercontent.com/SAP-docs/btp-integration-suite/33f339544cd06d3c4e272fe8ef57c7248f68c6a2/docs/ISuite_Integrations_APIs/create-an-mcp-server-from-an-http-endpoint-b59f141.md","title":"Create an MCP Server from an HTTP Endpoint","quote":"Each MCP server supports up to 30 tools.","checked":"2026-10-12"}],"facets":[{"key":"mcp_exposure_source","value":["API artifact","API proxy","HTTP/OpenAPI endpoint","RFC backend"],"source":{"url":"https://raw.githubusercontent.com/SAP-docs/btp-integration-suite/33f339544cd06d3c4e272fe8ef57c7248f68c6a2/docs/ISuite_Integrations_APIs/create-an-mcp-server-from-an-api-artifact-9f18140.md","title":"Create an MCP Server from an API Artifact","quote":"Only OData and REST API artifacts deployed on the Integration Cell runtime can be discovered","checked":"2026-10-12"},"sources":[{"url":"https://raw.githubusercontent.com/SAP-docs/btp-integration-suite/33f339544cd06d3c4e272fe8ef57c7248f68c6a2/docs/ISuite_Integrations_APIs/create-an-mcp-server-from-an-api-artifact-9f18140.md","title":"Create an MCP Server from an API Artifact","quote":"Only OData and REST API artifacts deployed on the Integration Cell runtime can be discovered","checked":"2026-10-12"},{"url":"https://raw.githubusercontent.com/SAP-docs/btp-integration-suite/33f339544cd06d3c4e272fe8ef57c7248f68c6a2/docs/ISuite_Integrations_APIs/create-an-mcp-server-from-an-api-proxy-40b31a0.md","title":"Create an MCP Server from an API Proxy","quote":"You can create an MCP server directly from an existing API proxy deployed on the classic API Management runtime.","checked":"2026-10-12"},{"url":"https://raw.githubusercontent.com/SAP-docs/btp-integration-suite/33f339544cd06d3c4e272fe8ef57c7248f68c6a2/docs/ISuite_Integrations_APIs/create-an-mcp-server-from-an-http-endpoint-b59f141.md","title":"Create an MCP Server from an HTTP Endpoint","quote":"The OpenAPI specification must be a version between 3.0.0 and 3.0.3.","checked":"2026-10-12"},{"url":"https://raw.githubusercontent.com/SAP-docs/btp-integration-suite/33f339544cd06d3c4e272fe8ef57c7248f68c6a2/docs/ISuite_Integrations_APIs/create-an-mcp-server-by-referring-to-an-rfc-based-backend-cbb8b78.md","title":"Create an MCP Server by Referring to an RFC-Based Backend","quote":"exposing selected RFC operations as MCP tools.","checked":"2026-10-12"},{"url":"https://raw.githubusercontent.com/SAP-docs/btp-integration-suite/33f339544cd06d3c4e272fe8ef57c7248f68c6a2/docs/ISuite_Integrations_APIs/create-an-mcp-server-from-an-http-endpoint-b59f141.md","title":"Create an MCP Server from an HTTP Endpoint","quote":"Create an MCP Server from any HTTP endpoint by providing its OpenAPI specification.","checked":"2026-10-12"}],"applies_to":{"ecosystems":["cap","btp"]}},{"key":"mcp_operations","value":"Selected source-API operations become tools; retrieval/create/update/delete depend on that API contract","source":{"url":"https://raw.githubusercontent.com/SAP-docs/btp-integration-suite/33f339544cd06d3c4e272fe8ef57c7248f68c6a2/docs/ISuite_Integrations_APIs/mcp-server-9eb9239.md","title":"MCP Server","quote":"They are derived from API operations and can represent actions such as retrieving, creating, updating, or deleting data.","checked":"2026-10-12"},"applies_to":{"ecosystems":["cap","btp"]}},{"key":"mcp_context","value":["MCP resources","MCP prompts","Tool input/output schemas"],"source":{"url":"https://help.sap.com/docs/integration-suite/isuite-integrations-and-apis/f58f7b04b86246419563fba744f073bd","title":"Configure an MCP Server Created from an HTTP Endpoint","quote":"add or manage tools, resources, and prompts available to AI agents.","checked":"2026-10-12"},"sources":[{"url":"https://help.sap.com/docs/integration-suite/isuite-integrations-and-apis/f58f7b04b86246419563fba744f073bd","title":"Configure an MCP Server Created from an HTTP Endpoint","quote":"add or manage tools, resources, and prompts available to AI agents.","checked":"2026-10-12"},{"url":"https://help.sap.com/docs/integration-suite/isuite-integrations-and-apis/f58f7b04b86246419563fba744f073bd","title":"Configure an MCP Server Created from an HTTP Endpoint","quote":"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.","checked":"2026-10-12"},{"url":"https://help.sap.com/docs/integration-suite/isuite-integrations-and-apis/f58f7b04b86246419563fba744f073bd","title":"Configure an MCP Server Created from an HTTP Endpoint","quote":"Review the input schema and output schema derived from the API operation.","checked":"2026-10-12"},{"url":"https://help.sap.com/docs/integration-suite/isuite-integrations-and-apis/f58f7b04b86246419563fba744f073bd","title":"Configure an MCP Server Created from an HTTP Endpoint","quote":"Defining prompts to guide how agents interact with these tools","checked":"2026-10-12"}],"applies_to":{"ecosystems":["cap","btp"]}},{"key":"mcp_execution_path","value":["Remote backend calls"],"source":{"url":"https://raw.githubusercontent.com/SAP-docs/btp-integration-suite/33f339544cd06d3c4e272fe8ef57c7248f68c6a2/docs/ISuite_Integrations_APIs/mcp-server-9eb9239.md","title":"MCP Server","quote":"The MCP gateway acts as the runtime layer that exposes enterprise APIs, tools, and backend services as MCP-compatible endpoints for AI agents.","checked":"2026-10-12"},"sources":[{"url":"https://raw.githubusercontent.com/SAP-docs/btp-integration-suite/33f339544cd06d3c4e272fe8ef57c7248f68c6a2/docs/ISuite_Integrations_APIs/mcp-server-9eb9239.md","title":"MCP Server","quote":"The MCP gateway acts as the runtime layer that exposes enterprise APIs, tools, and backend services as MCP-compatible endpoints for AI agents.","checked":"2026-10-12"},{"url":"https://raw.githubusercontent.com/SAP-docs/btp-integration-suite/33f339544cd06d3c4e272fe8ef57c7248f68c6a2/docs/ISuite_Integrations_APIs/create-an-mcp-server-from-an-api-artifact-9f18140.md","title":"Create an MCP Server from an API Artifact","quote":"The MCP server can be only deployed and managed over Integration Cell runtime profile.","checked":"2026-10-12"},{"url":"https://raw.githubusercontent.com/SAP-docs/btp-integration-suite/33f339544cd06d3c4e272fe8ef57c7248f68c6a2/docs/ISuite_Integrations_APIs/create-an-mcp-server-from-an-api-proxy-40b31a0.md","title":"Create an MCP Server from an API Proxy","quote":"You can create an MCP server directly from an existing API proxy deployed on the classic API Management runtime.","checked":"2026-10-12"}],"applies_to":{"ecosystems":["cap","btp"]}},{"key":"mcp_exposure_control","value":["API operation selection"],"source":{"url":"https://raw.githubusercontent.com/SAP-docs/btp-integration-suite/33f339544cd06d3c4e272fe8ef57c7248f68c6a2/docs/ISuite_Integrations_APIs/create-an-mcp-server-from-an-api-artifact-9f18140.md","title":"Create an MCP Server from an API Artifact","quote":"In *Create Tools*, select the API resource you want to expose as MCP tools.","checked":"2026-10-12"},"sources":[{"url":"https://raw.githubusercontent.com/SAP-docs/btp-integration-suite/33f339544cd06d3c4e272fe8ef57c7248f68c6a2/docs/ISuite_Integrations_APIs/create-an-mcp-server-from-an-api-artifact-9f18140.md","title":"Create an MCP Server from an API Artifact","quote":"In *Create Tools*, select the API resource you want to expose as MCP tools.","checked":"2026-10-12"},{"url":"https://help.sap.com/docs/integration-suite/isuite-integrations-and-apis/f58f7b04b86246419563fba744f073bd","title":"Configure an MCP Server Created from an HTTP Endpoint","quote":"Select the API operations that you want to expose as tools based on the HTTP method and resource path","checked":"2026-10-12"},{"url":"https://help.sap.com/docs/integration-suite/isuite-integrations-and-apis/f58f7b04b86246419563fba744f073bd","title":"Configure an MCP Server Created from an HTTP Endpoint","quote":"By default, Authentication and Authorization policies are applied to an MCP server. These policies are mandatory and cannot be deleted.","checked":"2026-10-12"}],"applies_to":{"ecosystems":["cap","btp"]}}]},{"capability":"capability:tool-governance","what_it_does":"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.","sources":[{"url":"https://raw.githubusercontent.com/SAP-docs/btp-integration-suite/33f339544cd06d3c4e272fe8ef57c7248f68c6a2/docs/ISuite_Integrations_APIs/mcp-server-9eb9239.md","title":"MCP Server — SAP Integration Suite documentation, SAP-docs/btp-integration-suite","checked":"2026-09-20","quote":"It provides capabilities such as security, traffic management, routing, and multi-protocol connectivity while enabling governed access to enterprise systems"},{"url":"https://raw.githubusercontent.com/SAP-docs/btp-integration-suite/33f339544cd06d3c4e272fe8ef57c7248f68c6a2/docs/ISuite_Integrations_APIs/mcp-server-9eb9239.md","title":"MCP Server — SAP Integration Suite documentation, SAP-docs/btp-integration-suite","checked":"2026-09-20","quote":"Both gateways share common capabilities such as security, traffic management, and multi-protocol connectivity."},{"url":"https://raw.githubusercontent.com/SAP-docs/btp-integration-suite/33f339544cd06d3c4e272fe8ef57c7248f68c6a2/docs/ISuite_Integrations_APIs/create-an-mcp-server-from-an-api-artifact-9f18140.md","title":"Create an MCP Server from an API Artifact — SAP Integration Suite documentation, SAP-docs/btp-integration-suite","checked":"2026-09-20","quote":"the *Policies* tab to configure traffic management and security policies"}]}],"part_of":{"ref":"artifact:btp-integration-suite","sources":[{"url":"https://raw.githubusercontent.com/SAP-docs/btp-integration-suite/33f339544cd06d3c4e272fe8ef57c7248f68c6a2/docs/ISuite_Integrations_APIs/components-of-api-management-e02ae53.md","title":"Components of API Management — SAP Integration Suite documentation, SAP-docs/btp-integration-suite","checked":"2026-09-20","quote":"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."},{"url":"https://raw.githubusercontent.com/SAP-docs/btp-integration-suite/33f339544cd06d3c4e272fe8ef57c7248f68c6a2/docs/ISuite/capabilities-of-sap-integration-suite-e1c5b90.md","title":"Capabilities of SAP Integration Suite — SAP Integration Suite documentation, SAP-docs/btp-integration-suite","checked":"2026-09-20","quote":"SAP Integration Suite brings together the features and functionality of various capabilities such as:"},{"url":"https://raw.githubusercontent.com/SAP-docs/btp-integration-suite/33f339544cd06d3c4e272fe8ef57c7248f68c6a2/docs/ISuite_Integrations_APIs/managing-cloud-foundry-microservices-through-api-management-e609a3e.md","title":"Managing Cloud Foundry Microservices through API Management — SAP Integration Suite documentation, SAP-docs/btp-integration-suite","checked":"2026-09-20","quote":"You've enabled API Management capability using SAP Integration Suite and have completed the setup."}]},"maintainers":["actor:sap"],"drafted_with_ai":true,"provenance":{"discovered_via":[{"source":"source:curator"}],"first_seen":"2026-09-20"},"history":[{"date":"2026-09-20","field":"provides","from":null,"to":"capability:mcp-servers, capability:tool-governance","reason":"Moved here from SAP Integration Suite. SAP files MCP Server under API Management in its documentation, and every creation path read lists the activated API Management capability as a prerequisite."},{"date":"2026-10-12","field":"provides[mcp-servers].facets and what_it_does","from":"[{\"key\":\"mcp_exposure_source\",\"value\":\"API artifacts/proxies, HTTP OpenAPI or RFC sources\"},{\"key\":\"mcp_operations\",\"value\":\"Selected API retrieval and write operations\"},{\"key\":\"mcp_context\",\"value\":\"Tools, resources and prompts configured on the MCP server\"}]","to":"[{\"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\"}]","reason":"The comparison distinguishes execution and surface selection at the stated runtime, retaining conditional operations and target restrictions."},{"date":"2026-10-12","field":"provides.mcp-servers.facets.mcp_exposure_source.value","from":"Integration Cell OData/REST API artifact, classic API proxy, HTTP OpenAPI 3.0.0–3.0.3 or selected RFC backend","to":"API artifact; API proxy; HTTP/OpenAPI endpoint; RFC backend","reason":"Converts the text answer to controlled list values. Its documented conditions remain in the capability relationship; original citations and runtime scope are retained."},{"date":"2026-10-12","field":"provides.mcp-servers.facets.mcp_context.value","from":"Resource URI/MIME schemas, prompt templates and API-operation tool input/output schemas","to":"MCP resources; MCP prompts; Tool input/output schemas","reason":"Converts the text answer to controlled list values. Its documented conditions remain in the capability relationship; original citations and runtime scope are retained."},{"date":"2026-10-12","field":"provides.mcp-servers.facets.mcp_execution_path.value","from":"MCP gateway routes backend API calls; MCP server deployment is Integration Cell-only even when the source proxy uses the classic runtime","to":"Remote backend calls","reason":"Converts the text answer to controlled list values. Its documented conditions remain in the capability relationship; original citations and runtime scope are retained."},{"date":"2026-10-12","field":"provides.mcp-servers.facets.mcp_exposure_control.value","from":"Select API operations/resources for tools and configure resources/prompts; HTTP-endpoint configuration requires Authentication and Authorization policies","to":"API operation selection","reason":"Converts the text answer to controlled list values. Its documented conditions remain in the capability relationship; original citations and runtime scope are retained."},{"date":"2026-10-12","field":"description.when_not_to_use","from":null,"to":"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.","reason":"Preserves the documented 30/50 tool-limit conflict as a condition for selecting a deployment; the HTTP creation-guide quotation is now attached explicitly alongside the API-artifact and configuration citations."},{"date":"2026-10-12","field":"provides[mcp-servers].what_it_does","from":"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; API-artifact sources must use OAuth and the HTTP specification must be OpenAPI 3.0.0–3.0.3. Both the API-artifact and HTTP-endpoint creation guides state 30 tools; the live HTTP-endpoint configuration guide states 50. The applicable deployment limit remains unresolved. The gateway routes backend API calls, with MCP deployment restricted to Integration Cell even when a source proxy runs on the classic runtime. 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.","to":"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.","reason":"Resolves the requested review findings while preserving the structured comparison values, runtime scopes and implementation restrictions."},{"date":"2026-10-12","field":"description.when_not_to_use","from":"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.","to":"Removed; the documented 30/50 MCP tool-limit discrepancy is retained on provides[mcp-servers].what_it_does.","reason":"Independent review found that the MCP-specific uncertainty does not describe a situation in which the whole API gateway service is the wrong choice."},{"date":"2026-10-12","field":"provides[mcp-servers].what_it_does","from":"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.","to":"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.","reason":"Independent source review supports prompts guiding agent interaction rather than templates; retains both sourced tool-count limits as an explicit MCP-specific discrepancy."}]},"effective_normative_relations":[],"readings":{"liveness":{"label":"Deprecation","tier":"good","evidence":"no plan deprecated, 2 plans"},"continuity":{"label":"Beta","tier":"good","evidence":"no plan in beta"},"reach":{"label":"Regions","tier":"reported","evidence":"3 regions"},"support":{"label":"Support","tier":"good","evidence":"OPU-API, OPU-API-OD-AN, OPU-API-OD-DT, OPU-API-OD-RT"}},"signals":{"crawled_at":"2026-10-25","technical_id":"api-management","technical_ids":["api-management"],"joined_by":"name","display_name":"API Management","plans":[{"name":"analytics","category":"SERVICE","deprecated":false,"beta":false,"regions":["eu10"]},{"name":"preview","category":"SERVICE","deprecated":false,"beta":false,"regions":["eu10","jp10","us10"]}],"regions":3,"deprecated_plans":0,"support_components":["OPU-API","OPU-API-OD-AN","OPU-API-OD-DT","OPU-API-OD-RT"]},"edges":{"maintainers":[{"ref":"actor:sap","name":"SAP","json":"/actors/sap.json"}],"contributors":[],"explained_by":[{"ref":"content:devtoberfest-2026-int-31-agentic-ai-integration-suite","name":"Powering Enterprise-Ready Agentic AI with SAP Integration Suite","json":"/content/devtoberfest-2026-int-31-agentic-ai-integration-suite.json"},{"ref":"content:devtoberfest-2026-int23-agent-calls-sap","name":"🔴 Your Agent Wants to Call SAP. Now What?","json":"/content/devtoberfest-2026-int23-agent-calls-sap.json"},{"ref":"content:sap-tutorial-integration-suite-mcp-server","name":"Create an MCP Server for Enterprise AI Agents","json":"/content/sap-tutorial-integration-suite-mcp-server.json"},{"ref":"content:api-composition-seamless-enterprise-data-access-for-developers-and-ai-agents","name":"API Composition: Seamless Enterprise Data Access for Developers and AI Agents","json":"/content/api-composition-seamless-enterprise-data-access-for-developers-and-ai-agents.json"},{"ref":"content:turn-sap-apis-into-mcp-tools-for-ai-agents-using-sap-integration-suite-free-tria","name":"Turn SAP APIs into MCP Tools for AI Agents using SAP Integration Suite Free Trial","json":"/content/turn-sap-apis-into-mcp-tools-for-ai-agents-using-sap-integration-suite-free-tria.json"},{"ref":"content:graph-on-integration-suite-simplifying-multi-api-data-retrieval-with-unified-bus","name":"Graph on Integration Suite: Simplifying Multi-API Data Retrieval with Unified Business Data Graph","json":"/content/graph-on-integration-suite-simplifying-multi-api-data-retrieval-with-unified-bus.json"},{"ref":"content:sap-pi-migration-to-btp-integration-suite-patterns-and-learning-experiences","name":"SAP PI Migration to BTP Integration Suite Patterns and learning experiences","json":"/content/sap-pi-migration-to-btp-integration-suite-patterns-and-learning-experiences.json"},{"ref":"content:information-map-introduction-series-graph-in-sap-integration-suite","name":"Information Map – Introduction Series: Graph in SAP Integration Suite","json":"/content/information-map-introduction-series-graph-in-sap-integration-suite.json"},{"ref":"content:edge-integration-cell-design-deploy-and-manage-apis","name":"Edge Integration Cell : Design, deploy and manage APIs","json":"/content/edge-integration-cell-design-deploy-and-manage-apis.json"},{"ref":"content:devtoberfest-2026-int-21-mcp-gateway-in-practice","name":"MCP Gateway in Practice: Architecture, configuration, and hands-on","json":"/content/devtoberfest-2026-int-21-mcp-gateway-in-practice.json"},{"ref":"content:integration-suite-mcp-http-configuration","name":"Configure an MCP Server Created from an HTTP Endpoint","json":"/content/integration-suite-mcp-http-configuration.json"},{"ref":"content:teched-2026-in212","name":"Modern integration at TÜV Rheinland: APIs, events and cloud transformation","json":"/content/teched-2026-in212.json"},{"ref":"content:teched-2026-in804","name":"Road map for SAP Integration Suite: What ships next across all capabilities","json":"/content/teched-2026-in804.json"}],"alternative_to_this":[],"needed_by":[],"available_via":[],"part_of":{"ref":"artifact:btp-integration-suite","name":"SAP Integration Suite","json":"/artifacts/btp-integration-suite.json"},"parts":[{"ref":"artifact:btp-api-composition","name":"API Composition","json":"/artifacts/btp-api-composition.json"}],"add_ons":[],"answered_through_parts":[]}}