Exposing selected application data and business operations to an AI agent through the Model Context Protocol. An application may also 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, connecting its exposed contract 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. 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.
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.
@cap-js/mcp A CAP plugin that serves an @mcp-annotated service over MCP with three generated tools, describe, query and call_action, and writes its endpoint into the local agent's configuration in development.
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.
Not covered: Generated tools are not stable APIs and may change; data changes require unbound actions, and out-of-the-box XSUAA PKCE authorisation is not fully implemented. The adapter supplies no automatic rate limiting, agent-action audit logging, approval workflows or policy enforcement for tool governanceTool governanceControlling what an agent may call, with which authorisations, and leaving an audit trail of what it did. The authorisation question that MCP exposure raises but does not answer.SAP and community, unassessed, performs no prompt-injection input/output validation, and must not be used as a gateway or proxy for SAP Application APIs, including when a CAP application wraps those APIs.
Community implementations add model-derived entity resources and prompt templates, optional entity write wrappers, draft lifecycle operations and interactive UI resources. Other implementations expose application-specific blockchain operations or natural-language queries against CDS database entities; these capabilities vary by provider.
On BTP, serving an application over MCP can be configured as an MCP server artifact in API ManagementAPI ManagementAPI proxies in front of backend services, with security and traffic management policies attached to them, and Developer Hub where consumers subscribe.sap official, btp, deployed on Integration Cell within SAP Integration SuiteSAP Integration SuiteSAP's integration service on BTP: Cloud Integration for orchestration, API Management in front of it, and an MCP gateway that serves a managed API to agents.sap official, btp. The documented source paths start from an API artifact, a classic API proxy, an HTTP endpoint with OpenAPI or an RFC backend.
API ManagementAPI ManagementAPI proxies in front of backend services, with security and traffic management policies attached to them, and Developer Hub where consumers subscribe.sap official, btp creates MCP server artifacts from API artifacts, API proxies, HTTP/OpenAPI endpoints or RFC backends and runs them through the Integration Suite MCP gateway. Servers can expose tools, URI-addressed resources and parameterised prompts.
Not covered: Availability depends on the Integration Suite service plan, with API ManagementAPI ManagementAPI proxies in front of backend services, with security and traffic management policies attached to them, and Developer Hub where consumers subscribe.sap official, btp and Integration Cell activation required for the assessed creation paths. The HTTP/OpenAPI path accepts OpenAPI 3.0.0–3.0.3. The API-artifact path accepts only OAuth-authenticated source APIs; MCP client access requires OAuth and mandatory Authentication and Authorization policies.
The API-artifact and HTTP creation guides state a 30-tool limit; the live HTTP configuration page states 50. The applicable limit for a deployment needs confirmation.
btp-cf-mcpbtp-cf-mcpAn MCP server over an SAP BTP account and its Cloud Foundry runtime that acts as the person who logged in, so their own global-account and space roles decide what an agent can see.independent, btp is a server that exposes an SAP BTP account and its Cloud Foundry runtime to an agent as read and write tools under the caller's own identity.
Here the question is whether the system can be the server rather than the thing being read. abap-ai/mcpabap-ai/mcpAn MCP server SDK written in ABAP to run natively on the ABAP stack, so an ABAP system can expose its own prompts, resources and tools to an agent from inside itself.independent, abap implements the protocol in ABAP itself — prompts, resources, tools, long-running tasks and DDIC-derived schemas — installed with abapGitabapGitmaintains 1 entrycommunity org(artifact:abapgit-abapgit) and running inside the system, so what an agent sees is what you chose to expose rather than whatever ADT happens to reach.
No core answer is documented.
Not covered: At the server half. The SDK's author states there is no realistic way to support the SSE streaming a client needs, so an ABAP system can answer an agent and cannot notify one.
The servers run inside the ABAP system: an SDK for writing them in ABAP (abap-ai/mcpabap-ai/mcpAn MCP server SDK written in ABAP to run natively on the ABAP stack, so an ABAP system can expose its own prompts, resources and tools to an agent from inside itself.independent, abap and its stateless rewrite abap-ai/mcp2abap-ai/mcp2A stateless rewrite of the ABAP MCP server SDK: one ABAP server contract answering both the 2026-07-28 protocol draft and the legacy 2025 versions, with no sessions and no SSE.independent, abap), an add-on that turns tables and CDS views into tools (Skybuffer AI MCP serverSkybuffer AI MCP serverAn ABAP add-on that serves SAP business data, transactions and development context as MCP tools from an ICF node inside SAP ECC and S/4HANA, each call running as the signed-in user under PFCG authorization checks.independent, abap) and an endpoint that drives opted-in abap2UI5 apps (abap-agent-runtimeabap-agent-runtimeAn ABAP-native MCP endpoint inside the SAP system: an agent reads the screen of an opted-in abap2UI5 app as structured data, fills its fields and fires its events as the logged-on SAP user.community org, abap). SAP's own ABAP MCP work reaches into a system from outside and lives in 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.
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 →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 →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.
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.
Remaining work: Implement and test the custom service handlers and remote calls, and configure client access and productive controls.
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.
Conditions: Current upstream prerequisites are Node.js 18+, CAP 10+ and Express 5+. Annotate the application entities/actions and configure inherited CAP authentication; the application owns outbound credentials and remote handlers. Entity write wrappers require deliberate configuration and still depend on application-side authorization.
Remaining work: Implement and test the application and remote handlers, enforce client/backend permissions and confirm target-specific use.
Conditions: Implement and configure custom application tools that call the selected CAP application service; the shipped product CRUD example uses in-memory data. Configure MCP access and application/backend authorization independently of the demo. Implement remote calls and their restrictions in the application; the custom-tool example does not establish a specific external-system bridge.
Remaining work: Implement and test the application and remote handlers, enforce client/backend permissions and confirm target-specific use.
Conditions: Install from source; the README requires Node.js 18+, @sap/cds 9+ and Express 4+. Annotate the application contract and configure authentication, deployment and session storage. @mcp.omit filters output only; omitted fields remain queryable in the underlying service and can still be supplied to writes. Implement outbound handlers and backend authorization; the server does not configure remote APIs.
Remaining work: Implement and test the application and remote handlers, enforce client/backend permissions and confirm target-specific use.
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.
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.
Conditions: Current upstream prerequisites are Node.js 18+, CAP 10+ and Express 5+. Annotate the application entities/actions and configure inherited CAP authentication; the application owns outbound credentials and remote handlers. Entity write wrappers require deliberate configuration and still depend on application-side authorization. No SAP Application API agent-access endorsement or deployment-specific permission was established by these sources.
Remaining work: Implement and test the application and remote handlers, enforce client/backend permissions and confirm target-specific use.
Conditions: Implement and configure custom application tools that call the selected CAP application service; the shipped product CRUD example uses in-memory data. Configure MCP access and application/backend authorization independently of the demo. Implement remote calls and their restrictions in the application; the custom-tool example does not establish a specific external-system bridge. No SAP Application API agent-access endorsement or deployment-specific permission was established by these sources.
Remaining work: Implement and test the application and remote handlers, enforce client/backend permissions and confirm target-specific use.
Conditions: Install from source; the README requires Node.js 18+, @sap/cds 9+ and Express 4+. Annotate the application contract and configure authentication, deployment and session storage. @mcp.omit filters output only; omitted fields remain queryable in the underlying service and can still be supplied to writes. Implement outbound handlers and backend authorization; the server does not configure remote APIs. No SAP Application API agent-access endorsement or deployment-specific permission was established by these sources.
Remaining work: Implement and test the application and remote handlers, enforce client/backend permissions and confirm target-specific use.
Create or update application records through an MCP client. Active-record changes through business actions or entity write tools; draft lifecycle is assessed separately.
Conditions: Install @cap-js/mcp into the CAP Node.js application. Annotate the custom application service with @mcp. Use a dedicated MCP service to restrict 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. 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: Own action logic, validation and authorization; this does not establish draft lifecycle support.
Conditions: Activate API Management and the Integration Cell runtime; assign PI_Integration_Developer and create an integration package. The selected Integration Suite service plan must include this feature. For the assessed HTTP source path, supply OpenAPI 3.0.0–3.0.3 and a reachable custom application endpoint or supported destination.
Remaining work: Select the source API operations, configure the destination, tools/resources/prompts and security policies, deploy on Integration Cell and arrange client access.
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.
Conditions: Node.js 18+, SAP CAP 10+ and Express 5+, as stated in the README. Install @gavdi/cap-mcp, configure cds.mcp and annotate the entities or operations to expose. Enable the required create/update modes through entity wrapper configuration.
Remaining work: Validate and authorize changes in the application; output omission does not block write inputs.
Conditions: Install @neoimpulse/cap-js-mcp in a CAP Node.js application and configure its component module paths. Choose the configurable authentication setting; when enabled, configure API-key access as described in the README. Implement custom tool modules that invoke the real application service and its authorised operations; the stock product CRUD tools do not persist application records.
Remaining work: Implement actual application service writes and permission checks in custom modules; the stock demo is not a production record-write implementation.
Conditions: Install cap-mcp-plugin from its GitHub source into a CAP Node.js application; no npm package is declared. Configure the MCP endpoint and the model annotations. Enable the required wrapper modes; draft roots require the separately documented draft lifecycle unless draft bypass is configured. The README requires Node.js 18+, @sap/cds 9+ and Express 4+.
Remaining work: Own application validation, permissions and deployment; @mcp.omit filters output only.
Remaining work: Use a separately assessed write-capable path for this outcome.
Create or edit a draft record and activate or discard the pending change through MCP. Draft-enabled application records; active-record writes and UI rendering are separate outcomes.
Conditions: Install cap-mcp-plugin from its GitHub source into a CAP Node.js application; no npm package is declared. Configure the MCP endpoint and the model annotations. Use draft-enabled roots and a consistent authenticated principal across draft calls.
Remaining work: Implement application validation and authorization and account for draft locking and activation failures.
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.
Conditions: Install @cap-js/mcp into the CAP Node.js 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. 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.
Conditions: Activate API Management and the Integration Cell runtime; assign PI_Integration_Developer and create an integration package. The selected Integration Suite service plan must include this feature. For the assessed HTTP source path, supply OpenAPI 3.0.0–3.0.3 and a reachable custom application endpoint or supported destination. MCP client access uses OAuth. Authentication and Authorization policies are mandatory and cannot be deleted; Authentication must be first in the request flow.
Remaining work: Select the source API operations, configure the destination, tools/resources/prompts and security policies, deploy on Integration Cell and arrange client access.
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.
Conditions: Node.js 18+, SAP CAP 10+ and Express 5+, as stated in the README. Install @gavdi/cap-mcp, configure cds.mcp and annotate the entities or operations to expose.
Remaining work: Choose the service surface and operations, configure client access and deployment governance.
Conditions: Install cap-mcp-plugin from its GitHub source into a CAP Node.js application; no npm package is declared. Configure the MCP endpoint and the model annotations. The README requires Node.js 18+, @sap/cds 9+ and Express 4+.
Remaining work: Choose annotations, configure authorization and session handling and validate the selected application operations.
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.
Conditions: Install @cap-js/mcp into the CAP Node.js 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. 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.
Conditions: Activate API Management and the Integration Cell runtime; assign PI_Integration_Developer and create an integration package. The selected Integration Suite service plan must include this feature. For the assessed HTTP source path, supply OpenAPI 3.0.0–3.0.3 and a reachable custom application endpoint or supported destination.
Remaining work: Select the source API operations, configure the destination, tools/resources/prompts and security policies, deploy on Integration Cell and arrange client access.
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.
Conditions: Node.js 18+, SAP CAP 10+ and Express 5+, as stated in the README. Install @gavdi/cap-mcp, configure cds.mcp and annotate the entities or operations to expose.
Remaining work: Implement business logic and choose the operation parameters and caller permissions.
Conditions: Install @neoimpulse/cap-js-mcp in a CAP Node.js application and configure its component module paths. Choose the configurable authentication setting; when enabled, configure API-key access as described in the README. Implement custom tool modules that invoke the real application service and its authorised operations; the stock product CRUD tools do not persist application records.
Remaining work: Implement the business operation and its authorization against real application services; built-in product tools are demonstrations.
Conditions: Install cap-mcp-plugin from its GitHub source into a CAP Node.js application; no npm package is declared. Configure the MCP endpoint and the model annotations. The README requires Node.js 18+, @sap/cds 9+ and Express 4+.
Remaining work: Implement and authorize the operation; elicitation is limited to direct tools, not entity wrappers.
Let an MCP client retrieve application data or schema context through resource URIs. The MCP resources primitive; a tool returning text or a document merely mentioning MCP is not a resource implementation.
Conditions: Activate API Management and the Integration Cell runtime; assign PI_Integration_Developer and create an integration package. The selected Integration Suite service plan must include this feature. For the assessed HTTP source path, supply OpenAPI 3.0.0–3.0.3 and a reachable custom application endpoint or supported destination. Only GET API resources can be listed as MCP resources; the HTTP configuration guide states a limit of 15 resources per server. MCP client access uses OAuth. Authentication and Authorization policies are mandatory and cannot be deleted; Authentication is first in the request flow.
Remaining work: Choose eligible GET resources, configure their URI templates and schemas, secure access and deploy the MCP server on Integration Cell.
Conditions: Node.js 18+, SAP CAP 10+ and Express 5+, as stated in the README. Install @gavdi/cap-mcp, configure cds.mcp and annotate the entities or operations to expose. Dynamic resource queries require all declared query parameters because of the documented SDK limitation.
Remaining work: Choose resource entities and supported query parameters and enforce caller permissions.
Conditions: Install @neoimpulse/cap-js-mcp in a CAP Node.js application and configure its component module paths. Choose the configurable authentication setting; when enabled, configure API-key access as described in the README.
Remaining work: Implement resource handlers and access controls for the desired application context.
Conditions: Install cap-mcp-plugin from its GitHub source into a CAP Node.js application; no npm package is declared. Configure the MCP endpoint and the model annotations. The README requires Node.js 18+, @sap/cds 9+ and Express 4+. Dynamic resource queries must supply all declared query parameters because of the documented SDK limitation.
Remaining work: Choose the exposed data, fields and permissions; interactive UI resources are a separate task.
Let an MCP client discover and retrieve reusable, parameterized interaction templates. Server-published MCP prompts; arbitrary application instructions and complete automated workflows are separate concerns.
Conditions: Activate API Management and the Integration Cell runtime; assign PI_Integration_Developer and create an integration package. The selected Integration Suite service plan must include this feature. For the assessed HTTP source path, supply OpenAPI 3.0.0–3.0.3 and a reachable custom application endpoint or supported destination.
Remaining work: Select the source API operations, configure the destination, tools/resources/prompts and security policies, deploy on Integration Cell and arrange client access.
Conditions: Node.js 18+, SAP CAP 10+ and Express 5+, as stated in the README. Install @gavdi/cap-mcp, configure cds.mcp and declare prompt templates on the service with @mcp.prompts.
Remaining work: Author templates and arguments and check client support; a prompt does not implement business logic.
Conditions: Install @neoimpulse/cap-js-mcp in a CAP Node.js application and configure its component module paths. Choose the configurable authentication setting; when enabled, configure API-key access as described in the README.
Remaining work: Implement template modules and arguments and verify the selected client can retrieve them.
Conditions: Install cap-mcp-plugin from its GitHub source into a CAP Node.js application; no npm package is declared. Configure the MCP endpoint and the model annotations. The README requires Node.js 18+, @sap/cds 9+ and Express 4+.
Remaining work: Author template inputs and content and arrange client access.
Retrieve selected application records through MCP without changing those records. Querying application data; exposing other write tools and granting write permissions are separate requirements.
Conditions: Install @cap-js/mcp into the CAP Node.js 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.
Remaining work: Shape the service projection and caller permissions; configure the client and deployment authorization.
Conditions: Activate API Management and the Integration Cell runtime; assign PI_Integration_Developer and create an integration package. The selected Integration Suite service plan must include this feature. For the assessed HTTP source path, supply OpenAPI 3.0.0–3.0.3 and a reachable custom application endpoint or supported destination.
Remaining work: Select the source API operations, configure the destination, tools/resources/prompts and security policies, deploy on Integration Cell and arrange client access.
Conditions: A CAP project with @sap/cds >= 7 and a configured CDS database, plus an LLM provider API key. For production, configure the dedicated read-only database user described in the README.
Remaining work: Check database access against application authorization requirements; service-layer handlers and permissions are not established by this database route.
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.
Conditions: Node.js 18+, SAP CAP 10+ and Express 5+, as stated in the README. Install @gavdi/cap-mcp, configure cds.mcp and annotate the entities or operations to expose.
Remaining work: Select entities and query modes; restrict caller permissions separately from output-field omission.
Conditions: Install @neoimpulse/cap-js-mcp in a CAP Node.js application and configure its component module paths. Configure the API-key authentication described in the published README.
Remaining work: Select the entity/service and implement any additional application tools; its product CRUD tools use demo in-memory data.
Conditions: Install cap-mcp-plugin from its GitHub source into a CAP Node.js application; no npm package is declared. Configure the MCP endpoint and the model annotations.
Remaining work: Select the model surface and read modes, configure authorization and choose session handling.
Render an interactive application list or detail view inside a supporting MCP client. MCP UI resources; a normal browser application or generic text tool result does not establish this outcome.
Conditions: Install cap-mcp-plugin from its GitHub source into a CAP Node.js application; no npm package is declared. Configure the MCP endpoint and the model annotations. Use an MCP host that supports the MCP Apps extension and annotate the entity with @mcp.wrap.tools and Fiori UI metadata.
Remaining work: Configure host rendering/CSP and permitted writes; read-only UI settings do not disable the underlying write tools.
Source connections explain where this sits. Implementation claims remain in their exact task assessment.
Editorially accepted assessment · assessed . No Atlas runtime testing.
Evidence changed · needs review · evidence captured 2026-10-12, 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.
Related knowledge
@cap-js/mcp exposes an annotated custom service for model discovery, querying and invocation of unbound actions and functions.
Why included: Dated assessment history; supporting evidence needs review.
Evidence status not tracked
Evidence observations do not cover this accepted claim; it is retained as dated history.
@gavdi/cap-mcp exposes annotated entities as resources and functions/actions as tools.
Why included: Dated assessment history; supporting evidence needs review.
Evidence status not tracked
Evidence observations do not cover this accepted claim; it is retained as dated history.
cap-mcp-bridge queries a custom application OData V4 endpoint and invokes its exposed operations.
Why included: Dated assessment history; supporting evidence needs review.
Evidence status not tracked
Evidence observations do not cover this accepted claim; it is retained as dated history.
A fifteen-minute walkthrough of turning a plain CAP service into an MCP server: annotate the service with @mcp, install @cap-js/mcp, and it is served alongside OData at /mcp/<path>. The part worth reading it for is what happens next — cds watch writes the endpoint into the local agent's own configuration file, so OpenCode or Claude Code can call the service without anyone editing JSON by hand. It is built on the tiny-sample facet, so there is nothing to prepare, and it shows the protocol traffic rather than only the result. Written while the adapter was in beta, and it says so.
Why included: CAP Node.js setup, @mcp service exposure, local client discovery and querying through the official adapter.
What the MCP adapter actually does when a CAP server boots, watched rather than described — the companion to the tutorial that switches it on.
Why included: CAP Node.js startup, tool discovery and query flow; the tutorial sample contains no actions or functions.
Documents @cap-js/mcp and com.sap.cds:cds-adapter-mcp, service annotations, generated describe/query/call tools and local client setup. The guide records Java doc-comment configuration, unbound-action-based data changes, incomplete XSUAA PKCE support and the adapter’s governance boundaries.
Why included: CAP Node.js and Java adapter installation, service exposure, model context, tools and documented limitations.
Source subject or learning resource; applicability is established separately by the scoped assessment.
Why included: Native relationship in the retained Developers snapshot; no runtime claim is inferred. · SAP Developers
Source subject or learning resource; applicability is established separately by the scoped assessment.
Why included: Native relationship in the retained Developers snapshot; no runtime claim is inferred. · SAP Developers
Source subject or learning resource; applicability is established separately by the scoped assessment.
Why included: Native relationship in the retained Developers snapshot; no runtime claim is inferred. · SAP Developers
Source subject or learning resource; applicability is established separately by the scoped assessment.
Why included: Native relationship in the retained Developers snapshot; no runtime claim is inferred. · SAP Developers
Source subject or learning resource; applicability is established separately by the scoped assessment.
Why included: Native relationship in the retained Developers snapshot; no runtime claim is inferred. · SAP Developers
Source subject or learning resource; applicability is established separately by the scoped assessment.
Why included: Native relationship in the retained Developers snapshot; no runtime claim is inferred. · SAP Developers
Source subject or learning resource; applicability is established separately by the scoped assessment.
Why included: Native relationship in the retained Developers snapshot; no runtime claim is inferred. · SAP Developers
Source subject or learning resource; applicability is established separately by the scoped assessment.
Why included: Native relationship in the retained Developers snapshot; no runtime claim is inferred. · SAP Developers
Source subject or learning resource; applicability is established separately by the scoped assessment.
Why included: Native relationship in the retained Developers snapshot; no runtime claim is inferred. · SAP Developers
Source subject or learning resource; applicability is established separately by the scoped assessment.
Why included: Native relationship in the retained Developers snapshot; no runtime claim is inferred. · SAP Developers
@cap-js/mcp → provides → Serve your application over MCP
Exposes an @mcp-annotated CAP Node.js 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.
Basis: atlas-record
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-12The CAP MCP adapter is intended only for exposing custom CAP application services.
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-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.
Model Context Protocol Adapter | capire · checked 2026-10-12Within your project root run this to add the @cap-js/mcp plugin for Node.js projects
@gavdi/cap-mcp → provides → Serve your application over MCP
Generates MCP resources and operation tools from annotated CAP Node.js services, with configured entity wrappers for query/get and optional create/update. The README requires Node.js 18+, CAP 10+ and Express 5+; resource reads and direct tools use service transactions in the pinned implementation. Output omission does not establish a field-access restriction. Annotations and wrapper modes select the exposed entities and operations. Entity resources, reusable prompt templates and @mcp.hint schema descriptions supply context; enable_model_description controls the model-description tool, and instructions configures server instructions. @mcp.omit filters output only: omitted fields remain queryable and can be supplied as write inputs.
Basis: atlas-record
CAP MCP Plugin — gavdilabs/cap-mcp-plugin README · checked 2026-10-12- **Node.js**: Version 18 or higher
CAP MCP Plugin — gavdilabs/cap-mcp-plugin README · checked 2026-10-12- **SAP CAP**: Version 10 or higher
CAP MCP Plugin — gavdilabs/cap-mcp-plugin README · checked 2026-10-12- **Express**: Version 5 or higher
CAP MCP Plugin — gavdilabs/cap-mcp-plugin README · checked 2026-10-12Omitted fields remain queryable in the CAP service - only MCP responses are filtered
CAP MCP Plugin — gavdilabs/cap-mcp-plugin README · checked 2026-10-12Annotate your CAP services with `@mcp` annotations:
CAP MCP Plugin — gavdilabs/cap-mcp-plugin README · checked 2026-10-12Convert CAP functions and actions into executable MCP tools
CAP MCP Plugin — gavdilabs/cap-mcp-plugin README · checked 2026-10-12Expose CAP entities as tools (`query`, `get`, and optionally `create`, `update`) for LLM tool use while keeping resources intact
CAP MCP Plugin — gavdilabs/cap-mcp-plugin README · checked 2026-10-12Define reusable prompt templates for AI interactions
CAP MCP Plugin — gavdilabs/cap-mcp-plugin README · checked 2026-10-12Hints are accessible in both resource queries and tool executions
CAP MCP Plugin — gavdilabs/cap-mcp-plugin README · checked 2026-10-12Expose CAP entities as MCP resources with OData v4 query capabilities
gavdilabs/cap-mcp-plugin — resources.ts at 1f3a97e1c0733d97c0cabea53d6d31767508daed · checked 2026-10-12const response = await service.tx({ user: accessRights }).run(query);
gavdilabs/cap-mcp-plugin — tools.ts at 1f3a97e1c0733d97c0cabea53d6d31767508daed · checked 2026-10-12const response = await service.tx({ user: accessRights }).send({
CAP MCP Plugin — gavdilabs/cap-mcp-plugin README · checked 2026-10-12Scans your CAP service definitions for `@mcp` annotations
CAP MCP Plugin — gavdilabs/cap-mcp-plugin README · checked 2026-10-12When `wrap_entities_to_actions` is enabled (globally or via `@mcp.wrap.tools: true`)
CAP MCP Plugin — gavdilabs/cap-mcp-plugin README · checked 2026-10-12Omitted fields are **only excluded from outputs** - they can still be provided as inputs for create/update operations
CAP MCP Plugin — gavdilabs/cap-mcp-plugin README · checked 2026-10-12Determines whether the MCP server should include the model description tool
CAP MCP Plugin — gavdilabs/cap-mcp-plugin README · checked 2026-10-12MCP server instructions for agents
cap-mcp-plugin → provides → Serve your application over MCP
Generates MCP entity resources and bound/unbound operation tools for CAP Node.js, with configured CRUD wrappers, a draft lifecycle and optional Fiori-derived MCP Apps. The README requires Node.js 18+, CAP 9+ and Express 4+. Resource/tool annotations and wrapper modes select the exposed surface; resource reads and direct operation tools call CAP service transactions in the pinned implementation. Entity resources, prompt templates and @mcp.hint schemas supply context, instructions configures server instructions, and MCP Apps require @mcp.wrap.tools with Fiori annotations. @mcp.omit filters output only, and disabling app write buttons leaves tools callable.
Basis: atlas-record
cap-mcp-plugin — sleibach/cap-mcp-plugin README · checked 2026-10-12- Node.js 18+
cap-mcp-plugin — sleibach/cap-mcp-plugin README · checked 2026-10-12- `@sap/cds` 9+
cap-mcp-plugin — sleibach/cap-mcp-plugin README · checked 2026-10-12- `express` 4+
cap-mcp-plugin — sleibach/cap-mcp-plugin README · checked 2026-10-12`@mcp.omit` filters MCP output only.
cap-mcp-plugin — sleibach/cap-mcp-plugin README · checked 2026-10-12no Create/Edit/Delete buttons (the write tools themselves are unaffected)
cap-mcp-plugin — sleibach/cap-mcp-plugin README · checked 2026-10-12Annotated entities become MCP resources, functions and actions become tools, and services can expose reusable prompt templates.
cap-mcp-plugin — sleibach/cap-mcp-plugin README · checked 2026-10-12CDS operations annotated with `@mcp.tool: true` become MCP tools.
cap-mcp-plugin — sleibach/cap-mcp-plugin README · checked 2026-10-12Both **unbound** (service-level) and **bound** (entity-level) operations are supported
cap-mcp-plugin — sleibach/cap-mcp-plugin README · checked 2026-10-12- `delete` — remove a row by key(s).
cap-mcp-plugin — sleibach/cap-mcp-plugin README · checked 2026-10-12- `draft-activate` — publish the pending draft to the active row.
cap-mcp-plugin — sleibach/cap-mcp-plugin README · checked 2026-10-12**Short-circuits active-row `create`, `update`, and `delete`** with a `DRAFT_REQUIRED` error
cap-mcp-plugin — sleibach/cap-mcp-plugin README · checked 2026-10-12entities annotated with `@odata.draft.bypass` (or the whole service with `cds.env.fiori.bypass_draft: true`) continue to accept direct active-row `create`/`update`/`delete`
cap-mcp-plugin — sleibach/cap-mcp-plugin README · checked 2026-10-12Declare reusable prompt templates.
cap-mcp-plugin — sleibach/cap-mcp-plugin README · checked 2026-10-12Enrich schemas for AI agents via `@mcp.hint` on elements and parameters.
cap-mcp-plugin — sleibach/cap-mcp-plugin README · checked 2026-10-12When an entity has `@mcp.wrap.tools` **and** Fiori UI annotations, the plugin registers two `ui://` HTML resources
sleibach/cap-mcp-plugin — resources.js at 5359398d0662f452d31529509c67634f8eb5406d · checked 2026-10-12const response = await service.tx({ user: accessRights }).run(query);
sleibach/cap-mcp-plugin — tools.js at 5359398d0662f452d31529509c67634f8eb5406d · checked 2026-10-12service.tx({ user: accessRights }).send({
cap-mcp-plugin — sleibach/cap-mcp-plugin README · checked 2026-10-12modes: ['query', 'get', 'create', 'update']
cap-mcp-plugin — sleibach/cap-mcp-plugin README · checked 2026-10-12Omitted fields can still be supplied as inputs on create / update operations and remain queryable in the underlying CAP service.
cap-mcp-plugin — sleibach/cap-mcp-plugin README · checked 2026-10-12Server-level instructions surfaced to agents
Model Context Protocol Adapter — CAP guide → explains → Serve your application over MCP
CAP Node.js and Java adapter installation, service exposure, model context, tools and documented limitations.
Basis: atlas-record
Model Context Protocol Adapter — CAP guide → explains → @cap-js/mcp
Node.js installation, service annotations, querying and unbound action/function invocation.
Basis: atlas-record
Add MCP capabilities to a CAP service → explains → Serve your application over MCP
CAP Node.js setup, @mcp service exposure, local client discovery and querying through the official adapter.
Basis: atlas-record
Add MCP capabilities to a CAP service → explains → @cap-js/mcp
Canonical Atlas relevance assertion.
Basis: atlas-record
Examine the details of the Model Context Protocol on startup → explains → Serve your application over MCP
CAP Node.js startup, tool discovery and query flow; the tutorial sample contains no actions or functions.
Basis: atlas-record
Examine the details of the Model Context Protocol on startup → explains → @cap-js/mcp
Canonical Atlas relevance assertion.
Basis: atlas-record
Add MCP capabilities to a CAP service → teaches → CAP OData V4 Service Development
Native relationship in the retained Developers snapshot; no runtime claim is inferred.
Basis: source-graph
SAP Developers graph snapshot · checked 2026-10-05T00:55:43.720Z
Add MCP capabilities to a CAP service → teaches → JSON-RPC Protocol
Native relationship in the retained Developers snapshot; no runtime claim is inferred.
Basis: source-graph
SAP Developers graph snapshot · checked 2026-10-05T00:55:43.720Z
Add MCP capabilities to a CAP service → teaches → MCP (Model Context Protocol) Adapter for CAP
Native relationship in the retained Developers snapshot; no runtime claim is inferred.
Basis: source-graph
SAP Developers graph snapshot · checked 2026-10-05T00:55:43.720Z
Add MCP capabilities to a CAP service → teaches → Connecting with AI Coding Agents
Native relationship in the retained Developers snapshot; no runtime claim is inferred.
Basis: source-graph
SAP Developers graph snapshot · checked 2026-10-05T00:55:43.720Z
Add MCP capabilities to a CAP service → teaches → CAP Annotations
Native relationship in the retained Developers snapshot; no runtime claim is inferred.
Basis: source-graph
SAP Developers graph snapshot · checked 2026-10-05T00:55:43.720Z
Add MCP capabilities to a CAP service → teaches → CAP Local Development Loop
Native relationship in the retained Developers snapshot; no runtime claim is inferred.
Basis: source-graph
SAP Developers graph snapshot · checked 2026-10-05T00:55:43.720Z
Add MCP capabilities to a CAP service → teaches → MCP Servers
Native relationship in the retained Developers snapshot; no runtime claim is inferred.
Basis: source-graph
SAP Developers graph snapshot · checked 2026-10-05T00:55:43.720Z
Examine the details of the Model Context Protocol on startup → teaches → JSON-RPC Protocol
Native relationship in the retained Developers snapshot; no runtime claim is inferred.
Basis: source-graph
SAP Developers graph snapshot · checked 2026-10-05T00:55:43.720Z
Examine the details of the Model Context Protocol on startup → teaches → CAP for Node.js
Native relationship in the retained Developers snapshot; no runtime claim is inferred.
Basis: source-graph
SAP Developers graph snapshot · checked 2026-10-05T00:55:43.720Z
Examine the details of the Model Context Protocol on startup → teaches → MCP (Model Context Protocol) Adapter for CAP
Native relationship in the retained Developers snapshot; no runtime claim is inferred.
Basis: source-graph
SAP Developers graph snapshot · checked 2026-10-05T00:55:43.720Z
Examine the details of the Model Context Protocol on startup → teaches → MCP Inspector TUI Client
Native relationship in the retained Developers snapshot; no runtime claim is inferred.
Basis: source-graph
SAP Developers graph snapshot · checked 2026-10-05T00:55:43.720Z
Examine the details of the Model Context Protocol on startup → teaches → MCP Servers
Native relationship in the retained Developers snapshot; no runtime claim is inferred.
Basis: source-graph
SAP Developers graph snapshot · checked 2026-10-05T00:55:43.720Z
Examine the details of the Model Context Protocol on startup → teaches → MCP Tools and Autonomous Multi-Step Workflows
Native relationship in the retained Developers snapshot; no runtime claim is inferred.
Basis: source-graph
SAP Developers graph snapshot · checked 2026-10-05T00:55:43.720Z
Expose an application service to an AI agent → associatedWith → Serve your application over MCP
Primary capability recorded by the accepted task.
Basis: atlas-assessment
MCP (Model Context Protocol) Adapter for CAP → addressesPartOf → Expose an application service to an AI agent
The retained source graph says the CAP tutorial teaches this adapter subject. The tutorial exposes a CAP Node.js service through @cap-js/mcp, which addresses the official-adapter part of this assessment.
Basis: atlas-mapping
Mapping: partial · accepted · Reviewed canonical mapping · checked 2026-10-12
Evidence matches captured sources · evidence captured 2026-10-12
Add MCP capabilities to a CAP service · checked 2026-10-12the implementation of MCP capabilities is provided by the MCP adapter plugin @cap-js/mcp
Add MCP capabilities to a CAP service · checked 2026-10-12You will need a development environment for CAP Node.js.
MCP Servers → contextualizes → Serve your application over MCP
The retained source graph says the CAP tutorial teaches MCP Servers. In CAP Node.js that tutorial supplies service-exposure context for Serve your application over MCP; this does not classify every tutorial under the broad source subject.
Basis: atlas-mapping
Mapping: about · accepted · Reviewed canonical mapping · checked 2026-10-12
Evidence matches captured sources · evidence captured 2026-10-12
Add MCP capabilities to a CAP service · checked 2026-10-12the implementation of MCP capabilities is provided by the MCP adapter plugin @cap-js/mcp
Add MCP capabilities to a CAP service · checked 2026-10-12You will need a development environment for CAP Node.js.
Expose an application service to an AI agent → assesses → Expose an application service to an AI agent
One shared outcome, one scoped assessment.
Basis: atlas-assessment
@cap-js/mcp → previouslyContributedTo → Expose an application service to an AI agent
Last accepted assessment (2026-10-12): @cap-js/mcp exposes an annotated custom service for model discovery, querying and invocation of unbound actions and functions.
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.
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-12there is no automatic rate limiting, no specific audit logging of agent actions, no approval workflows for sensitive operations, and no policy enforcement layer.
Model Context Protocol Adapter | capire · checked 2026-10-12out-of-the-box support for authorization with XSUAA, with PKCE, but it is not fully implemented yet.
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-12npm add @cap-js/mcp
Model Context Protocol Adapter | capire · checked 2026-10-12For any deployment ensure you use infrastructure and practices that mitigate prompt injection risks and connect only to trusted MCP agents (e.g., Joule).
Model Context Protocol Adapter | capire · checked 2026-10-12Tools are meant to be used by LLMs and AI agents and do not constitute a stable API.
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-12Instead of annotating an existing service with @mcp and exposing all its entities and actions, simply create a dedicated service specifically for MCP.
@gavdi/cap-mcp → previouslyContributedTo → Expose an application service to an AI agent
Last accepted assessment (2026-10-12): @gavdi/cap-mcp exposes annotated entities as resources and functions/actions as tools.
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.
CAP MCP Plugin — gavdilabs/cap-mcp-plugin README · checked 2026-10-12Expose CAP entities as MCP resources with OData v4 query capabilities
CAP MCP Plugin — gavdilabs/cap-mcp-plugin README · checked 2026-10-12Convert CAP functions and actions into executable MCP tools
CAP MCP Plugin — gavdilabs/cap-mcp-plugin README · checked 2026-10-12**Node.js**: Version 18 or higher
CAP MCP Plugin — gavdilabs/cap-mcp-plugin README · checked 2026-10-12**SAP CAP**: Version 10 or higher
CAP MCP Plugin — gavdilabs/cap-mcp-plugin README · checked 2026-10-12**Express**: Version 5 or higher
cap-mcp-bridge → previouslyContributedTo → Expose an application service to an AI agent
Last accepted assessment (2026-10-12): cap-mcp-bridge queries a custom application OData V4 endpoint and invokes its exposed operations.
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.
SanoberRehman/cap-mcp-bridge — README · checked 2026-10-12| `query_entity` | The workhorse: filter, select, expand, orderBy, paging, `$count` |
SanoberRehman/cap-mcp-bridge — README · checked 2026-10-12| `invoke_action` | Call an action. **Write mode only** |
SanoberRehman/cap-mcp-bridge — README · checked 2026-10-12`cap-mcp-bridge` runs **outside** the service and consumes `$metadata` over HTTP.
SanoberRehman/cap-mcp-bridge — README · checked 2026-10-12That starts an MCP server on stdio.
cap-mcp-plugin → previouslyContributedTo → Expose an application service to an AI agent
Last accepted assessment (2026-10-12): cap-mcp-plugin derives MCP resources and tools from annotated CDS entities and operations.
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.
CAP MCP Plugin — sleibach/cap-mcp-plugin README · checked 2026-10-12Annotated entities become MCP resources, functions and actions become tools, and services can expose reusable prompt templates.
CAP MCP Plugin — sleibach/cap-mcp-plugin README · checked 2026-10-12Node.js 18+
CAP MCP Plugin — sleibach/cap-mcp-plugin README · checked 2026-10-12`@sap/cds` 9+
CAP MCP Plugin — sleibach/cap-mcp-plugin README · checked 2026-10-12`express` 4+
CAP MCP Plugin — sleibach/cap-mcp-plugin README · checked 2026-10-12There is **no npm registry package yet**. Install straight from GitHub:
CAP MCP Plugin — sleibach/cap-mcp-plugin README · checked 2026-10-12- Node.js 18+ - `@sap/cds` 9+ - `express` 4+
Expose an application service to an AI agent → reading → Model Context Protocol Adapter | capire
Curated supporting reading for this assessment.
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.
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-12there is no automatic rate limiting, no specific audit logging of agent actions, no approval workflows for sensitive operations, and no policy enforcement layer.
Model Context Protocol Adapter | capire · checked 2026-10-12out-of-the-box support for authorization with XSUAA, with PKCE, but it is not fully implemented yet.
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-12npm add @cap-js/mcp
Model Context Protocol Adapter | capire · checked 2026-10-12For any deployment ensure you use infrastructure and practices that mitigate prompt injection risks and connect only to trusted MCP agents (e.g., Joule).
Model Context Protocol Adapter | capire · checked 2026-10-12Tools are meant to be used by LLMs and AI agents and do not constitute a stable API.
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-12Instead of annotating an existing service with @mcp and exposing all its entities and actions, simply create a dedicated service specifically for MCP.
Expose an application service to an AI agent → reading → CAP MCP Plugin — gavdilabs/cap-mcp-plugin README
Curated supporting reading for this assessment.
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.
CAP MCP Plugin — gavdilabs/cap-mcp-plugin README · checked 2026-10-12Expose CAP entities as MCP resources with OData v4 query capabilities
CAP MCP Plugin — gavdilabs/cap-mcp-plugin README · checked 2026-10-12Convert CAP functions and actions into executable MCP tools
CAP MCP Plugin — gavdilabs/cap-mcp-plugin README · checked 2026-10-12**Node.js**: Version 18 or higher
CAP MCP Plugin — gavdilabs/cap-mcp-plugin README · checked 2026-10-12**SAP CAP**: Version 10 or higher
CAP MCP Plugin — gavdilabs/cap-mcp-plugin README · checked 2026-10-12**Express**: Version 5 or higher
Expose an application service to an AI agent → reading → SanoberRehman/cap-mcp-bridge — README
Curated supporting reading for this assessment.
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.
SanoberRehman/cap-mcp-bridge — README · checked 2026-10-12| `query_entity` | The workhorse: filter, select, expand, orderBy, paging, `$count` |
SanoberRehman/cap-mcp-bridge — README · checked 2026-10-12| `invoke_action` | Call an action. **Write mode only** |
SanoberRehman/cap-mcp-bridge — README · checked 2026-10-12`cap-mcp-bridge` runs **outside** the service and consumes `$metadata` over HTTP.
SanoberRehman/cap-mcp-bridge — README · checked 2026-10-12That starts an MCP server on stdio.
Expose an application service to an AI agent → reading → Add MCP capabilities to a CAP service
Curated supporting reading for this assessment.
Basis: atlas-assessment
Expose an application service to an AI agent → reading → Examine the details of the Model Context Protocol on startup
Curated supporting reading for this assessment.
Basis: atlas-assessment
Expose an application service to an AI agent → reading → Model Context Protocol Adapter — CAP guide
Curated supporting reading for this assessment.
Basis: atlas-assessment
sap-developers:t:cap-add-mcp-capabilities → content:sap-tutorial-add-mcp-capabilities-to-a-cap-service
Same resource across graphs; this does not establish implementation compatibility.
Evidence matches captured sources · evidence captured 2026-10-12
sap-developers:t:cap-examine-mcp-startup → content:sap-tutorial-cap-examine-mcp-startup
Same resource across graphs; this does not establish implementation compatibility.
Evidence matches captured sources · evidence captured 2026-10-12
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.
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.
Related knowledge
Source subject or learning resource; applicability is established separately by the scoped assessment.
Why included: The CAP framework subject is broader than the Node.js runtime. This is a route to context, not package identity or compatibility. · SAP Developers
@cap-js/mcp → provides → Serve your application over MCP
Exposes an @mcp-annotated CAP Node.js 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.
Basis: atlas-record
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-12The CAP MCP adapter is intended only for exposing custom CAP application services.
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-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.
Model Context Protocol Adapter | capire · checked 2026-10-12Within your project root run this to add the @cap-js/mcp plugin for Node.js projects
@gavdi/cap-mcp → provides → Serve your application over MCP
Generates MCP resources and operation tools from annotated CAP Node.js services, with configured entity wrappers for query/get and optional create/update. The README requires Node.js 18+, CAP 10+ and Express 5+; resource reads and direct tools use service transactions in the pinned implementation. Output omission does not establish a field-access restriction. Annotations and wrapper modes select the exposed entities and operations. Entity resources, reusable prompt templates and @mcp.hint schema descriptions supply context; enable_model_description controls the model-description tool, and instructions configures server instructions. @mcp.omit filters output only: omitted fields remain queryable and can be supplied as write inputs.
Basis: atlas-record
CAP MCP Plugin — gavdilabs/cap-mcp-plugin README · checked 2026-10-12- **Node.js**: Version 18 or higher
CAP MCP Plugin — gavdilabs/cap-mcp-plugin README · checked 2026-10-12- **SAP CAP**: Version 10 or higher
CAP MCP Plugin — gavdilabs/cap-mcp-plugin README · checked 2026-10-12- **Express**: Version 5 or higher
CAP MCP Plugin — gavdilabs/cap-mcp-plugin README · checked 2026-10-12Omitted fields remain queryable in the CAP service - only MCP responses are filtered
CAP MCP Plugin — gavdilabs/cap-mcp-plugin README · checked 2026-10-12Annotate your CAP services with `@mcp` annotations:
CAP MCP Plugin — gavdilabs/cap-mcp-plugin README · checked 2026-10-12Convert CAP functions and actions into executable MCP tools
CAP MCP Plugin — gavdilabs/cap-mcp-plugin README · checked 2026-10-12Expose CAP entities as tools (`query`, `get`, and optionally `create`, `update`) for LLM tool use while keeping resources intact
CAP MCP Plugin — gavdilabs/cap-mcp-plugin README · checked 2026-10-12Define reusable prompt templates for AI interactions
CAP MCP Plugin — gavdilabs/cap-mcp-plugin README · checked 2026-10-12Hints are accessible in both resource queries and tool executions
CAP MCP Plugin — gavdilabs/cap-mcp-plugin README · checked 2026-10-12Expose CAP entities as MCP resources with OData v4 query capabilities
gavdilabs/cap-mcp-plugin — resources.ts at 1f3a97e1c0733d97c0cabea53d6d31767508daed · checked 2026-10-12const response = await service.tx({ user: accessRights }).run(query);
gavdilabs/cap-mcp-plugin — tools.ts at 1f3a97e1c0733d97c0cabea53d6d31767508daed · checked 2026-10-12const response = await service.tx({ user: accessRights }).send({
CAP MCP Plugin — gavdilabs/cap-mcp-plugin README · checked 2026-10-12Scans your CAP service definitions for `@mcp` annotations
CAP MCP Plugin — gavdilabs/cap-mcp-plugin README · checked 2026-10-12When `wrap_entities_to_actions` is enabled (globally or via `@mcp.wrap.tools: true`)
CAP MCP Plugin — gavdilabs/cap-mcp-plugin README · checked 2026-10-12Omitted fields are **only excluded from outputs** - they can still be provided as inputs for create/update operations
CAP MCP Plugin — gavdilabs/cap-mcp-plugin README · checked 2026-10-12Determines whether the MCP server should include the model description tool
CAP MCP Plugin — gavdilabs/cap-mcp-plugin README · checked 2026-10-12MCP server instructions for agents
@neoimpulse/cap-js-mcp → provides → Serve your application over MCP
Runs an MCP server inside a CAP Node.js application with default model/query tools and configured application modules. Default queries use service instances when available and otherwise cds.run(); custom operations supply their own service calls. The built-in product CRUD tools use in-memory demo data. Default tools read the running application’s compiled CDS model, including model definitions returned by search_model and get_cds_model. Configured tool, resource and prompt modules can inherit and override defaults; file/data resources and prompt templates are extensible. Custom business tools own their dispatch.
Basis: atlas-record
@neoimpulse/cap-js-mcp — published npm README · checked 2026-10-12Service-aware routing (uses service instances if available)
@neoimpulse/cap-js-mcp — published npm README · checked 2026-10-12Fallback to local execution (`cds.run()`)
@neoimpulse/cap-js-mcp — published npm README · checked 2026-10-12They use in-memory data storage and are not intended for production use.
@neoimpulse/cap-js-mcp — published npm README · checked 2026-10-12These tools work with **any CAP application** and use the compiled CDS model from the running application.
@neoimpulse/cap-js-mcp — published npm README · checked 2026-10-12"path": "./srv/lib/mcp-tools"
@neoimpulse/cap-js-mcp — published npm README · checked 2026-10-12**`execute_odata_query`** - Execute OData queries
@neoimpulse/cap-js-mcp — published npm README · checked 2026-10-12The built-in product catalog tools are for demonstration and testing purposes only.
@neoimpulse/cap-js-mcp — published npm README · checked 2026-10-12In a real application, you would implement tools that interact with your actual CAP services and data models.
@neoimpulse/cap-js-mcp — published npm README · checked 2026-10-12**MCP Resources**: File and data resource access (extensible)
@neoimpulse/cap-js-mcp — published npm README · checked 2026-10-12**MCP Prompts**: Template-based prompt system (extensible)
@neoimpulse/cap-js-mcp — published npm README · checked 2026-10-12**Resources** (`resources.extends`)
@neoimpulse/cap-js-mcp — published npm README · checked 2026-10-12const srv = await cds.connect.to('OrderService');
@neoimpulse/cap-js-mcp — published npm README · checked 2026-10-12return await srv.send('processOrder', args);
@neoimpulse/cap-js-mcp — published npm README · checked 2026-10-12// 4. No inheritance - just return main instance
@neoimpulse/cap-js-mcp — published npm README · checked 2026-10-12// Override: Tool exists in main class
@neoimpulse/cap-js-mcp — README · checked 2026-10-12Returns full CSN definitions with annotations and metadata
@neoimpulse/cap-js-mcp — README · checked 2026-10-12**`get_cds_model`** - Get the complete CDS model
cap-mcp-bridge → provides → Agent access to your systems
Canonical Atlas provides relationship.
Basis: atlas-record
@sap/cds → provides → Service integration
Builds a remote proxy with cds.connect.to for any imported service, translates a local query into OData V4, OData V2 or HCQL against the remote entity, and mocks the imported service in process until a binding is configured; outbound calls use the SAP Cloud SDK client when installed, else the native fetch client.
Basis: atlas-record
CAP-Level Service Integration — capire · checked 2026-09-27Remote CAP services can be consumed using the same high-level, uniform APIs as for local services – that is, as if they were local. cds.connect automatically constructs remote proxies, which translate all local requests into protocol-specific ones, sent to remote services.
CAP-Level Service Integration — capire · checked 2026-09-27CAP mocks imported services automatically in-process with mock data in the same in-memory database as our own data.
Remote Services Concept — capire · checked 2026-09-27CAP provides a built-in remote client that uses the native Node.js fetch API, including support for resolving named destinations from the SAP BTP Destination service.
cap-mcp-plugin → provides → Serve your application over MCP
Generates MCP entity resources and bound/unbound operation tools for CAP Node.js, with configured CRUD wrappers, a draft lifecycle and optional Fiori-derived MCP Apps. The README requires Node.js 18+, CAP 9+ and Express 4+. Resource/tool annotations and wrapper modes select the exposed surface; resource reads and direct operation tools call CAP service transactions in the pinned implementation. Entity resources, prompt templates and @mcp.hint schemas supply context, instructions configures server instructions, and MCP Apps require @mcp.wrap.tools with Fiori annotations. @mcp.omit filters output only, and disabling app write buttons leaves tools callable.
Basis: atlas-record
cap-mcp-plugin — sleibach/cap-mcp-plugin README · checked 2026-10-12- Node.js 18+
cap-mcp-plugin — sleibach/cap-mcp-plugin README · checked 2026-10-12- `@sap/cds` 9+
cap-mcp-plugin — sleibach/cap-mcp-plugin README · checked 2026-10-12- `express` 4+
cap-mcp-plugin — sleibach/cap-mcp-plugin README · checked 2026-10-12`@mcp.omit` filters MCP output only.
cap-mcp-plugin — sleibach/cap-mcp-plugin README · checked 2026-10-12no Create/Edit/Delete buttons (the write tools themselves are unaffected)
cap-mcp-plugin — sleibach/cap-mcp-plugin README · checked 2026-10-12Annotated entities become MCP resources, functions and actions become tools, and services can expose reusable prompt templates.
cap-mcp-plugin — sleibach/cap-mcp-plugin README · checked 2026-10-12CDS operations annotated with `@mcp.tool: true` become MCP tools.
cap-mcp-plugin — sleibach/cap-mcp-plugin README · checked 2026-10-12Both **unbound** (service-level) and **bound** (entity-level) operations are supported
cap-mcp-plugin — sleibach/cap-mcp-plugin README · checked 2026-10-12- `delete` — remove a row by key(s).
cap-mcp-plugin — sleibach/cap-mcp-plugin README · checked 2026-10-12- `draft-activate` — publish the pending draft to the active row.
cap-mcp-plugin — sleibach/cap-mcp-plugin README · checked 2026-10-12**Short-circuits active-row `create`, `update`, and `delete`** with a `DRAFT_REQUIRED` error
cap-mcp-plugin — sleibach/cap-mcp-plugin README · checked 2026-10-12entities annotated with `@odata.draft.bypass` (or the whole service with `cds.env.fiori.bypass_draft: true`) continue to accept direct active-row `create`/`update`/`delete`
cap-mcp-plugin — sleibach/cap-mcp-plugin README · checked 2026-10-12Declare reusable prompt templates.
cap-mcp-plugin — sleibach/cap-mcp-plugin README · checked 2026-10-12Enrich schemas for AI agents via `@mcp.hint` on elements and parameters.
cap-mcp-plugin — sleibach/cap-mcp-plugin README · checked 2026-10-12When an entity has `@mcp.wrap.tools` **and** Fiori UI annotations, the plugin registers two `ui://` HTML resources
sleibach/cap-mcp-plugin — resources.js at 5359398d0662f452d31529509c67634f8eb5406d · checked 2026-10-12const response = await service.tx({ user: accessRights }).run(query);
sleibach/cap-mcp-plugin — tools.js at 5359398d0662f452d31529509c67634f8eb5406d · checked 2026-10-12service.tx({ user: accessRights }).send({
cap-mcp-plugin — sleibach/cap-mcp-plugin README · checked 2026-10-12modes: ['query', 'get', 'create', 'update']
cap-mcp-plugin — sleibach/cap-mcp-plugin README · checked 2026-10-12Omitted fields can still be supplied as inputs on create / update operations and remain queryable in the underlying CAP service.
cap-mcp-plugin — sleibach/cap-mcp-plugin README · checked 2026-10-12Server-level instructions surfaced to agents
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 Framework (Cloud Application Programming Model) → contextualizes → @sap/cds
The CAP framework subject is broader than the Node.js runtime. This is a route to context, not package identity or compatibility.
Basis: pilot-mapping
Mapping: about · pending-human-review · authored from cited sources · checked 2026-10-06
CAP — Serving Media Data · checked 2026-10-06The media data is streamed automatically.
CAP Node.js 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
@sap/cds → previouslyContributedTo → CAP Node.js application bridge for custom external APIs outside SAP Application APIs
Last accepted assessment (2026-10-12): @sap/cds consumes remote services through CAP service APIs; the application supplies the contract and handlers that bridge the external system.
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/integration/calesi · checked 2026-10-12Remote services represented as CAP services, which you can consume as if they were local
https://cap.cloud.sap/docs/guides/integration/calesi · checked 2026-10-12Remote services are proxied by CAP services
@cap-js/mcp → previouslyContributedTo → CAP Node.js application bridge for custom external APIs outside SAP Application APIs
Last accepted assessment (2026-10-12): @cap-js/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.
@gavdi/cap-mcp → previouslyContributedTo → CAP Node.js application bridge for custom external APIs outside SAP Application APIs
Last accepted assessment (2026-10-12): @gavdi/cap-mcp — The inspected source dispatches resource queries and tool calls through the CAP application service; the application can supply remote-service handlers.
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://raw.githubusercontent.com/gavdilabs/cap-mcp-plugin/1f3a97e1c0733d97c0cabea53d6d31767508daed/src/mcp/resources.ts · checked 2026-10-12const response = await service.tx({ user: accessRights }).run(query);
https://raw.githubusercontent.com/gavdilabs/cap-mcp-plugin/1f3a97e1c0733d97c0cabea53d6d31767508daed/src/mcp/tools.ts · checked 2026-10-12const response = await service.tx({ user: accessRights }).send({
https://raw.githubusercontent.com/gavdilabs/cap-mcp-plugin/1f3a97e1c0733d97c0cabea53d6d31767508daed/README.md · checked 2026-10-12**SAP CAP**: Version 10 or higher
https://raw.githubusercontent.com/gavdilabs/cap-mcp-plugin/1f3a97e1c0733d97c0cabea53d6d31767508daed/README.md · checked 2026-10-12Uses your CAP application's existing authentication system:
https://raw.githubusercontent.com/gavdilabs/cap-mcp-plugin/1f3a97e1c0733d97c0cabea53d6d31767508daed/README.md · checked 2026-10-12When `wrap_entities_to_actions` is enabled (globally or via `@mcp.wrap.tools: true`), you will see tools named like:
https://raw.githubusercontent.com/gavdilabs/cap-mcp-plugin/1f3a97e1c0733d97c0cabea53d6d31767508daed/README.md · checked 2026-10-12**Node.js**: Version 18 or higher
https://raw.githubusercontent.com/gavdilabs/cap-mcp-plugin/1f3a97e1c0733d97c0cabea53d6d31767508daed/README.md · checked 2026-10-12**Express**: Version 5 or higher
cap-mcp-plugin → previouslyContributedTo → CAP Node.js application bridge for custom external APIs outside SAP Application APIs
Last accepted assessment (2026-10-12): cap-mcp-plugin — The inspected source dispatches queries and operations through the CAP application service, leaving remote integration to its handlers.
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://raw.githubusercontent.com/sleibach/cap-mcp-plugin/5359398d0662f452d31529509c67634f8eb5406d/lib/mcp/resources.js · checked 2026-10-12const response = await service.tx({ user: accessRights }).run(query);
https://raw.githubusercontent.com/sleibach/cap-mcp-plugin/5359398d0662f452d31529509c67634f8eb5406d/lib/mcp/tools.js · checked 2026-10-12service.tx({ user: accessRights }).send({
https://raw.githubusercontent.com/sleibach/cap-mcp-plugin/5359398d0662f452d31529509c67634f8eb5406d/README.md · checked 2026-10-12`@mcp.omit` filters MCP output only.
https://raw.githubusercontent.com/sleibach/cap-mcp-plugin/5359398d0662f452d31529509c67634f8eb5406d/README.md · checked 2026-10-12There is **no npm registry package yet**.
https://raw.githubusercontent.com/sleibach/cap-mcp-plugin/5359398d0662f452d31529509c67634f8eb5406d/README.md · checked 2026-10-12Auth modes: `inherit`
https://raw.githubusercontent.com/sleibach/cap-mcp-plugin/5359398d0662f452d31529509c67634f8eb5406d/README.md · checked 2026-10-12Where MCP session state lives.
https://raw.githubusercontent.com/sleibach/cap-mcp-plugin/5359398d0662f452d31529509c67634f8eb5406d/README.md · checked 2026-10-12Node.js 18+
https://raw.githubusercontent.com/sleibach/cap-mcp-plugin/5359398d0662f452d31529509c67634f8eb5406d/README.md · checked 2026-10-12`@sap/cds` 9+
https://raw.githubusercontent.com/sleibach/cap-mcp-plugin/5359398d0662f452d31529509c67634f8eb5406d/README.md · checked 2026-10-12`express` 4+
@neoimpulse/cap-js-mcp → previouslyContributedTo → CAP Node.js application bridge for custom external APIs outside SAP Application APIs
Last accepted assessment (2026-10-12): @neoimpulse/cap-js-mcp — The documentation shows a custom tool connecting to an application service and sending an operation; implementing the remote-system bridge remains application work.
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://www.npmjs.com/package/@neoimpulse/cap-js-mcp · checked 2026-10-12const srv = await cds.connect.to('OrderService');
https://www.npmjs.com/package/@neoimpulse/cap-js-mcp · checked 2026-10-12return await srv.send('processOrder', args);
https://www.npmjs.com/package/@neoimpulse/cap-js-mcp · checked 2026-10-12The built-in product catalog tools are for demonstration and testing purposes only.
cap-mcp-bridge → previouslyContributedTo → CAP Node.js 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://raw.githubusercontent.com/SanoberRehman/cap-mcp-bridge/0006d47ddcfe0291160ddc5f7c1e02007ee8cf7a/README.md · checked 2026-10-12Point it at any SAP CAP / OData v4 service.
https://raw.githubusercontent.com/SanoberRehman/cap-mcp-bridge/0006d47ddcfe0291160ddc5f7c1e02007ee8cf7a/README.md · checked 2026-10-12**Read-only by default.** Write tools only exist when `writeEnabled: true` (`--write`).
https://raw.githubusercontent.com/SanoberRehman/cap-mcp-bridge/0006d47ddcfe0291160ddc5f7c1e02007ee8cf7a/README.md · checked 2026-10-12`invoke_action` | Call an action. **Write mode only**
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.
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.
Related knowledge
Source subject or learning resource; applicability is established separately by the scoped assessment.
Why included: The CAP framework subject is broader than the Node.js runtime. This is a route to context, not package identity or compatibility. · SAP Developers
@cap-js/mcp → provides → Serve your application over MCP
Exposes an @mcp-annotated CAP Node.js 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.
Basis: atlas-record
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-12The CAP MCP adapter is intended only for exposing custom CAP application services.
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-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.
Model Context Protocol Adapter | capire · checked 2026-10-12Within your project root run this to add the @cap-js/mcp plugin for Node.js projects
@gavdi/cap-mcp → provides → Serve your application over MCP
Generates MCP resources and operation tools from annotated CAP Node.js services, with configured entity wrappers for query/get and optional create/update. The README requires Node.js 18+, CAP 10+ and Express 5+; resource reads and direct tools use service transactions in the pinned implementation. Output omission does not establish a field-access restriction. Annotations and wrapper modes select the exposed entities and operations. Entity resources, reusable prompt templates and @mcp.hint schema descriptions supply context; enable_model_description controls the model-description tool, and instructions configures server instructions. @mcp.omit filters output only: omitted fields remain queryable and can be supplied as write inputs.
Basis: atlas-record
CAP MCP Plugin — gavdilabs/cap-mcp-plugin README · checked 2026-10-12- **Node.js**: Version 18 or higher
CAP MCP Plugin — gavdilabs/cap-mcp-plugin README · checked 2026-10-12- **SAP CAP**: Version 10 or higher
CAP MCP Plugin — gavdilabs/cap-mcp-plugin README · checked 2026-10-12- **Express**: Version 5 or higher
CAP MCP Plugin — gavdilabs/cap-mcp-plugin README · checked 2026-10-12Omitted fields remain queryable in the CAP service - only MCP responses are filtered
CAP MCP Plugin — gavdilabs/cap-mcp-plugin README · checked 2026-10-12Annotate your CAP services with `@mcp` annotations:
CAP MCP Plugin — gavdilabs/cap-mcp-plugin README · checked 2026-10-12Convert CAP functions and actions into executable MCP tools
CAP MCP Plugin — gavdilabs/cap-mcp-plugin README · checked 2026-10-12Expose CAP entities as tools (`query`, `get`, and optionally `create`, `update`) for LLM tool use while keeping resources intact
CAP MCP Plugin — gavdilabs/cap-mcp-plugin README · checked 2026-10-12Define reusable prompt templates for AI interactions
CAP MCP Plugin — gavdilabs/cap-mcp-plugin README · checked 2026-10-12Hints are accessible in both resource queries and tool executions
CAP MCP Plugin — gavdilabs/cap-mcp-plugin README · checked 2026-10-12Expose CAP entities as MCP resources with OData v4 query capabilities
gavdilabs/cap-mcp-plugin — resources.ts at 1f3a97e1c0733d97c0cabea53d6d31767508daed · checked 2026-10-12const response = await service.tx({ user: accessRights }).run(query);
gavdilabs/cap-mcp-plugin — tools.ts at 1f3a97e1c0733d97c0cabea53d6d31767508daed · checked 2026-10-12const response = await service.tx({ user: accessRights }).send({
CAP MCP Plugin — gavdilabs/cap-mcp-plugin README · checked 2026-10-12Scans your CAP service definitions for `@mcp` annotations
CAP MCP Plugin — gavdilabs/cap-mcp-plugin README · checked 2026-10-12When `wrap_entities_to_actions` is enabled (globally or via `@mcp.wrap.tools: true`)
CAP MCP Plugin — gavdilabs/cap-mcp-plugin README · checked 2026-10-12Omitted fields are **only excluded from outputs** - they can still be provided as inputs for create/update operations
CAP MCP Plugin — gavdilabs/cap-mcp-plugin README · checked 2026-10-12Determines whether the MCP server should include the model description tool
CAP MCP Plugin — gavdilabs/cap-mcp-plugin README · checked 2026-10-12MCP server instructions for agents
@neoimpulse/cap-js-mcp → provides → Serve your application over MCP
Runs an MCP server inside a CAP Node.js application with default model/query tools and configured application modules. Default queries use service instances when available and otherwise cds.run(); custom operations supply their own service calls. The built-in product CRUD tools use in-memory demo data. Default tools read the running application’s compiled CDS model, including model definitions returned by search_model and get_cds_model. Configured tool, resource and prompt modules can inherit and override defaults; file/data resources and prompt templates are extensible. Custom business tools own their dispatch.
Basis: atlas-record
@neoimpulse/cap-js-mcp — published npm README · checked 2026-10-12Service-aware routing (uses service instances if available)
@neoimpulse/cap-js-mcp — published npm README · checked 2026-10-12Fallback to local execution (`cds.run()`)
@neoimpulse/cap-js-mcp — published npm README · checked 2026-10-12They use in-memory data storage and are not intended for production use.
@neoimpulse/cap-js-mcp — published npm README · checked 2026-10-12These tools work with **any CAP application** and use the compiled CDS model from the running application.
@neoimpulse/cap-js-mcp — published npm README · checked 2026-10-12"path": "./srv/lib/mcp-tools"
@neoimpulse/cap-js-mcp — published npm README · checked 2026-10-12**`execute_odata_query`** - Execute OData queries
@neoimpulse/cap-js-mcp — published npm README · checked 2026-10-12The built-in product catalog tools are for demonstration and testing purposes only.
@neoimpulse/cap-js-mcp — published npm README · checked 2026-10-12In a real application, you would implement tools that interact with your actual CAP services and data models.
@neoimpulse/cap-js-mcp — published npm README · checked 2026-10-12**MCP Resources**: File and data resource access (extensible)
@neoimpulse/cap-js-mcp — published npm README · checked 2026-10-12**MCP Prompts**: Template-based prompt system (extensible)
@neoimpulse/cap-js-mcp — published npm README · checked 2026-10-12**Resources** (`resources.extends`)
@neoimpulse/cap-js-mcp — published npm README · checked 2026-10-12const srv = await cds.connect.to('OrderService');
@neoimpulse/cap-js-mcp — published npm README · checked 2026-10-12return await srv.send('processOrder', args);
@neoimpulse/cap-js-mcp — published npm README · checked 2026-10-12// 4. No inheritance - just return main instance
@neoimpulse/cap-js-mcp — published npm README · checked 2026-10-12// Override: Tool exists in main class
@neoimpulse/cap-js-mcp — README · checked 2026-10-12Returns full CSN definitions with annotations and metadata
@neoimpulse/cap-js-mcp — README · checked 2026-10-12**`get_cds_model`** - Get the complete CDS model
cap-mcp-bridge → provides → Agent access to your systems
Canonical Atlas provides relationship.
Basis: atlas-record
@sap/cds → provides → Service integration
Builds a remote proxy with cds.connect.to for any imported service, translates a local query into OData V4, OData V2 or HCQL against the remote entity, and mocks the imported service in process until a binding is configured; outbound calls use the SAP Cloud SDK client when installed, else the native fetch client.
Basis: atlas-record
CAP-Level Service Integration — capire · checked 2026-09-27Remote CAP services can be consumed using the same high-level, uniform APIs as for local services – that is, as if they were local. cds.connect automatically constructs remote proxies, which translate all local requests into protocol-specific ones, sent to remote services.
CAP-Level Service Integration — capire · checked 2026-09-27CAP mocks imported services automatically in-process with mock data in the same in-memory database as our own data.
Remote Services Concept — capire · checked 2026-09-27CAP provides a built-in remote client that uses the native Node.js fetch API, including support for resolving named destinations from the SAP BTP Destination service.
cap-mcp-plugin → provides → Serve your application over MCP
Generates MCP entity resources and bound/unbound operation tools for CAP Node.js, with configured CRUD wrappers, a draft lifecycle and optional Fiori-derived MCP Apps. The README requires Node.js 18+, CAP 9+ and Express 4+. Resource/tool annotations and wrapper modes select the exposed surface; resource reads and direct operation tools call CAP service transactions in the pinned implementation. Entity resources, prompt templates and @mcp.hint schemas supply context, instructions configures server instructions, and MCP Apps require @mcp.wrap.tools with Fiori annotations. @mcp.omit filters output only, and disabling app write buttons leaves tools callable.
Basis: atlas-record
cap-mcp-plugin — sleibach/cap-mcp-plugin README · checked 2026-10-12- Node.js 18+
cap-mcp-plugin — sleibach/cap-mcp-plugin README · checked 2026-10-12- `@sap/cds` 9+
cap-mcp-plugin — sleibach/cap-mcp-plugin README · checked 2026-10-12- `express` 4+
cap-mcp-plugin — sleibach/cap-mcp-plugin README · checked 2026-10-12`@mcp.omit` filters MCP output only.
cap-mcp-plugin — sleibach/cap-mcp-plugin README · checked 2026-10-12no Create/Edit/Delete buttons (the write tools themselves are unaffected)
cap-mcp-plugin — sleibach/cap-mcp-plugin README · checked 2026-10-12Annotated entities become MCP resources, functions and actions become tools, and services can expose reusable prompt templates.
cap-mcp-plugin — sleibach/cap-mcp-plugin README · checked 2026-10-12CDS operations annotated with `@mcp.tool: true` become MCP tools.
cap-mcp-plugin — sleibach/cap-mcp-plugin README · checked 2026-10-12Both **unbound** (service-level) and **bound** (entity-level) operations are supported
cap-mcp-plugin — sleibach/cap-mcp-plugin README · checked 2026-10-12- `delete` — remove a row by key(s).
cap-mcp-plugin — sleibach/cap-mcp-plugin README · checked 2026-10-12- `draft-activate` — publish the pending draft to the active row.
cap-mcp-plugin — sleibach/cap-mcp-plugin README · checked 2026-10-12**Short-circuits active-row `create`, `update`, and `delete`** with a `DRAFT_REQUIRED` error
cap-mcp-plugin — sleibach/cap-mcp-plugin README · checked 2026-10-12entities annotated with `@odata.draft.bypass` (or the whole service with `cds.env.fiori.bypass_draft: true`) continue to accept direct active-row `create`/`update`/`delete`
cap-mcp-plugin — sleibach/cap-mcp-plugin README · checked 2026-10-12Declare reusable prompt templates.
cap-mcp-plugin — sleibach/cap-mcp-plugin README · checked 2026-10-12Enrich schemas for AI agents via `@mcp.hint` on elements and parameters.
cap-mcp-plugin — sleibach/cap-mcp-plugin README · checked 2026-10-12When an entity has `@mcp.wrap.tools` **and** Fiori UI annotations, the plugin registers two `ui://` HTML resources
sleibach/cap-mcp-plugin — resources.js at 5359398d0662f452d31529509c67634f8eb5406d · checked 2026-10-12const response = await service.tx({ user: accessRights }).run(query);
sleibach/cap-mcp-plugin — tools.js at 5359398d0662f452d31529509c67634f8eb5406d · checked 2026-10-12service.tx({ user: accessRights }).send({
cap-mcp-plugin — sleibach/cap-mcp-plugin README · checked 2026-10-12modes: ['query', 'get', 'create', 'update']
cap-mcp-plugin — sleibach/cap-mcp-plugin README · checked 2026-10-12Omitted fields can still be supplied as inputs on create / update operations and remain queryable in the underlying CAP service.
cap-mcp-plugin — sleibach/cap-mcp-plugin README · checked 2026-10-12Server-level instructions surfaced to agents
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 Framework (Cloud Application Programming Model) → contextualizes → @sap/cds
The CAP framework subject is broader than the Node.js runtime. This is a route to context, not package identity or compatibility.
Basis: pilot-mapping
Mapping: about · pending-human-review · authored from cited sources · checked 2026-10-06
CAP — Serving Media Data · checked 2026-10-06The media data is streamed automatically.
CAP Node.js 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
@sap/cds → previouslyContributedTo → CAP Node.js application bridge for SAP Application APIs
Last accepted assessment (2026-10-12): @sap/cds consumes remote services through CAP service APIs; the application supplies the contract and handlers that bridge the external system.
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/integration/calesi · checked 2026-10-12Remote services represented as CAP services, which you can consume as if they were local
https://cap.cloud.sap/docs/guides/integration/calesi · checked 2026-10-12Remote services are proxied by CAP services
@cap-js/mcp → previouslyContributedTo → CAP Node.js application bridge for SAP Application APIs
Last accepted assessment (2026-10-12): @cap-js/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.
@gavdi/cap-mcp → previouslyContributedTo → CAP Node.js application bridge for SAP Application APIs
Last accepted assessment (2026-10-12): @gavdi/cap-mcp — The documented CAP service dispatch/custom-tool mechanism is relevant, but the captured evidence does not establish this implementation as a supported bridge to the selected 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://raw.githubusercontent.com/gavdilabs/cap-mcp-plugin/1f3a97e1c0733d97c0cabea53d6d31767508daed/src/mcp/resources.ts · checked 2026-10-12const response = await service.tx({ user: accessRights }).run(query);
https://raw.githubusercontent.com/gavdilabs/cap-mcp-plugin/1f3a97e1c0733d97c0cabea53d6d31767508daed/src/mcp/tools.ts · checked 2026-10-12const response = await service.tx({ user: accessRights }).send({
https://github.com/gavdilabs/cap-mcp-plugin · checked 2026-10-12**SAP CAP**: Version 10 or higher
cap-mcp-plugin → previouslyContributedTo → CAP Node.js application bridge for SAP Application APIs
Last accepted assessment (2026-10-12): cap-mcp-plugin — The documented CAP service dispatch/custom-tool mechanism is relevant, but the captured evidence does not establish this implementation as a supported bridge to the selected 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://raw.githubusercontent.com/sleibach/cap-mcp-plugin/5359398d0662f452d31529509c67634f8eb5406d/lib/mcp/resources.js · checked 2026-10-12const response = await service.tx({ user: accessRights }).run(query);
https://raw.githubusercontent.com/sleibach/cap-mcp-plugin/5359398d0662f452d31529509c67634f8eb5406d/lib/mcp/tools.js · checked 2026-10-12service.tx({ user: accessRights }).send({
https://github.com/sleibach/cap-mcp-plugin · checked 2026-10-12`@mcp.omit` filters MCP output only.
https://github.com/sleibach/cap-mcp-plugin · checked 2026-10-12There is **no npm registry package yet**.
@neoimpulse/cap-js-mcp → previouslyContributedTo → CAP Node.js application bridge for SAP Application APIs
Last accepted assessment (2026-10-12): @neoimpulse/cap-js-mcp — The documented CAP service dispatch/custom-tool mechanism is relevant, but the captured evidence does not establish this implementation as a supported bridge to the selected 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://www.npmjs.com/package/@neoimpulse/cap-js-mcp · checked 2026-10-12const srv = await cds.connect.to('OrderService');
https://www.npmjs.com/package/@neoimpulse/cap-js-mcp · checked 2026-10-12return await srv.send('processOrder', args);
https://www.npmjs.com/package/@neoimpulse/cap-js-mcp · checked 2026-10-12The built-in product catalog tools are for demonstration and testing purposes only.
cap-mcp-bridge → previouslyContributedTo → CAP Node.js 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**
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.
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.
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**
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.
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.
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**
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.
The core gained an MCP protocol adapter. Before it, exposing a CAP service to an agent meant writing and maintaining a separate MCP server that restated the model; after it, @mcp on the service is the whole of it.
Guidance that you must hand-write an MCP server to put a CAP service in front of an agent. That was true until mid-2026 and is not now — what is left to build is governance and anything that writes data.
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.
capability:mcp-servers