Skip to content

Minor adjustments to mcp.md #2772

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
qmacro wants to merge 5 commits into
base: main
Choose a base branch
from
+8 −5
Open

Minor adjustments to mcp.md #2772

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
7e9c74d
Adjust title and fix typo for Using Specific MCP Services section of …
qmacro Jul 24, 2026
0bffa60
clarification improvement to mcp.md
qmacro Jul 24, 2026
ff409e9
Add note on "MCP server" terminology
qmacro Jul 24, 2026
f78c502
"MCP protocol" is tautalogical, doh!
qmacro Jul 24, 2026
d28217f
Adjust title of mcp.md to avoid tautology
qmacro Jul 24, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 8 additions & 5 deletions guides/protocols/mcp.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@ synopsis: >
Expose CAP services via the Model Context Protocol for seamless AI agent integration.
---

# MCP Protocol Adapter <Beta />
# Model Context Protocol Adapter <Beta />



Expand Down Expand Up @@ -116,9 +116,9 @@ annotate CatalogService with @mcp:'books'
> From the perspective of a developer in a CAP-based project, `@mcp` is just another protocol for your services, similar to `@odata`, `@graphql`, `@rest`, or `@hcql`. The adapter takes care of the rest, with all the standard CAP features you know working out of the box also with MCP, including annotations like `@cds.query.limit`, etc.


### Using Specific MCP Services
### Tailored services for MCP use

In case you want to serve tailor the entities or elements served via MCP you can also create specific services for MCP and annotate only those with `@mcp`. For example, you could create a `BooksService` that only exposes a subset of the entities of the `AdminService` like that:
In case you want to tailor the entities or elements served via MCP you can also create specific services for MCP and annotate only those with `@mcp`. For example, you could create a `BooksService` that only exposes a subset of the entities of the `AdminService` like that:

::: code-group
```cds [srv/books-service.cds]
Expand Down Expand Up @@ -321,9 +321,12 @@ INFO com.sap.cds.adapter.mcp.McpServlet : Received MCP query request for entity

### Autowired MCP Clients

Whenever you start your application, the MCP adapter automatically registers all MCP endpoints with local MCP clients – currently supported for [Claude Code](https://code.claude.com/docs) and [Opencode](https://opencode.ai/) - so you can just go ahead and run queries from your MCP client without any additional configuration. This makes it super easy to test and interact with your services via MCP during development.
Whenever you start your application, the MCP adapter automatically registers all MCP servers with local MCP clients – currently supported for [Claude Code](https://code.claude.com/docs) and [Opencode](https://opencode.ai/) - so you can just go ahead and run queries from your MCP client without any additional configuration. This makes it super easy to test and interact with your services via MCP during development.

During startup, the generated MCP servers and their URL are added to the client-specific configuration files like that:
> [!tip] MCP servers
> Note the distinction between the CAP server that listens on a certain port, and MCP servers which are just endpoints provided and served by the CAP server. We use the term "MCP server" despite this, to align with MCP terminology.

During startup, information about the MCP server endpoints is added to the client-specific configuration files like that:

::: code-group
```json [~/.claude.json]
Expand Down
Loading