onedevatlasBeta
Browse the atlas
AllCAPUI5ABAPBTP
CDS pluginCDS plugintypeInstalls into a CAP project and extends the runtime. CAP loads it through cds.requires or the plugin hook.See every one →What this type is →independently maintainedindependently maintainedoriginPublished by one person or a small company outside SAP. Says nothing about quality; the readings say that.See every one →

@neoimpulse/cap-js-mcp

An MCP server inside a CAP application, with default tools that read the running model and query entities, plus configurable application tools, prompts and resources.

Default tools read the running application’s compiled CDS model and query entities, while configured modules extend its tools, prompts and resources. The default tool implementation is inspired by @cap-js/mcp-server. Built-in product CRUD uses in-memory demo data; operations against real application services require custom implementation, with API-key authentication configured separately.

npm35/wk

Facts

Latestv1.0.7ReleasedLicenceApache License 2.0, January 2004

Where it sits

Lives in
CAP
Provides
Serve your application over MCPCAPServe your application over MCPcapabilityExposing selected application data and business operations to an AI agent through the Model Context Protocol. An application may also integrate remote services through [service integration](capability:service-integration), connecting its exposed contract with [agent access to your systems](capability:agent-systems-access). Development assistance belongs to [agent access to your code](capability:agent-code-access).
Flavors
Node.jsfrom its runtime
Requires
@sap/cds≥ 9@sap/cdsartifactThe peer range, as published.

Who is behind it

neoimpulse GmbHneoimpulse GmbHOrganisationMaintains this
In the atlas: maintains 7@neoimpulseGmbHmaintainer

Before choosing this

Conditions

LicenceSAP Developer License Agreement 3.2 CAP§ 1, 2, 3A cds-plugin is used with SAP CAP materials, or an artifact is explicitly identified as a CAP plugin or application.
  • § 1 License. Productive customer applications are limited to SAP BTP or another SAP-licensed platform, and mass extraction to a non-SAP product is restricted except where solely required for SAP interoperability.
  • § 2 Intellectual Property. The agreement retains SAP's rights in the covered materials and limits making APIs, tools or software available to third parties, while preserving ownership of customer applications subject to SAP's underlying rights.
  • § 3 Artificial Intelligence Training. The agreement prohibits use of the covered materials and customer applications for training artificial-intelligence models or systems.
SAP Developer License Agreement 3.2 CAP →

Also, from Serve your application over MCP§ 1, 3: 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.

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

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

SAP API Policy 4.2026a →

What it declares

Every artifact

Type
CDS plugin
Origin
Independently maintained
Runtime
Node.js

As a CDS plugin

Declared for
>=9
Distributed through
does not say

For serve your application over MCP

Exposure source
Compiled CDS model
Exposed operations
Default model/query tools; application business/write operations need custom tools; product CRUD is an in-memory demo
Context delivery
MCP resourcesMCP promptsModel descriptions via tools
Execution path
CAP service callsCDS query fallbackCustom tool handlers
Exposure control
Tool module configuration

Tasks this contributes to6Beta

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

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

What it does

@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.

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.

All options on the Serve your application over MCP page →
CAP Node.jsAssessed, not known

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

What it does

@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.

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.

All options on the Serve your application over MCP page →
Change application records from an agentCreate or update application records through an MCP client.Node.jsCovers, under conditionscustom application tool server
What it does

@neoimpulse/cap-js-mcp documents demo product CRUD and extension modules, but the demo operations use in-memory storage.

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.

All options on the Serve your application over MCP page →
Invoke a business operation from an agentInvoke a selected application business operation through an MCP tool.Node.jsCovers, under conditionscustom application tool server
What it does

@neoimpulse/cap-js-mcp lets the application supply custom business tools through configured modules.

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.

All options on the Serve your application over MCP page →
Provide application context as MCP resourcesLet an MCP client retrieve application data or schema context through resource URIs.Node.jsCovers, under conditionscustom resource module server
What it does

@neoimpulse/cap-js-mcp loads extensible file/data resource handlers from configured application modules.

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.

All options on the Serve your application over MCP page →
Publish reusable MCP promptsLet an MCP client discover and retrieve reusable, parameterized interaction templates.Node.jsCovers, under conditionscustom prompt module server
What it does

@neoimpulse/cap-js-mcp loads extensible prompt-template modules from the application.

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.

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

@neoimpulse/cap-js-mcp includes execute_odata_query and lets an application extend its configured tool modules.

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.

All options on the Serve your application over MCP page →

Connections3

Download
@neoimpulse/cap-js-mcp connections@neoimpulse/cap-js-mcpFUNCTIONAL→ alternative to1alternative to authored@cap-js/mcp→ provides1provides stated Runs an MCP server inside a CAP [Node.js](external:nodejs) 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. @neoimpulse/cap-js-mcp — published npm README: https://www.npmjs.com/package/@neoimpulse/cap-js-mcp @neoimpulse/cap-js-mcp — published npm README: https://www.npmjs.com/package/@neoimpulse/cap-js-mcp @neoimpulse/cap-js-mcp — published npm README: https://www.npmjs.com/package/@neoimpulse/cap-js-mcp @neoimpulse/cap-js-mcp — published npm README: https://www.npmjs.com/package/@neoimpulse/cap-js-mcp @neoimpulse/cap-js-mcp — published npm README: https://www.npmjs.com/package/@neoimpulse/cap-js-mcp @neoimpulse/cap-js-mcp — published npm README: https://www.npmjs.com/package/@neoimpulse/cap-js-mcp @neoimpulse/cap-js-mcp — published npm README: https://www.npmjs.com/package/@neoimpulse/cap-js-mcp @neoimpulse/cap-js-mcp — published npm README: https://www.npmjs.com/package/@neoimpulse/cap-js-mcp @neoimpulse/cap-js-mcp — published npm README: https://www.npmjs.com/package/@neoimpulse/cap-js-mcp @neoimpulse/cap-js-mcp — published npm README: https://www.npmjs.com/package/@neoimpulse/cap-js-mcp @neoimpulse/cap-js-mcp — published npm README: https://www.npmjs.com/package/@neoimpulse/cap-js-mcp @neoimpulse/cap-js-mcp — published npm README: https://www.npmjs.com/package/@neoimpulse/cap-js-mcp @neoimpulse/cap-js-mcp — published npm README: https://www.npmjs.com/package/@neoimpulse/cap-js-mcp @neoimpulse/cap-js-mcp — published npm README: https://www.npmjs.com/package/@neoimpulse/cap-js-mcp @neoimpulse/cap-js-mcp — published npm README: https://www.npmjs.com/package/@neoimpulse/cap-js-mcp @neoimpulse/cap-js-mcp — README: https://www.npmjs.com/package/@neoimpulse/cap-js-mcp @neoimpulse/cap-js-mcp — README: https://www.npmjs.com/package/@neoimpulse/cap-js-mcpServe your application over MCPLINEAGE→ inspired by1inspired by stated Neoimpulse — default-tool inspiration: https://www.npmjs.com/package/@neoimpulse/cap-js-mcp@cap-js/mcp-server

Install

npm add @neoimpulse/cap-js-mcp

Derived from the package name. No recipe recorded; the README has the configuration.

History

Latest

v1.0.7

  1. v1.0.6

  2. v1.0.5

  3. v1.0.4

  4. v1.0.3

  5. v1.0.2

  6. v1.0.1

  7. v1.0.0

On npm
31downloads per week, npm
Weekly downloads for @neoimpulse/cap-js-mcp26 complete calendar weeks from 2026-04-27 to 2026-10-25; the latest total is 31.27 Apr – 3 May: 94 May – 10 May: 2611 May – 17 May: 2018 May – 24 May: 1125 May – 31 May: 61 Jun – 7 Jun: 198 Jun – 14 Jun: 915 Jun – 21 Jun: 2322 Jun – 28 Jun: 229 Jun – 5 Jul: 196 Jul – 12 Jul: 1113 Jul – 19 Jul: 320 Jul – 26 Jul: 1627 Jul – 2 Aug: 63 Aug – 9 Aug: 910 Aug – 16 Aug: 1617 Aug – 23 Aug: 324 Aug – 30 Aug: 731 Aug – 6 Sept: 187 Sept – 13 Sept: 714 Sept – 20 Sept: 421 Sept – 27 Sept: 428 Sept – 4 Oct: 25 Oct – 11 Oct: 112 Oct – 18 Oct: 619 Oct – 25 Oct: 31

Others providing8

Compare all 9 on the Serve your application over MCP page →
Declared alternative
  1. @cap-js/mcpExposes CAP services as MCP servers for AI agents
Serve your application over MCP
  1. API ManagementAPI proxies with security and traffic policies and Developer Hub
  2. com.sap.cds:cds-adapter-mcpMCP adapter turning a CAP Java service into an MCP server
  3. @cap-js/mcpExposes CAP services as MCP servers for AI agents
  4. @gavdi/cap-mcpGenerates an MCP server from annotated CDS entities and actions
  5. @odatano/core-mcpMCP server exposing the ODATANO Cardano-to-OData bridge as tools
  6. @odatano/nightgate-mcpMCP server exposing the NIGHTGATE Midnight attestation layer
  7. @shahid.la/cds-db-nlquery-mcpMCP server answering plain-English questions against a CDS schema
  8. cap-mcp-pluginMCP server generated from a CDS model, forked from @gavdi/cap-mcp

Details

Connected knowledge — wider context2

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

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

Editorially accepted assessment · assessed . No Atlas runtime testing.

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

Supporting evidence changed; this accepted claim needs review.

Evidence status not tracked

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

Related knowledge

CAP Framework (Cloud Application Programming Model)

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

Why this assessment is relevant
  1. Access an external system through an application MCP service → CAP Node.js application bridge for custom external APIs outside SAP Application APIs
Relationships and evidence (17)
Gaps, source snapshot and retrieval limits
  • The application integration and MCP contributions are assessed separately; no captured source shows these complete generic bridge paths working against a chosen external system.
  • The selected target API, client and backend permissions, tenant mapping and remote error behavior need a project-specific assessment.
  • A compatible component does not establish an endorsed architecture or permission to expose an SAP Application API.
  • Evidence observations do not cover this accepted claim; it is retained as dated history.
  • Supporting evidence changed; this accepted claim needs review.
  • Retrieval uses at most four typed steps within a bounded source index. Source relationships do not establish compatibility.

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

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

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

Editorially accepted assessment · assessed . No Atlas runtime testing.

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

Supporting evidence changed; this accepted claim needs review.

Evidence status not tracked

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

Related knowledge

CAP Framework (Cloud Application Programming Model)

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

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

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

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

Sources3
npm registrydiscovered here, cds-pluginchecked
npm registrydiscovered here, @cap-jschecked
npm registry, @neoimpulse/cap-js-mcpversion, releases, installschecked

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

Compatibility and provenance
runtimesnode
declared for>=9
latestv1.0.7
first release
releases and cadence8, ~1d median
discovered vianpm registry · cds-plugin, npm registry · @cap-js
first seen in the atlas
ecosystem and domaincap, ai-and-agents
History in the atlas9
  1. An MCP server inside a CAP application, with default tools that read the running model and query entities, plus configurable application tools, prompts and resources.
  2. [{"key":"mcp_exposure_source","value":"Compiled CDS model plus configured tool/resource/prompt modules"},{"key":"mcp_operations","value":"Default model/query tools; application business/write operations need custom tools; product CRUD is an in-memory demo"},{"key":"mcp_context","value":"Extensible file/data resources and prompt templates; modules can inherit and override defaults"},{"key":"mcp_execution_path","value":"Default query tool uses a service instance when available, with cds.run() fallback; custom business tools own their dispatch"},{"key":"mcp_exposure_control","value":"Configured component modules and inheritance/overrides determine registered tools"}]
  3. Compiled CDS model
  4. MCP resources; MCP prompts; Model descriptions via tools
  5. CAP service calls; CDS query fallback; Custom tool handlers
  6. Tool module configuration
  7. npm only
  8. An MCP server inside a CAP application, where the tools, prompts and resources are modules you point it at rather than the model it derives.
  9. First seen.
For your agent
Ref
artifact:neoimpulse-cap-js-mcp
JSON
/artifacts/neoimpulse-cap-js-mcp.json
MCP
Connecting an agent