From 27be7ed8bff816ed7da2b8fcd9ea94bc9aa6c06e Mon Sep 17 00:00:00 2001 From: Maximilian Eckert Date: Wed, 22 Jul 2026 11:29:08 +0200 Subject: [PATCH 1/7] add SAP API policy note to MCP adapter doc --- guides/protocols/mcp.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/guides/protocols/mcp.md b/guides/protocols/mcp.md index 96268437e..5207af593 100644 --- a/guides/protocols/mcp.md +++ b/guides/protocols/mcp.md @@ -17,6 +17,9 @@ The [Model Context Protocol (MCP)](https://modelcontextprotocol.io/) is an open- > > In parallel, there's also the *MCP Server* plugin ([*@cap-js/mcp-server*](https://github.com/cap-js/mcp-server)), which serves a different purpose, though, that is: AI-assisted *development* of CAP projects. +> [!warning] SAP API Policy Applies +> +> The [SAP API Policy](https://api.sap.com/api-policy) remains applicable even when exposing data via MCP. Before exposing any SAP service or data through an MCP endpoint, ensure your use case complies with the SAP API Policy and any applicable licensing terms. From e4c3d7cecbe43e99bc3896fe7544b4a3dad4a8be Mon Sep 17 00:00:00 2001 From: Marvin Lindner Date: Wed, 22 Jul 2026 14:03:37 +0200 Subject: [PATCH 2/7] change alpha and internal flags to beta --- guides/protocols/index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/guides/protocols/index.md b/guides/protocols/index.md index 19f517248..f17282223 100644 --- a/guides/protocols/index.md +++ b/guides/protocols/index.md @@ -8,7 +8,7 @@ CAP supports the following service protocols: - **OData**: A widely used protocol for building and consuming RESTful APIs. CAP provides built-in support for OData v2 and v4, allowing you to easily expose your data models as OData services. - **OpenAPI**: A specification for building APIs that allows you to define your API endpoints, request/response formats, and authentication methods. CAP can generate OpenAPI specifications for your services, enabling easy integration with other systems. - **AsyncAPI**: A specification for defining asynchronous APIs, such as those using messaging protocols. CAP supports AsyncAPI for building event-driven applications and integrating with messaging systems. -- **MCP**: Model Context Protocol (MCP) is an open protocol that enables seamless integration between LLM applications and external data sources and tools. +- **MCP**: Model Context Protocol (MCP) is an open protocol that enables seamless integration between LLM applications and external data sources and tools. ## Using Protocols in CAP To use a specific protocol in your CAP application, you typically need to configure your service definitions and handlers accordingly. Here are some general steps to get started: @@ -25,7 +25,7 @@ For more detailed information on each protocol and how to implement them in CAP, - [OData APIs](odata.md) - [OpenAPI](openapi.md) - [AsyncAPI](asyncapi.md) -- [MCP](mcp.md) +- [MCP](mcp.md) These guides provide step-by-step instructions, examples, and best practices for working with each protocol in your CAP applications. From f4f0bfb4f8b9c2dddf6c3c8c3d7705beafd29f47 Mon Sep 17 00:00:00 2001 From: Marvin Lindner Date: Wed, 22 Jul 2026 14:25:17 +0200 Subject: [PATCH 3/7] remove internal instructions --- guides/protocols/mcp.md | 5 ----- 1 file changed, 5 deletions(-) diff --git a/guides/protocols/mcp.md b/guides/protocols/mcp.md index 5207af593..ebdbf50ea 100644 --- a/guides/protocols/mcp.md +++ b/guides/protocols/mcp.md @@ -22,7 +22,6 @@ The [Model Context Protocol (MCP)](https://modelcontextprotocol.io/) is an open- > The [SAP API Policy](https://api.sap.com/api-policy) remains applicable even when exposing data via MCP. Before exposing any SAP service or data through an MCP endpoint, ensure your use case complies with the SAP API Policy and any applicable licensing terms. - ## Preliminaries Following are one-time preparatory setup tasks. Basically, you need to ensure that you have access to LLM(s) to use with your MCP clients in local test-drives. @@ -74,10 +73,6 @@ Add this to the *srv/pom.xml*: ``` -Make sure internal artifactory is configured for Maven build as described in [*Java > Getting Started > Setting Up Local Development*](../../java/getting-started.md#local). - - - ## Serving MCP From e6fe5725cc3eec022dc450b36750105b157d862d Mon Sep 17 00:00:00 2001 From: Marvin Lindner Date: Thu, 23 Jul 2026 09:21:25 +0200 Subject: [PATCH 4/7] add back the java note due to the mills ... --- guides/protocols/mcp.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/guides/protocols/mcp.md b/guides/protocols/mcp.md index ebdbf50ea..34050b152 100644 --- a/guides/protocols/mcp.md +++ b/guides/protocols/mcp.md @@ -74,6 +74,8 @@ Add this to the *srv/pom.xml*: ``` +Make sure internal artifactory is configured for Maven build as described in [*Java > Getting Started > Setting Up Local Development*](../../java/getting-started.md#local). + ## Serving MCP ### Annotate services with `@mcp` From d76f409d529989afd1b7732a759364149ad0cc89 Mon Sep 17 00:00:00 2001 From: Maximilian Eckert Date: Thu, 23 Jul 2026 09:56:42 +0200 Subject: [PATCH 5/7] fix link --- guides/protocols/mcp.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/guides/protocols/mcp.md b/guides/protocols/mcp.md index 5207af593..45d310037 100644 --- a/guides/protocols/mcp.md +++ b/guides/protocols/mcp.md @@ -19,7 +19,7 @@ The [Model Context Protocol (MCP)](https://modelcontextprotocol.io/) is an open- > [!warning] SAP API Policy Applies > -> The [SAP API Policy](https://api.sap.com/api-policy) remains applicable even when exposing data via MCP. Before exposing any SAP service or data through an MCP endpoint, ensure your use case complies with the SAP API Policy and any applicable licensing terms. +> The [SAP API Policy](https://help.sap.com/doc/sap-api-policy) remains applicable even when exposing data via MCP. Before exposing any SAP service or data through an MCP endpoint, ensure your use case complies with the SAP API Policy and any applicable licensing terms. From 17011f9086bd82e5fedb6efd4bba4d86f38752d4 Mon Sep 17 00:00:00 2001 From: Simon Engel Date: Thu, 23 Jul 2026 10:00:32 +0200 Subject: [PATCH 6/7] fix link --- guides/protocols/mcp.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/guides/protocols/mcp.md b/guides/protocols/mcp.md index 9be8b1bf5..eff2a2ac5 100644 --- a/guides/protocols/mcp.md +++ b/guides/protocols/mcp.md @@ -19,7 +19,7 @@ The [Model Context Protocol (MCP)](https://modelcontextprotocol.io/) is an open- > [!warning] SAP API Policy Applies > -> The [SAP API Policy](https://help.sap.com/doc/sap-api-policy) remains applicable even when exposing data via MCP. Before exposing any SAP service or data through an MCP endpoint, ensure your use case complies with the SAP API Policy and any applicable licensing terms. +> The [SAP API Policy](https://help.sap.com/doc/sap-api-policy/latest/en-US/API_Policy_latest.pdf) remains applicable even when exposing data via MCP. Before exposing any SAP service or data through an MCP endpoint, ensure your use case complies with the SAP API Policy and any applicable licensing terms. ## Preliminaries From c251b1dae707465e46e82c9b1082facf03d32011 Mon Sep 17 00:00:00 2001 From: Simon Engel Date: Thu, 23 Jul 2026 10:02:40 +0200 Subject: [PATCH 7/7] Update guides/protocols/mcp.md --- guides/protocols/mcp.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/guides/protocols/mcp.md b/guides/protocols/mcp.md index eff2a2ac5..9be8b1bf5 100644 --- a/guides/protocols/mcp.md +++ b/guides/protocols/mcp.md @@ -19,7 +19,7 @@ The [Model Context Protocol (MCP)](https://modelcontextprotocol.io/) is an open- > [!warning] SAP API Policy Applies > -> The [SAP API Policy](https://help.sap.com/doc/sap-api-policy/latest/en-US/API_Policy_latest.pdf) remains applicable even when exposing data via MCP. Before exposing any SAP service or data through an MCP endpoint, ensure your use case complies with the SAP API Policy and any applicable licensing terms. +> The [SAP API Policy](https://help.sap.com/doc/sap-api-policy) remains applicable even when exposing data via MCP. Before exposing any SAP service or data through an MCP endpoint, ensure your use case complies with the SAP API Policy and any applicable licensing terms. ## Preliminaries