AI & Analytics Legends The knowledge platform for SAP Analytics Sign inSign up
Guide

SAP CAP MCP server: what it does and where it stops

SAP CAP MCP server: what it does and where it stops — Analytics Legends section illustration for SAP analytics market intelligence (Datasphere, BDC, SAC, BW/4HANA)

As of 2026-10-18

Edited by , sole editor and publication director — 27 years in the SAP ecosystem. How these pages are produced, and where automation is used.

The SAP CAP MCP server (cap-js/mcp-server) is a local stdio server for coding agents. It offers two tools: a fuzzy search over the compiled CDS model and a local semantic search of the CAP documentation. Its README says the tools are not a stable API. A separate vendor plugin does something different: it turns your annotated CAP services into an MCP server.

Two different things called CAP MCP

The first is a development aid. The official CAP MCP server helps an assistant such as Claude Code or Cursor understand a CAP project: which entities, elements and services exist in the compiled model, and what the CAP documentation says. It does not run your services or touch data.

The second is a runtime exposure. The CAP MCP Plugin from Gavdi Labs generates an MCP server from annotated CAP services and serves them over a local /mcp HTTP endpoint. There the assistant calls your application's own operations. Mixing the two up is the commonest mistake: one reads your model, the other acts on your business logic.

What the official server lets an assistant do

Two tools, both read-only in nature. The model search is fuzzy, so an agent can find the right entity without guessing names or reading every CDS file. The documentation search is semantic and local, which means the CAP docs are indexed on the machine rather than fetched at query time. The practical effect is fewer invented CDS syntax and API calls in generated code, since the agent can check the documentation first.

SAP Build also lists CAP among its bundled MCP servers, alongside Fiori and UI5 (and an MDK server on the help portal), so a Build Code user gets it without separate setup. The server is Apache-2.0 licensed.

Stability and what that means

The README states the tools are not a stable API. For a consultant that has a concrete meaning: do not hard-code tool names into team automation or custom agent prompts, pin the version in your project, and re-test after upgrades. It is a productivity aid, not an interface contract.

The Gavdi plugin in more detail

The plugin is from a vendor, Apache-2.0, and reads annotations on your CAP services to decide what to expose. It serves a local /mcp HTTP endpoint. Because the exposure is driven by annotations, the security question becomes: who can add an annotation, and does the exposed operation inherit the CAP authorisation you already defined? Verify with a test user that lacks the role, not with the developer account.

The verified catalogue does not state its maturity or its authentication behaviour, so read the repository before you plan anything beyond a prototype.

Local or remote, and checks before production

The official server is stdio, so it lives on the developer machine. That is right for a development tool and wrong for anything shared. The plugin is HTTP on a local endpoint; moving it to a deployed CAP application on BTP means you now own authentication for an MCP route, which the MCP authorisation approach addresses with OAuth 2.0.

Before production: confirm which operations are exposed and that none writes data without a confirmation step; check that CAP roles and restrictions apply to the MCP route; log calls with the calling identity; keep the development-aid server out of deployed images.

Relation to Joule and agent platforms

Joule for Developers and agentic IDEs consume servers like this one in the developer workflow. A CAP application exposed through the plugin could be a tool provider for an agent platform, though SAP's governed route for enterprise APIs is the Integration Suite gateway. Analytics Legends runs its own read-only MCP server for firm, day-rate and opportunity data, and it is unrelated to CAP development.

What we cannot assert

Maturity and authentication behaviour of the Gavdi plugin, and transport for the SAP Build overview page, are not stated in the sources we verified (18 October 2026).

Frequently asked

Is the CAP MCP server official?

Yes. It is published by SAP in the cap-js organisation under Apache-2.0, and SAP Build lists it among its bundled servers.

Can it query my CAP service data?

No. Its two tools search the compiled CDS model and the CAP documentation. For calling services, the Gavdi plugin is the option, from a vendor rather than SAP.

Is it stable enough for a team?

As a development aid, yes, with the version pinned. The README says the tools are not a stable API, so avoid building automation on tool names.

stdio or HTTP?

The official server is stdio, local to the developer. The Gavdi plugin serves HTTP on a local /mcp endpoint.

Engage the editor

This guide is written by . 27 years of SAP — Datasphere, Business Data Cloud, SAC Planning, Joule. Freelance or permanent · Hybrid / remote · Anywhere in EMEA. Available from 19 October 2026.

Profile and contact

What this page is built on

External sources

Read next

Guides that answer with this page

These guides cite this page as one of the sources their answer rests on.