Claude SAP CAP connectorWhat Claude can look up in your CAP project and docs.
The Claude SAP CAP connector exposes 2 tools. Both are read tools, 0 write anything, and none goes undocumented. Below: what Claude finds in your CDS model, how it searches the CAP docs, and why every lookup runs on your own machine.
Verified Trustpilot reviews · AI, automation & growth agency
Why a CAP developer would plug this in
SAP describes this server as help for developing CAP projects: it searches the definitions of your compiled CDS model and the CAP documentation. The questions SAP gives as examples are about which CDS services a project holds and where they are served, what its entities are about and how they relate, and how to add columns to a select statement in CAP Node.js.
Find a definition from a rough name. search_model runs a fuzzy search on the names of definitions in your compiled CDS model. Per SAP, that model carries the project's definitions, their relationships, annotations and HTTP endpoints.
Search the docs without the exact wording. search_docs compares your question by meaning with a preprocessed copy of the CAP documentation, so your words do not have to match the text. SAP says that search runs locally, on your machine.
Ask about the project in plain words. The questions SAP lists concern services, entities and how they relate, or how a CAP Node.js query is written. The connector is a local extension that the directory lists for Claude Desktop only.
What it will not do: by default, its directory sheet only shows read tools, and nothing fires in the background when you save a model, since Claude calls the tools while it answers you. Unattended pipelines are a different trade; the Integrations hub covers that side.
Five terms before you connect SAP CAP
The vocabulary this page relies on.
- Connector
- A link you set up once between Claude and a tool you already use, so Claude can call on it while it answers you.
- Tool
- One named capability a connector hands to Claude. Claude decides which ones to call; the directory sheet lists them by name.
- Local extension
- A connector installed on your own computer and launched by Claude Desktop rather than a remote service. This one is local.
- Approval
- The confirmation Claude waits for in the conversation before it carries out something that changes things on your behalf.
- MCP
- The shared standard connectors are built on: it is what lets an assistant like Claude talk to an outside program or service.
How to connect SAP CAP to Claude
- 01
Find it in Claude Desktop
Open Claude Desktop settings, go to Customize, then Connectors, and search for SAP CAP. The directory lists it for the desktop app only, not for Claude on the web.
- 02
Add it from its row
Click Connect on the SAP CAP row. In a Team or Enterprise workspace, an Owner or Primary Owner has to switch the connector on before individual members can add it.
- 03
Read before you confirm
If an authorization screen shows up, read it before you accept: it sets the scope of access. A broken link is fixed with Disconnect and a fresh connection.
The 2 tools behind the Claude SAP CAP connector
SAP CAP MCP Server gives Claude 2 tools: 2 that read your account, 0 that change something in it.
Two tools, both read-only lookups. Names stay exactly as Claude shows them.
- 2 read
What Claude reads (2)
2 toolsOne search runs against your model, the other against the docs.
search_model
Looks up a definition in your compiled CDS model by name, even a partial or misspelled one. The compiled model holds every definition, how they relate, their annotations and the project's HTTP endpoints.
search_docs
Queries a preprocessed copy of the CAP documentation by semantic similarity instead of exact keywords, without leaving your machine.
What Claude asks before it acts
By default, Claude stops and asks for your go-ahead before any action it takes on your behalf. Here both tools only search.
In a Team or Enterprise workspace, owners decide whether members may let certain actions through without being asked every time. Owners can also cap what a connector is allowed to do across the whole organization, and nobody overrides that from their own account. Claude never gets more reach than you have: whatever is off limits to you on your machine or in your project stays off limits to it, however you phrase the request.
Which plans include it
Not one of the 819 directory sheets shows plan availability. For SAP CAP, as for every other connector, that answer is not published anywhere.
The general rule is published, though: desktop extensions install on Claude Desktop, while remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner enables a connector before members can use it. Check the SAP CAP sheet in the official directory for its current status.
Where SAP CAP stops
A connector is not an automation. Claude calls these tools while it is answering you; nothing starts on its own when a file changes.
Treat the tool list as an observed floor, not a promise: an admin can open up capabilities that appear on no public sheet. The partner badge is not a security audit either, and Anthropic says so on every sheet: it does not pick the tools a publisher exposes and does not vouch for how they behave. Only SAP documents this connector, in its server repository; neither Claude's help center nor Anthropic's developer docs cover it. For other ways to wire up your stack, browse Integrations.
Need help connecting SAP CAP MCP Server to Claude?
A person reads every message.