onedevatlasBeta
Browse the atlas
AllCAPUI5ABAPBTP
PackagePackagetypeA library you install and call yourself.See every one →What this type is →by SAPby SAPoriginPublished by SAP itself. A visible facet, never an input to a reading — a dormant official plugin reads exactly like a dormant independent one.See every one →

com.sap.cds:cds-adapter-mcp

The MCP protocol adapter for CAP Java, serving an @mcp-annotated Application Service as an MCP server with three generated tools, describe, query and call, and data changes only through unbound actions.

Turns an @mcp-annotated Application Service into an MCP server, so an agent calls it through three generic tools generated from the model: describe, query and call. Its version comes from com.sap.cds:cds-services-bom; the module is added to srv/pom.xml with runtime scope, the CAP Java route to the same adapter capire documents for Node.js as @cap-js/mcp. It stops at reading and at unbound actions: a data change has to be modelled as an unbound action, since there is no direct create, update or delete over MCP. During mvn cds:watch it also autowires the endpoint into a local agent's configuration, adding Basic credentials for the mock user privileged, credentials that mean nothing once the mocked auth strategy is out of the picture.

Homepage
Docs

Facts

LicenceSAP DEVELOPER LICENSE AGREEMENT for CAP

Where it sits

Lives in
CAP
Provides
Serve your application over MCPCAPServe your application over MCPcapabilityExposing selected application data and business operations to an AI agent through the Model Context Protocol. An application may also integrate remote services through [service integration](capability:service-integration), connecting its exposed contract with [agent access to your systems](capability:agent-systems-access). Development assistance belongs to [agent access to your code](capability:agent-code-access).
Flavors
Java

Before choosing this

Conditions

PracticalFunctional boundary

SAP prohibits gateway/proxy use for SAP Application APIs; the Atlas separately excludes CAP wrappers around those APIs from its assessed scope. Data changes require application-defined unbound actions, and the adapter supplies no rate limiting, agent-action audit logging, approval workflows or policy enforcement.

PolicySAP API Policy 4.2026a§ 1.1, 1.2, 2.2.2from Serve your application over MCPAn MCP server exposes an SAP API, or uses SAP APIs to supply tools, resources or data to an agent.
  • § 1.1 Published APIs. Published APIs are made available for the documented purposes identified by SAP, including integration, extensions and data exchange.
  • § 1.2 Non-Published APIs. Customer and third-party applications must not access non-published APIs except where documentation permits it or SAP otherwise authorizes it.
  • § 2.2.2 AI call sequences and data extraction. Outside SAP-endorsed architectures, data services or expressly identified pathways, the policy prohibits specified agentic API use and systematic or large-scale extraction.

MCP does not replace the API's documented-use boundary. Check that every endpoint is published for the intended use and whether the policy's AI-call or extraction provisions apply to the design.

SAP API Policy 4.2026a →
LicenceSAP Developer License Agreement 3.2 CAP§ 1, 3from Serve your application over MCPA covered CAP plugin or application exposes SAP product data or covered customer-application functionality through MCP.
  • § 1 License. Productive customer applications are limited to SAP BTP or another SAP-licensed platform, and mass extraction to a non-SAP product is restricted except where solely required for SAP interoperability.
  • § 3 Artificial Intelligence Training. The agreement prohibits use of the covered materials and customer applications for training artificial-intelligence models or systems.

The CAP developer agreement can apply alongside the API Policy. Ordinary agent inference is not automatically AI training; section 3 becomes relevant when covered materials or applications are used to train, develop or refine a model or system.

SAP Developer License Agreement 3.2 CAP →

What it declares

Every artifact

Type
Package
Origin
By SAP
Runtime
Java

As a package

Where it runs
does not say
Distributed through
does not say

For serve your application over MCP

Exposure source
CAP service contract
Exposed operations
Read queries and unbound actions/functions; changes require application-defined unbound actions
Context delivery
Model descriptions via toolsServer instructions
Execution path
CAP service calls
Exposure control
Service selection

Tasks this contributes to5Beta

Serve your application over MCP5
Access an external system through an application MCP serviceAn AI agent queries external system data or invokes selected external operations through an application-owned service contract exposed over MCP.Java2 scopes
CAP JavaCovers, under conditions

Dated assessment history · last accepted 2026-10-12. Excluded from the current connected answer.

What it does

com.sap.cds:cds-adapter-mcp exposes the custom application service for discovery, data queries and unbound operations; it does not implement the remote-system integration.

Conditions

Expose a custom CAP application service with @mcp; SAP Application API gateway/proxy scenarios are excluded.; Use reading queries and unbound actions/functions; changes require unbound actions.; Provide deployment authorization; out-of-the-box XSUAA PKCE support is not fully implemented.; Supply prompt-injection mitigation and governance controls; the adapter supplies no automatic rate limiting, agent-action audit logging, approval workflows or policy layer.; Treat generated tools as a changing interface; validate the application handlers and selected remote API separately.; Add cds-adapter-mcp with runtime scope; enable model doc comments in the Java application and MTX sidecar when using that context.

Remaining work

Implement and test the custom service handlers and remote calls, and configure client access and productive controls.

All options on the Serve your application over MCP page →
CAP JavaStated not supported

Dated assessment history · last accepted 2026-10-12. Excluded from the current connected answer.

What it does

com.sap.cds:cds-adapter-mcp must not be used as a gateway or proxy for SAP Application APIs; placing a CAP application service in front of the API does not remove that prohibition.

Conditions

This assessment targets SAP Application APIs, including an application service that proxies those APIs.

Remaining work

Choose a separately assessed exposure design; no workaround is established by wrapping or renaming the target API.

All options on the Serve your application over MCP page →
Change application records from an agentCreate or update application records through an MCP client.JavaCovers, under conditionsbusiness-action adapter
What it does

com.sap.cds:cds-adapter-mcp can invoke unbound actions that perform application data changes; the documented adapter does not generate direct entity CREATE, UPDATE or DELETE tools.

Conditions

Add the cds-adapter-mcp runtime dependency to the CAP Java application.; Annotate the custom application service with @mcp; choose the exposed entities and operations.; Implement each required record change through an unbound business action.; The guide records incomplete out-of-the-box XSUAA authorization with PKCE; choose and validate deployment authorization accordingly.; Enable model doc comments in the Java application and MTX sidecar when supplying that context through describe.

Remaining work

Own action logic, validation and authorization; this does not establish draft lifecycle support.

All options on the Serve your application over MCP page →
Expose an application service to an AI agentLet an MCP client discover and query application data and invoke selected business operations.JavaCovers, under conditionsapplication adapter
What it does

com.sap.cds:cds-adapter-mcp exposes an annotated custom service for model discovery, querying and invocation of unbound actions and functions.

Conditions

Add the cds-adapter-mcp runtime dependency to the CAP Java application.; Annotate the custom application service with @mcp. Use a dedicated MCP service to restrict the exposed entities and operations.; Provide deployment authorization; the guide records incomplete out-of-the-box XSUAA PKCE support.; Enable model doc comments in the Java application and MTX sidecar when supplying that context through describe.; Connect only trusted MCP agents and use deployment controls to mitigate prompt injection.; Generated tools are not stable APIs; supply application governance controls before productive use.; Use this adapter only for custom CAP application services, not as a gateway or proxy for SAP application APIs.

Remaining work

Configure the client, application descriptions and governance; no runtime deployment was tested by the Atlas.

All options on the Serve your application over MCP page →
Invoke a business operation from an agentInvoke a selected application business operation through an MCP tool.JavaCovers, under conditionsapplication adapter
What it does

com.sap.cds:cds-adapter-mcp generates a call tool for unbound application actions and functions.

Conditions

Add the cds-adapter-mcp runtime dependency to the CAP Java application.; Annotate the custom application service with @mcp. Use a dedicated MCP service to restrict the exposed entities and operations.; Implement and expose the unbound action or function and its required parameters.; The guide records incomplete out-of-the-box XSUAA authorization with PKCE; choose and validate deployment authorization accordingly.; Enable model doc comments in the Java application and MTX sidecar when supplying that context through describe.; Connect only trusted MCP agents and use deployment controls to mitigate prompt injection.; Generated tools are not stable APIs; supply application governance controls before productive use.; Use this adapter only for custom CAP application services, not as a gateway or proxy for SAP application APIs.

Remaining work

Implement business rules, validation and authorization in the application.

All options on the Serve your application over MCP page →
Query application data from an agentRetrieve selected application records through MCP without changing those records.JavaCovers, under conditionsapplication adapter
What it does

com.sap.cds:cds-adapter-mcp generates describe and query tools for entities exposed by an annotated service.

Conditions

Add the cds-adapter-mcp runtime dependency to the CAP Java application.; Annotate the custom application service with @mcp; choose the exposed entities and operations.; The guide records incomplete out-of-the-box XSUAA authorization with PKCE; choose and validate deployment authorization accordingly.; Enable model doc comments in the Java application and MTX sidecar when supplying that context through describe.

Remaining work

Shape the service projection and caller permissions; configure the client and deployment authorization.

All options on the Serve your application over MCP page →

Connections1

Download
com.sap.cds:cds-adapter-mcp connectionscom.sap.cds:cds-adapter-mcpPROVIDES→ provides1provides stated Exposes an @mcp-annotated CAP Java application service through generated describe, query and unbound-action/function tools. The query and call tools invoke the exposed service without direct CRUD tools; data changes require application-defined unbound actions. The describe tool returns model descriptions, and the adapter sends generic and custom server instructions to clients. Whole-service opt-in with @mcp can be narrowed through a dedicated service with selected projections and actions. Java doc comments require configuration in the application and MTX sidecar. Model Context Protocol Adapter — capire: https://cap.cloud.sap/docs/guides/ai/cap-mcp Model Context Protocol Adapter — capire: https://cap.cloud.sap/docs/guides/ai/cap-mcp com.sap.cds:cds-adapter-mcp — Maven POM: https://repo1.maven.org/maven2/com/sap/cds/cds-adapter-mcp/5.1.1/cds-adapter-mcp-5.1.1.pom Model Context Protocol Adapter | capire: https://cap.cloud.sap/docs/guides/ai/cap-mcp Model Context Protocol Adapter | capire: https://cap.cloud.sap/docs/guides/ai/cap-mcp Model Context Protocol Adapter | capire: https://cap.cloud.sap/docs/guides/ai/cap-mcp Model Context Protocol Adapter | capire: https://cap.cloud.sap/docs/guides/ai/cap-mcp Model Context Protocol Adapter | capire: https://cap.cloud.sap/docs/guides/ai/cap-mcp Model Context Protocol Adapter | capire: https://cap.cloud.sap/docs/guides/ai/cap-mcp Model Context Protocol Adapter | capire: https://cap.cloud.sap/docs/guides/ai/cap-mcp Model Context Protocol Adapter | capire: https://cap.cloud.sap/docs/guides/ai/cap-mcp Model Context Protocol Adapter | capire: https://cap.cloud.sap/docs/guides/ai/cap-mcp Model Context Protocol Adapter | capire: https://cap.cloud.sap/docs/guides/ai/cap-mcp Model Context Protocol Adapter | capire: https://cap.cloud.sap/docs/guides/ai/cap-mcpServe your application over MCP

Learn more1

Readings
  1. Model Context Protocol Adapter — CAP guideCapire Docs & Samples, capire

Others providing14

Compare all 15 on the Serve your application over MCP page →
Serve your application over MCP
  1. abap-ai/mcpMCP server SDK written in ABAPfrom ABAP
  2. abap-ai/mcp2Stateless ABAP MCP server SDK for the 2026-07-28 protocol draftfrom ABAP
  3. abap-agent-runtimeABAP-native MCP endpoint that drives opted-in abap2UI5 appsfrom ABAP
  4. API ManagementAPI proxies with security and traffic policies and Developer Hubfrom BTP/BAIP
  5. @cap-js/mcpExposes CAP services as MCP servers for AI agentsfrom CAP
  6. @gavdi/cap-mcpGenerates an MCP server from annotated CDS entities and actionsfrom CAP
  7. btp-cf-mcpMCP server for SAP BTP and Cloud Foundry acting as the logged-in userfrom BTP/BAIP
  8. MarkWuRY168/SAP_MCPMCP server publishing SAP functions as tools from config tablesfrom ABAP
  9. @neoimpulse/cap-js-mcpMCP server inside a CAP application with model and query toolsfrom CAP
  10. @odatano/core-mcpMCP server exposing the ODATANO Cardano-to-OData bridge as toolsfrom CAP
  11. @odatano/nightgate-mcpMCP server exposing the NIGHTGATE Midnight attestation layerfrom CAP
  12. @shahid.la/cds-db-nlquery-mcpMCP server answering plain-English questions against a CDS schemafrom CAP
  13. Skybuffer AI MCP serverABAP add-on serving business data and transactions as MCP toolsfrom ABAP
  14. cap-mcp-pluginMCP server generated from a CDS model, forked from @gavdi/cap-mcpfrom CAP

Details

Connected knowledge — wider context2

Source connections explain where this sits. Implementation claims remain in their exact task assessment.

Access an external system through an application MCP service · CAP Java application bridge for custom external APIs outside SAP Application APIs
View scoped assessment

Editorially accepted assessment · assessed . No Atlas runtime testing.

Evidence changed · needs review · evidence captured 2026-10-12, 2026-10-15, 2026-10-26

Supporting evidence changed; this accepted claim needs review.

Evidence status not tracked

Evidence observations do not cover this accepted claim; it is retained as dated history.

Why this assessment is relevant
  1. Access an external system through an application MCP service → CAP Java application bridge for custom external APIs outside SAP Application APIs
Relationships and evidence (10)

  • com.sap.cds:cds-adapter-mcp → provides → Serve your application over MCP

    Exposes an @mcp-annotated CAP Java application service through generated describe, query and unbound-action/function tools. The query and call tools invoke the exposed service without direct CRUD tools; data changes require application-defined unbound actions. The describe tool returns model descriptions, and the adapter sends generic and custom server instructions to clients. Whole-service opt-in with @mcp can be narrowed through a dedicated service with selected projections and actions. Java doc comments require configuration in the application and MTX sidecar.

    Basis: atlas-record

    Model Context Protocol Adapter — capire · checked 2026-09-19the plugin automatically creates an MCP server per CAP service, each serving three generic tools

    Model Context Protocol Adapter — capire · checked 2026-09-19the cds-adapter-mcp dependency to your srv/pom.xml for CAP Java projects

    com.sap.cds:cds-adapter-mcp — Maven POM · checked 2026-09-19MCP adapter for CDS Services Java

    Model Context Protocol Adapter | capire · checked 2026-10-12Simply add the @mcp annotation to a service definition to expose it via MCP.

    Model Context Protocol Adapter | capire · checked 2026-10-12This tool is used to read data from the service.

    Model Context Protocol Adapter | capire · checked 2026-10-12This tool is used to call unbound actions or functions.

    Model Context Protocol Adapter | capire · checked 2026-10-12while any data changes need to be implemented via unbound actions for now.

    Model Context Protocol Adapter | capire · checked 2026-10-12The CAP MCP adapter must not be used as a gateway or proxy for SAP Application APIs.

    Model Context Protocol Adapter | capire · checked 2026-10-12The adapter is not an SAP-endorsed architecture, data service, or service-specific pathway under section 2.2.2 of the SAP API Policy and is not an endorsed mechanism for exposing, proxying, or providing agentic access to SAP Application APIs.

    Model Context Protocol Adapter | capire · checked 2026-10-12This information is included in the output of the describe tool

    Model Context Protocol Adapter | capire · checked 2026-10-12The MCP Adapter automatically sends MCP instructions to MCP clients to help models understand how to interact with your services effectively.

    Model Context Protocol Adapter | capire · checked 2026-10-12You must enable doc comments in the Java application and in the MTX sidecar.

    Model Context Protocol Adapter | capire · checked 2026-10-12Use the @mcp.instructions annotation on service level, entity level, or action level to specify such custom instructions.

    Model Context Protocol Adapter | capire · checked 2026-10-12Instead of annotating an existing service with @mcp and exposing all its entities and actions, simply create a dedicated service specifically for MCP.

  • com.sap.cds:cds-feature-remote-odata → provides → Service integration

    Serves a remote OData V2 or V4 API as a CAP Remote Service in CAP Java: configured with the service definition from the CDS model and a destination or service binding, a CQN query against it is translated into the OData request.

    Basis: atlas-record

    Remote Services (CAP Java) — capire · checked 2026-09-27To enable Remote Services for OData V2 or V4 APIs in an application, add the following Maven dependency to your project

    com.sap.cds:cds-feature-remote-odata — POM (5.1.1) · checked 2026-09-27Consuming remote OData V2/V4 services using SAP Cloud SDK

  • cap-mcp-bridge → provides → Agent access to your systems

    Canonical Atlas provides relationship.

    Basis: atlas-record

  • Access an external system through an application MCP service → associatedWith → Serve your application over MCP

    Assessment home

    Basis: atlas-record

  • Access an external system through an application MCP service → associatedWith → Agent access to your systems

    Reach external system data and operations through the application.

    Basis: atlas-record

  • Access an external system through an application MCP service → associatedWith → Service integration

    Connect the application service to the external system.

    Basis: atlas-record

  • CAP Java application bridge for custom external APIs outside SAP Application APIs → assesses → Access an external system through an application MCP service

    One shared outcome, one scoped assessment.

    Basis: atlas-assessment

  • com.sap.cds:cds-feature-remote-odata → previouslyContributedTo → CAP Java application bridge for custom external APIs outside SAP Application APIs

    Last accepted assessment (2026-10-12): com.sap.cds:cds-feature-remote-odata consumes configured OData V2 or V4 APIs through CAP Java Remote Services; application handlers must call them explicitly.

    Basis: atlas-assessment · dated relationship; evidence needs review

    Evidence status not tracked

    Evidence observations do not cover this accepted claim; it is retained as dated history.

    https://cap.cloud.sap/docs/java/cqn-services/remote-services · checked 2026-10-12To enable Remote Services for OData V2 or V4 APIs in an application, add the following Maven dependency to your project:

    https://cap.cloud.sap/docs/java/cqn-services/remote-services · checked 2026-10-12CAP doesn't automatically forward CQN queries to these services.

    https://cap.cloud.sap/docs/java/cqn-services/remote-services · checked 2026-10-12In case data from Remote Services should be combined with data from the database custom coding is required.

  • com.sap.cds:cds-adapter-mcp → previouslyContributedTo → CAP Java application bridge for custom external APIs outside SAP Application APIs

    Last accepted assessment (2026-10-12): com.sap.cds:cds-adapter-mcp exposes the custom application service for discovery, data queries and unbound operations; it does not implement the remote-system integration.

    Basis: atlas-assessment · dated relationship; evidence needs review

    Evidence status not tracked

    Evidence observations do not cover this accepted claim; it is retained as dated history.

    https://cap.cloud.sap/docs/guides/ai/cap-mcp · checked 2026-10-12The CAP MCP adapter is intended only for exposing custom CAP application services.

    https://cap.cloud.sap/docs/guides/ai/cap-mcp · checked 2026-10-12the plugin automatically creates an MCP server per CAP service, each serving three generic tools

    https://cap.cloud.sap/docs/guides/ai/cap-mcp · checked 2026-10-12any data changes need to be implemented via unbound actions for now.

    https://cap.cloud.sap/docs/guides/ai/cap-mcp · checked 2026-10-12out-of-the-box support for authorization with XSUAA, with PKCE, but it is not fully implemented yet.

    https://cap.cloud.sap/docs/guides/ai/cap-mcp · checked 2026-10-12The MCP adapter does not perform any input validation or output validation to prevent prompt injection attacks.

    https://cap.cloud.sap/docs/guides/ai/cap-mcp · checked 2026-10-12there is no automatic rate limiting, no specific audit logging of agent actions, no approval workflows for sensitive operations, and no policy enforcement layer.

  • cap-mcp-bridge → previouslyContributedTo → CAP Java application bridge for custom external APIs outside SAP Application APIs

    Last accepted assessment (2026-10-12): cap-mcp-bridge derives MCP tools from the CAP application service's OData V4 metadata; it is outside the application and does not implement its outbound integration.

    Basis: atlas-assessment · dated relationship; evidence needs review

    Evidence status not tracked

    Evidence observations do not cover this accepted claim; it is retained as dated history.

    https://github.com/SanoberRehman/cap-mcp-bridge · checked 2026-10-12Point it at any SAP CAP / OData v4 service.

    https://github.com/SanoberRehman/cap-mcp-bridge · checked 2026-10-12**Read-only by default.** Write tools only exist when `writeEnabled: true` (`--write`).

    https://github.com/SanoberRehman/cap-mcp-bridge · checked 2026-10-12`invoke_action` | Call an action. **Write mode only**

Gaps, source snapshot and retrieval limits
  • The application integration and MCP contributions are assessed separately; no captured source shows these complete generic bridge paths working against a chosen external system.
  • The selected target API, client and backend permissions, tenant mapping and remote error behavior need a project-specific assessment.
  • A compatible component does not establish an endorsed architecture or permission to expose an SAP Application API.
  • The external MCP process is assessed against the exposed OData V4 contract, not as a Java library; no Java in-process community adapter was established in this bounded inventory.
  • Evidence observations do not cover this accepted claim; it is retained as dated history.
  • Supporting evidence changed; this accepted claim needs review.
  • Retrieval uses at most four typed steps within a bounded source index. Source relationships do not establish compatibility.

Developers snapshot checked 2026-10-05 · 33 indexed records from a 9,023-node source snapshot. This is a bounded retrieval view; absence is not evidence that no solution exists. Source relationships and proximity do not establish runtime compatibility.

Mapping version: connected-tasks-2026-10-06-v4+mcp-records-b256b58cfb844590. Task and mapping evidence remain separate from implementation evidence.

Access an external system through an application MCP service · CAP Java application bridge for SAP Application APIs
View scoped assessment

Editorially accepted assessment · assessed . No Atlas runtime testing.

Evidence changed · needs review · evidence captured 2026-10-12, 2026-10-15, 2026-10-26

Supporting evidence changed; this accepted claim needs review.

Evidence status not tracked

Evidence observations do not cover this accepted claim; it is retained as dated history.

Why this assessment is relevant
  1. Access an external system through an application MCP service → CAP Java application bridge for SAP Application APIs
Relationships and evidence (10)

  • com.sap.cds:cds-adapter-mcp → provides → Serve your application over MCP

    Exposes an @mcp-annotated CAP Java application service through generated describe, query and unbound-action/function tools. The query and call tools invoke the exposed service without direct CRUD tools; data changes require application-defined unbound actions. The describe tool returns model descriptions, and the adapter sends generic and custom server instructions to clients. Whole-service opt-in with @mcp can be narrowed through a dedicated service with selected projections and actions. Java doc comments require configuration in the application and MTX sidecar.

    Basis: atlas-record

    Model Context Protocol Adapter — capire · checked 2026-09-19the plugin automatically creates an MCP server per CAP service, each serving three generic tools

    Model Context Protocol Adapter — capire · checked 2026-09-19the cds-adapter-mcp dependency to your srv/pom.xml for CAP Java projects

    com.sap.cds:cds-adapter-mcp — Maven POM · checked 2026-09-19MCP adapter for CDS Services Java

    Model Context Protocol Adapter | capire · checked 2026-10-12Simply add the @mcp annotation to a service definition to expose it via MCP.

    Model Context Protocol Adapter | capire · checked 2026-10-12This tool is used to read data from the service.

    Model Context Protocol Adapter | capire · checked 2026-10-12This tool is used to call unbound actions or functions.

    Model Context Protocol Adapter | capire · checked 2026-10-12while any data changes need to be implemented via unbound actions for now.

    Model Context Protocol Adapter | capire · checked 2026-10-12The CAP MCP adapter must not be used as a gateway or proxy for SAP Application APIs.

    Model Context Protocol Adapter | capire · checked 2026-10-12The adapter is not an SAP-endorsed architecture, data service, or service-specific pathway under section 2.2.2 of the SAP API Policy and is not an endorsed mechanism for exposing, proxying, or providing agentic access to SAP Application APIs.

    Model Context Protocol Adapter | capire · checked 2026-10-12This information is included in the output of the describe tool

    Model Context Protocol Adapter | capire · checked 2026-10-12The MCP Adapter automatically sends MCP instructions to MCP clients to help models understand how to interact with your services effectively.

    Model Context Protocol Adapter | capire · checked 2026-10-12You must enable doc comments in the Java application and in the MTX sidecar.

    Model Context Protocol Adapter | capire · checked 2026-10-12Use the @mcp.instructions annotation on service level, entity level, or action level to specify such custom instructions.

    Model Context Protocol Adapter | capire · checked 2026-10-12Instead of annotating an existing service with @mcp and exposing all its entities and actions, simply create a dedicated service specifically for MCP.

  • com.sap.cds:cds-feature-remote-odata → provides → Service integration

    Serves a remote OData V2 or V4 API as a CAP Remote Service in CAP Java: configured with the service definition from the CDS model and a destination or service binding, a CQN query against it is translated into the OData request.

    Basis: atlas-record

    Remote Services (CAP Java) — capire · checked 2026-09-27To enable Remote Services for OData V2 or V4 APIs in an application, add the following Maven dependency to your project

    com.sap.cds:cds-feature-remote-odata — POM (5.1.1) · checked 2026-09-27Consuming remote OData V2/V4 services using SAP Cloud SDK

  • cap-mcp-bridge → provides → Agent access to your systems

    Canonical Atlas provides relationship.

    Basis: atlas-record

  • Access an external system through an application MCP service → associatedWith → Serve your application over MCP

    Assessment home

    Basis: atlas-record

  • Access an external system through an application MCP service → associatedWith → Agent access to your systems

    Reach external system data and operations through the application.

    Basis: atlas-record

  • Access an external system through an application MCP service → associatedWith → Service integration

    Connect the application service to the external system.

    Basis: atlas-record

  • CAP Java application bridge for SAP Application APIs → assesses → Access an external system through an application MCP service

    One shared outcome, one scoped assessment.

    Basis: atlas-assessment

  • com.sap.cds:cds-feature-remote-odata → previouslyContributedTo → CAP Java application bridge for SAP Application APIs

    Last accepted assessment (2026-10-12): com.sap.cds:cds-feature-remote-odata consumes configured OData V2 or V4 APIs through CAP Java Remote Services; application handlers must call them explicitly.

    Basis: atlas-assessment · dated relationship; evidence needs review

    Evidence status not tracked

    Evidence observations do not cover this accepted claim; it is retained as dated history.

    https://cap.cloud.sap/docs/java/cqn-services/remote-services · checked 2026-10-12To enable Remote Services for OData V2 or V4 APIs in an application, add the following Maven dependency to your project:

    https://cap.cloud.sap/docs/java/cqn-services/remote-services · checked 2026-10-12CAP doesn't automatically forward CQN queries to these services.

    https://cap.cloud.sap/docs/java/cqn-services/remote-services · checked 2026-10-12In case data from Remote Services should be combined with data from the database custom coding is required.

  • com.sap.cds:cds-adapter-mcp → previouslyContributedTo → CAP Java application bridge for SAP Application APIs

    Last accepted assessment (2026-10-12): com.sap.cds:cds-adapter-mcp must not be used as a gateway or proxy for SAP Application APIs; placing a CAP application service in front of the API does not remove that prohibition.

    Basis: atlas-assessment · dated relationship; evidence needs review

    Evidence status not tracked

    Evidence observations do not cover this accepted claim; it is retained as dated history.

    https://cap.cloud.sap/docs/guides/ai/cap-mcp · checked 2026-10-12The CAP MCP adapter must not be used as a gateway or proxy for SAP Application APIs.

    https://cap.cloud.sap/docs/guides/ai/cap-mcp · checked 2026-10-12The CAP MCP adapter is intended only for exposing custom CAP application services.

  • cap-mcp-bridge → previouslyContributedTo → CAP Java application bridge for SAP Application APIs

    Last accepted assessment (2026-10-12): cap-mcp-bridge documents CAP/OData V4 endpoint access, but these sources do not establish a supported or endorsed CAP bridge to the chosen SAP Application API.

    Basis: atlas-assessment · dated relationship; evidence needs review

    Evidence status not tracked

    Evidence observations do not cover this accepted claim; it is retained as dated history.

    https://github.com/SanoberRehman/cap-mcp-bridge · checked 2026-10-12Point it at any SAP CAP / OData v4 service.

    https://github.com/SanoberRehman/cap-mcp-bridge · checked 2026-10-12**Read-only by default.** Write tools only exist when `writeEnabled: true` (`--write`).

    https://github.com/SanoberRehman/cap-mcp-bridge · checked 2026-10-12`invoke_action` | Call an action. **Write mode only**

Gaps, source snapshot and retrieval limits
  • The application integration and MCP contributions are assessed separately; no captured source shows these complete generic bridge paths working against a chosen external system.
  • The selected target API, client and backend permissions, tenant mapping and remote error behavior need a project-specific assessment.
  • A compatible component does not establish an endorsed architecture or permission to expose an SAP Application API.
  • The official CAP MCP adapter is explicitly unsupported for this target scope. The community MCP implementations remain unknown for the complete SAP Application API bridge; their general service exposure does not establish that result.
  • The external MCP process is assessed against the exposed OData V4 contract, not as a Java library; no Java in-process community adapter was established in this bounded inventory.
  • Evidence observations do not cover this accepted claim; it is retained as dated history.
  • Supporting evidence changed; this accepted claim needs review.
  • Retrieval uses at most four typed steps within a bounded source index. Source relationships do not establish compatibility.

Developers snapshot checked 2026-10-05 · 33 indexed records from a 9,023-node source snapshot. This is a bounded retrieval view; absence is not evidence that no solution exists. Source relationships and proximity do not establish runtime compatibility.

Mapping version: connected-tasks-2026-10-06-v4+mcp-records-b256b58cfb844590. Task and mapping evidence remain separate from implementation evidence.

Sources1
Added by handdiscovered herechecked

Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.

Compatibility and provenance
runtimesjava
discovered viaAdded by hand
first seen in the atlas
ecosystem and domaincap, protocols-and-apis
Flavors1
Java
“MCP adapter for CDS Services Java” — com.sap.cds:cds-adapter-mcp — Maven POMchecked
History in the atlas10
  1. CDS application-service contract selected with @mcp; Read queries and unbound actions/functions; changes require application-defined unbound actions; Describe output and generic/custom MCP instructions; Java doc comments require configuration in the application and MTX sidecar; Generated query and call tools invoke the exposed CAP service; no direct CRUD tools; @mcp opts in a whole service; dedicated service projections/actions narrow its exposed contract
  2. Exposes an @mcp-annotated CAP Java application service through generated describe, query and unbound-action/function tools. Data changes require application-defined unbound actions. The adapter must not be used as a gateway or proxy for SAP Application APIs, including when the application wraps those APIs.
  3. CAP service contract
  4. Model descriptions via tools; Server instructions
  5. CAP service calls
  6. Service selection
  7. SAP prohibits gateway/proxy use for SAP Application APIs; the Atlas separately excludes CAP wrappers around those APIs from its assessed scope. Data changes require application-defined unbound actions, and the adapter supplies no rate limiting, agent-action audit logging, approval workflows or policy enforcement.
  8. Exposes an @mcp-annotated CAP Java application service through generated describe, query and unbound-action/function tools. The query and call tools invoke the exposed service without direct CRUD tools; data changes require application-defined unbound actions. The describe tool returns model descriptions, and the adapter sends generic and custom server instructions to clients. Whole-service opt-in with @mcp can be narrowed through a dedicated service with selected projections and actions. Java doc comments require configuration in the application and MTX sidecar.
  9. Turns an @mcp-annotated Application Service into an MCP server for CAP Java, generating the describe, query and call tools from the service's entities, actions and functions.
  10. First seen.
For your agent
Ref
artifact:cap-java-cds-adapter-mcp
JSON
/artifacts/cap-java-cds-adapter-mcp.json
MCP
Connecting an agent