Serve your application over MCP
Exposing selected application data and business operations to an AI agent through the Model Context Protocol, alongside protocols such as ODataODataExposing data and operations through OData, including the service model, metadata and protocol versions clients require. Version differences affect which clients can consume a service and which query features they can use.SAP and community, narrow by design and GraphQLGraphQLServing the same model over GraphQL instead of OData — one endpoint, the client naming the fields it wants, for consumers who expect that shape rather than an OData one.SAP only. A CAP application can integrate remote services through service integrationService integrationUsing a service that runs somewhere else as if it were one of your own: its API imported into the model, a proxy that turns a local query into the remote protocol, and a mock that stands in for it on a laptop. Distinct from destinations, which is how the address and the credentials are found, and from replication, which is holding the data locally.SAP and community, narrow by design and expose its own service contract over MCP, connecting this concern with Agent access to your systemsAgent access to your systemsGiving an AI agent access to the business data, configuration or operations of systems you run through an MCP server. Serving your application over MCP exposes your own service contract; system access reaches the systems behind it, and one implementation may do both. Development assistance belongs to agent access to your code.SAP and community, narrow by design; the chosen MCP implementation determines which uses are supported. Development assistance belongs to Agent access to your codeAgent access to your codeLetting a coding agent read the project or the system you actually have, reach its model, its objects and its checks, and act on it. In file-based environments that works out of the box; complex systems need dedicated access capabilities. Whatever the environment, the agent also needs project- and framework-specific context, so it understands the thing in front of it rather than guessing from what it remembers of its training data. The transport is incidental: an MCP server, a language server or a CLI answer the same question, and what differs between them is how much of the real thing the agent can see. Distinct from MCP servers, which is a protocol adapter on your own running service, and from agent guidance, which is knowledge handed over as files rather than read from the thing itself.SAP and community, unassessed.
Showing artifacts, examples and content with confirmed Java applicability. View All CAP
Overview
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.
A Java coverage assessment has not been written. View all flavors
No community artifact is confirmed here for Java.
A Java coverage assessment has not been written. View all flavors
Policy and licence
PolicySAP API Policy 4.2026a§ 1.1, 1.2, 2.2.2AlwaysAn 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 →Sources
LicenceSAP Developer License Agreement 3.2 CAP§ 1, 3AlwaysA 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 →Sources
Artifacts
Tasks
Access an external system through an application MCP service
An AI agent queries external system data or invokes selected external operations through an application-owned service contract exposed over MCP. The application integrates the target system and selects the data and operations exposed to an agent. This connects Agent access to your systems, Service integration and Serve your application over MCP; direct agent access to an external endpoint without the application layer is a separate design. Cross-system atomic transactions and development-assistance tools are outside this outcome.
com.sap.cds:cds-adapter-mcpcom.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.
com.sap.cds:cds-adapter-mcpcom.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.
Change application records from an agent
Create or update application records through an MCP client. Active-record changes through business actions or entity write tools; draft lifecycle is assessed separately.
com.sap.cds:cds-adapter-mcpcom.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.
Expose an application service to an AI agent
Let an MCP client discover and query application data and invoke selected business operations. Application-service exposure to MCP clients. Development-assistance tools and SAP application API gateway scenarios are outside this task.
com.sap.cds:cds-adapter-mcpcom.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.
Invoke a business operation from an agent
Invoke a selected application business operation through an MCP tool. Calling application operations; generating business logic or orchestrating a complete multi-system process is outside this task.
com.sap.cds:cds-adapter-mcpcom.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.
Query application data from an agent
Retrieve selected application records through MCP without changing those records. Querying application data; exposing other write tools and granting write permissions are separate requirements.
com.sap.cds:cds-adapter-mcpcom.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.
Content
Details
Connected knowledge — wider context
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
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
- 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
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
- 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.
Coverage
Designs that place it
Comparison properties
These are the questions used to compare what the artifacts do. Values come from their documentation and may apply to a particular ecosystem or runtime. Each recorded value in the comparison opens its statement and sources.
For your agent
- Ref
capability:mcp-servers- JSON
- /capabilities/mcp-servers.json
- MCP
- Connecting an agent