Skip to content
CAP and ABAP with MCP: Building AI Agents on SAP BAIP
Architecture · ·8 min read

CAP and ABAP with MCP: Building AI Agents on SAP BAIP

Michael Suter

Michael Suter

Senior SAP BAIP Architect, Spadoom AG

Share

In 2026 MCP arrived in both SAP programming models. CAP can serve any service as an MCP endpoint, ABAP has an MCP server for the IDE, and Joule Studio builds agents on SAP Business AI Platform (BAIP, formerly BTP). That is a lot of new tooling in a few months, at very different maturity levels. This post sorts it out, with the status as of 30 October 2026.

TL;DR: CAP’s MCP adapters are generally available for Node.js and Java since September 2026. CAP-level agents (@agent, served via A2A) are Gamma for Node.js and Alpha for Java. The ABAP MCP server for Eclipse and VS Code is GA. Joule Studio is in phased GA. Use CAP for MCP endpoints on your own extensions, Joule Studio for agents that live in Joule.

For the TechEd announcements around it, read our TechEd 2026 summary.

What is MCP, and why does it matter for SAP extensions?

The Model Context Protocol (MCP) lets an AI client, such as a coding assistant or an agent, discover and call tools on a server in a standard way. For SAP it means your own services can become tools that agents call, without custom glue code per model. SAP’s agent-to-agent protocol support (A2A) is the counterpart for agents calling agents.

At TechEd 2026 SAP said every agent is natively an A2A endpoint and that agents not verified in SAP AI Agent Hub cannot be invoked at runtime (SAP keynote recap). So the plumbing is standard, and governance is a gate, not an afterthought.

CAP: MCP endpoints from annotations

CAP introduced the MCP adapter in its June 2026 release as beta for Node.js. The release notes describe @mcp as “just another protocol for your services”, like @odata or @rest. The adapter serves an MCP endpoint with tools to describe the model, query data and call actions, and during cds watch it configures Claude Code and OpenCode as clients automatically.

In the September 2026 release the MCP adapters became generally available for Node.js and Java. That makes them a real option for production extensions: a Sales Cloud V2 or S/4HANA extension built in CAP can expose its read and write operations to an agent with an annotation.

What we would watch:

  • Authorization stays yours. The MCP endpoint is another protocol on the same service. Test who can call what through it as carefully as you would for an OData endpoint.
  • Start read-only. Expose queries first, actions later, and only with human approval.

CAP-level agents: promising, still experimental

CAP-level agents are services annotated with @agent, served via A2A. In the September release they are labelled Gamma for Node.js, “quite mature and tested in productive projects” according to the release notes, and Alpha for Java. The October 2026 release added several pieces that matter in practice:

  • @cap-js/agents 0.9.8 with a provider for OpenAI-compatible models.
  • One generic call tool for actions, which honours @agent.hitl and asks the user for approval before the action runs.
  • Streamed tool progress for A2A clients.
  • OpenTelemetry traces and token-use metrics for agents and MCP, so you can see whether time goes to the model or the database.
  • Persistent agent memory for CAP Java, explicitly Alpha and “not for production use”.

Concretely: use CAP-level agents for pilots inside your own applications, with @agent.hitl on every action that changes data. Wait with production use until the Java side matures, if you are on Java.

ABAP: an MCP server for the IDE

For S/4HANA teams, SAP’s ABAP update of 18 August 2026 brought three relevant facts:

  • The ABAP MCP server for Eclipse and Visual Studio Code is generally available.
  • ABAP development in Visual Studio Code started in Q2 2026, initially for the ABAP Cloud scope.
  • SAP released a first agent for custom code migration in Q2 2026; the article scheduled a clean-core transformation agent for Q3 2026, and we have not confirmed its current availability.

What the MCP server changes in daily work: your coding assistant can read the released objects and APIs of your system instead of guessing them. On ABAP Cloud in S/4HANA Public Cloud, where only released APIs are allowed, that is a real gain. Our post on embedded Steampunk and ABAP Cloud explains the extension model it plugs into.

Joule Studio: agents that live in Joule

Joule Studio is SAP’s tool for building agents and skills that run in Joule. When SAP introduced the new Joule Studio in May 2026, it named pro-code support for LangChain, Pydantic AI and LlamaIndex, extension from VS Code, Cursor and other agentic IDEs, agent memory on SAP HANA Cloud and runtime sandboxes on NVIDIA OpenShell. As of the Q3 2026 release highlights, general availability is underway in phases; the agent builder is free until December 2026 and then becomes a premium AI feature.

Which tool for which job?

You want to Use Status as of 30 October 2026
Make your CAP extension callable by agents CAP MCP adapter (@mcp) GA, Node.js and Java
Build an agent inside your own CAP application CAP-level agent (@agent, A2A) Gamma (Node.js), Alpha (Java)
Build an agent that lives in Joule and spans SAP systems Joule Studio GA underway in phases
Let a coding assistant work with your ABAP system ABAP MCP server (Eclipse, VS Code) GA
Let third-party agents call Joule Agents Agent gateway GA, enhanced interoperability in phases

The pattern we like: business logic and data stay in a clean CAP or ABAP Cloud extension, exposed through MCP with proper authorization. Agents, whether in Joule Studio or elsewhere, call those tools. That keeps the logic testable and upgrade-safe, and it lets you swap the agent layer without touching the core. It is the clean core approach with CAP we already use, with one more protocol.

Spadoom’s view

We build our own products on SAP BAIP: Engage, our extensions for SAP Sales and Service Cloud V2, runs multi-tenant there. For us MCP is not a new architecture; it is a new door into services we already run. That is the right way to think about it in your landscape too. Let’s not reinvent the wheel: the extension that is clean today is the tool an agent can use tomorrow.

Next step

Want to know which of your CAP or ABAP extensions could become agent tools, and what that means for authorization and operations? Start with our SAP BAIP solution page or our Business AI page, or talk to us directly. We look at one extension with you and sketch the MCP or agent setup.

FAQ

Is the MCP adapter in SAP CAP production-ready?

Yes. CAP introduced the MCP adapter as beta in its June 2026 release and made it generally available for Node.js and Java in the September 2026 release. With the @mcp annotation, a CAP service is served as an MCP endpoint, much like @odata or @rest.

What are CAP-level agents?

Agents declared with @agent on a CAP service, served via the Agent-to-Agent protocol (A2A). In the September 2026 release they are labelled Gamma for Node.js and Alpha for Java. Since October 2026 the generic call tool honours @agent.hitl and asks a user for approval before the action runs.

Is there an MCP server for ABAP?

Yes. According to SAP’s ABAP update of 18 August 2026, the ABAP MCP server for Eclipse and Visual Studio Code is generally available. ABAP development in Visual Studio Code started in Q2 2026, initially for the ABAP Cloud scope.

When should I use Joule Studio instead of CAP?

Use Joule Studio when the agent should live in Joule and be governed in SAP AI Agent Hub, for example a business assistant across SAP systems. Use CAP when the logic belongs to your own extension and you want an MCP endpoint or an agent next to your data model. Both meet at A2A and MCP.

SAP CAPABAP CloudMCPA2AJoule StudioSAP Business AI PlatformBAIPAI Agents
Ask Spadoom · AI assistant

Ask Spadoom

Answers drawn from what Spadoom has published on this site, with links to the pages they come from.

Try one of these

Enter to send · Shift+Enter for a new line 0 / 600
Continue with an expert Opens the contact form with your question filled in.

AI-generated answers. Verify before acting. Questions are stored anonymously, without your IP address, so we can improve our content. Please do not enter personal data.

Next step

SAP Business AI Platform (BTP) implementation partner

Spadoom is the SAP Business AI Platform (BTP) implementation partner across Switzerland, Germany, Austria and Italy. 14-week median go-live. Live customers across DACH.

Related articles

Insights 8 min read

SAP TechEd 2026: What Developers and Architects Should Take Away

SAP TechEd 2026 ran from 27 to 29 October in Berlin. Joule Work and Joule Studio are in phased general availability, the agent gateway is generally available, and a lot more is planned for 2027. Our status table, sorted by GA, beta and roadmap, plus the CAP and ABAP news that are absent from SAP's written keynote recap.

Michael Suter · 30 Oct 2026
Read article →