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-feature-remote-odata

A CAP Java feature for consuming remote OData V2 and V4 services as Remote Services, translating CQN queries into OData requests against a destination or a service binding.

Adds Remote Services for consuming OData V2 and V4 APIs, one of the optional application features that build on the CAP Java runtime. A Remote Service is configured in application.yaml against a CDS service definition from the model and either a destination or a service binding; the feature translates CQN queries issued against it into OData requests. It depends on com.sap.cds:cds-integration-cloud-sdk, which resolves that destination or binding through the SAP Cloud SDK. Combining data from a Remote Service with data from the database is left to custom code.

Homepage
Docs

Facts

LicenceSAP DEVELOPER LICENSE AGREEMENT for CAP

Where it sits

Lives in
CAP
Provides
DestinationsCAPDestinationscapabilityReaching a system that is not yours — an S/4HANA tenant, an on-premise service, a third-party API — without the address, the credentials or the tunnel being written into the application. The destination is the indirection, and the reason an endpoint can move without a redeploy.Service integrationCAPService integrationcapabilityUsing 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](capability:destinations), which is how the address and the credentials are found, and from [replication](capability:replication), which is holding the data locally.
Flavors
Java
Requires
com.sap.cds:cds-integration-cloud-sdkcom.sap.cds:cds-integration-cloud-sdkartifactNamed as a dependency in its documentation.
Optional
SAP Destination serviceSAP Destination serviceartifactThe remote service is configured with a destination rather than a service binding.destination source

Before choosing this

Conditions

LicenceSAP Developer License Agreement 3.2 CAP§ 1from DestinationsA destination used by a covered CAP application sends SAP product data to a non-SAP product rather than only addressing a remote endpoint.
  • § 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.

A destination is configuration, not the deciding boundary. The licence becomes material when the resulting data flow is extraction into a non-SAP product, so the target and purpose need review.

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

Tasks this contributes to1Beta

Serve your application over MCP1
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-feature-remote-odata consumes configured OData V2 or V4 APIs through CAP Java Remote Services; application handlers must call them explicitly.

Conditions

Model and configure the remote service, supported protocol, connectivity and backend credentials.; Implement the application handlers that call the remote service; limit the exposed contract and allowed operations.; Add com.sap.cds:cds-feature-remote-odata for an OData V2 or V4 target and configure its CDS definition plus destination or service binding.; Explicitly invoke Remote Services from application handlers; combine local database and remote data through custom code.

Remaining work

Implement the application service contract and remote-service handlers, restrict operations, configure backend credentials and tenant mapping, and test the selected target. No runtime integration was executed by the Atlas.

All options on the Serve your application over MCP page →
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-feature-remote-odata consumes configured OData V2 or V4 APIs through CAP Java Remote Services; application handlers must call them explicitly.

Conditions

Model and configure the remote service, supported protocol, connectivity and backend credentials.; Implement the application handlers that call the remote service; limit the exposed contract and allowed operations.; Confirm the target API and intended agent use against its applicable published API documentation and policy; remote-service consumption alone establishes no MCP exposure permission.; Add com.sap.cds:cds-feature-remote-odata for an OData V2 or V4 target and configure its CDS definition plus destination or service binding.; Explicitly invoke Remote Services from application handlers; combine local database and remote data through custom code.

Remaining work

Implement the application service contract and remote-service handlers, restrict operations, configure backend credentials and tenant mapping, and test the selected target. No runtime integration was executed by the Atlas.

All options on the Serve your application over MCP page →

Connections4

Download
com.sap.cds:cds-feature-remote-odata connectionscom.sap.cds:cds-feature-remote-odataPROVIDES→ provides2provides stated Consuming remote OData V2/V4 services using SAP Cloud SDK, translating CQN queries against a configured Remote Service into OData V2 or V4 requests over the resolved destination or service binding. com.sap.cds:cds-feature-remote-odata — POM (5.1.1): https://repo1.maven.org/maven2/com/sap/cds/cds-feature-remote-odata/5.1.1/cds-feature-remote-odata-5.1.1.pom CAP documentation — Java: Remote Services: https://cap.cloud.sap/docs/java/cqn-services/remote-servicesDestinationsprovides stated 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. Remote Services (CAP Java) — capire: https://cap.cloud.sap/docs/java/cqn-services/remote-services com.sap.cds:cds-feature-remote-odata — POM (5.1.1): https://repo1.maven.org/maven2/com/sap/cds/cds-feature-remote-odata/5.1.1/cds-feature-remote-odata-5.1.1.pomService integrationNEEDS→ needs1needs stated CAP documentation — Java: Remote Services: https://cap.cloud.sap/docs/java/cqn-services/remote-servicescom.sap.cds:cds-integration-cloud-sdk→ optionally needs1optionally needs stated If: The remote service is configured with a destination rather than a service binding. CAP documentation — Java: Remote Services: https://cap.cloud.sap/docs/java/cqn-services/remote-services#destination-based-scenariosSAP Destination serviceif

Where it sits in your app

Download
Your CAP applicationYour SAP BTP subaccountdocumentedrequiresdocumentedmay needif The remote service isconfigured with a destinationrather than a service bindingcom.sap.cds:cds-feature-remote-odata, modulecom.sap.cds:cds-feat…com.sap.cds:cds-integration-cloud-sdk, modulecom.sap.cds:cds-inte…SAP Destination service, service instanceSAP Destinationservice
SAPnot SAP's, or the project's owndocumented onlyunder a condition

Others providing16

Destinations
  1. SAP Destination serviceNamed, credentialed addresses of other systems resolved at runtimefrom BTP/BAIP
  2. SAP Private Link ServicePrivate network link between a BTP service and a partner cloudfrom BTP/BAIP
  3. com.sap.cds:cds-integration-cloud-sdkSAP Cloud SDK integration for remote REST services in CAP Javafrom CAP
  4. capire/s4Prebuilt SAP S/4HANA integration package for CAP projectsfrom CAP
  5. cdseDestination resolution and axios calls from CAP configurationfrom CAP
  6. @sap/cdsCAP Node.js runtimefrom CAP
  7. @sap-cloud-sdk/connectivityDestination lookup and connectivity proxy for the Cloud SDKfrom CAP
  8. @sap-cloud-sdk/http-clientHTTP client carrying a destination's credentialsfrom CAP
  9. @sap-cloud-sdk/odata-commonShared machinery under the Cloud SDK's OData and OpenAPI clientsfrom CAP
  10. @sap-cloud-sdk/openapiGenerated OpenAPI clients for the Cloud SDKfrom CAP
  11. @sap-cloud-sdk/resilienceTimeouts, retries and circuit breaking around remote callsfrom CAP
  12. @sap-cloud-sdk/utilGeneral utilities shared across the Cloud SDK packagesfrom CAP
  13. btp-cloud-connector-setup-automationYeoman generator for Cloud Connector mappings and BTP destinationsfrom BTP/BAIP
  14. @sapmentors/cds-scp-apiNode module for CAP calling external APIs through a destinationfrom CAP
Service integration
  1. capire/s4Prebuilt SAP S/4HANA integration package for CAP projectsfrom CAP
  2. cds-data-federationData federation for CAP via delegation, caching and replicationfrom CAP
  3. @sap/cds-dkCommand line client and development toolkit for CAPfrom CAP
  4. @sap/cdsCAP Node.js runtimefrom 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, integration-and-messaging
Flavors1
Java
“Consuming remote OData V2/V4 services using SAP Cloud SDK” — com.sap.cds:cds-feature-remote-odata — POM (5.1.1)checked
History in the atlas2
  1. Consuming remote OData V2/V4 services using SAP Cloud SDK, translating CQN queries against a configured Remote Service into OData V2 or V4 requests over the resolved destination or service binding.
  2. First seen.
For your agent
Ref
artifact:cap-java-cds-feature-remote-odata
JSON
/artifacts/cap-java-cds-feature-remote-odata.json
MCP
Connecting an agent