Everything in CAP / Node.js
Type
Domain
Origin
Signals: 2
Node.js: Answers in Node.js
More: 3
Group by: Capability
CAP Node.js runtime
Six CAP features in one package, from replication cache to rate limits
It is a bundle, not a plugin with one job. Depending on it for one feature brings the rest.
Exports AsyncAPI documents for a CAP service's events
Generates Open Resource Discovery documents from a CAP model
CAP Node.js runtime
Exposes a CAP service as OData V2
CAP Node.js runtime
CAP Node.js runtime
Exposes CAP services as MCP servers for AI agents
SAP prohibits gateway/proxy use for SAP Application APIs; the Atlas applies that prohibition to CAP wrappers around those APIs. Data changes require application-defined unbound actions, and the adapter supplies no rate limiting, agent-action audit logging, approval workflows or policy enforcement. In beta, with nine releases in the six weeks after the first, so pin it.
MCP server inside a CAP application with model and query tools
MCP server exposing the ODATANO Cardano-to-OData bridge as tools
The repository the package declares has been deleted — verified against the GitHub API, not just a failed fetch. The package is still on npm, so it installs; the source it was published from is no longer readable, which is a harder thing to discover than a stale version number.
MCP server exposing the NIGHTGATE Midnight attestation layer
CAP Node.js runtime
CAP Node.js runtime
Six CAP features in one package, from replication cache to rate limits
It is a bundle, not a plugin with one job. Depending on it for one feature brings the rest.
CAP Node.js runtime
CAP caching plugin for query results and remote service responses
When user-dependent responses are cached without user-aware or explicit operation keys, or translated responses share keys across locales. These cases require key isolation; locale-aware keys are off by default.
Data federation for CAP via delegation, caching and replication
CAP Node.js runtime
Six CAP features in one package, from replication cache to rate limits
It is a bundle, not a plugin with one job. Depending on it for one feature brings the rest.
CAP Node.js runtime
Data federation for CAP via delegation, caching and replication
Scheduled READ, MAP, WRITE pipelines between CAP services
CAP Node.js runtime
Compiler from CDS models to CSN, EDMX and database schemas
CAP plugin casting read values back to CDS model types
CAP Node.js runtime
CAP Node.js runtime
Command line client and development toolkit for CAP
Six CAP features in one package, from replication cache to rate limits
It is a bundle, not a plugin with one job. Depending on it for one feature brings the rest.
CAP Node.js runtime
Multitenancy, tenant provisioning and extensibility for CAP
CAP Node.js runtime
CAP Node.js runtime
CAP Node.js runtime
CAP plugin stripping whitespace from strings on write via @cds.trim
CAP plugin uppercasing strings on write via @cds.uppercase
Transactional processing of asynchronous and periodic CAP events
If you need sub-second fan-out to external consumers this is the wrong layer — reach for [Event Mesh](artifact:btp-event-mesh) or Kafka. Without [Redis](external:redis), periodic processing still works but instant dispatch degrades to polling.
SDK for SAP Advanced Financial Closing scheduling providers on CDS
CAP Node.js runtime
CAP Node.js runtime
CAP integration with SAP Integration Suite advanced event mesh
Exports AsyncAPI documents for a CAP service's events
Consumes events from SAP Cloud Application Event Hub in CAP
CAP Node.js runtime
Annotation-driven mail on CAP entity lifecycle events
Node below 22, or [@sap/cds](artifact:sap-cds) below 9: the package declares the first in engines and the second as a peer dependency. Any mail path other than Microsoft Graph, until a provider is written for it: graph is the only kind that sends, and basic, the kind configured by default, is the base class such a provider extends.
Copy of @cap-js/notifications published under another scope
Reach for the original unless you know why you are not. This is a republished copy rather than a fork with a direction of its own: the README points at cap-js/notifications for the details, and nothing here says what was changed or why.
SDK-free TypeScript client for SAP synchronous RFC on Node.js
The maintainer states 0.x is beta with no production SLA, and scopes support deliberately narrowly: direct application-server transport, classic serialization and password authentication on S/4HANA 2023 and NetWeaver 7.50. Anything outside that is untested rather than unsupported.
CAP Node.js runtime
CAP Node.js runtime
Command line client and development toolkit for CAP
CAP service for typed decisions about one text or JSON state
CAP Java is outside it: the plugin is written for CAP Node.js applications, and `cds add decisions` prints a message and writes nothing in a Java project. A decision needs an answer, so the service cannot be queued: a truthy `queued`, `outboxed` or `outbox` setting fails with `INVALID_CONFIG`, which rules out handing a call to the outbox. The package is not yet on npm, so it is installed from a GitHub release archive, and the subclass hooks, the HTTP mock server, the `cds add` facet and the provider test kit are marked experimental.
Data federation for CAP via delegation, caching and replication
MCP server generating tools from a CAP or OData V4 service's metadata
CAP service kind putting eleven model providers behind one API
LangGraph Store keeping agent memory as CDS entities
Deep Agents filesystem over an SAP Document Management repository
Not a way to edit Office formats: the author states that access to a file does not automatically provide native editing of Word documents, spreadsheets or PDFs, and suggests starting with text-based content such as instructions, templates and reports. Not a control point either: a prompt telling the agent to ask for confirmation or to leave a template alone needs enforceable application controls where that is a business requirement, and the host application stays responsible for the authenticated request context and tenant isolation.
LangGraph checkpointer backed by CDS for CAP agents
CAP service kind putting eleven model providers behind one API
Toolkit turning a CAP service into tools for agent frameworks
Worked example of the cap-agent-ui5-webui plugin
Neither the package manifest nor the repository tree declares a licence.
CAP samples comparing SAP AI Core responses with content filtering
Every CDS service in both samples is marked `@requires: 'any'` and left publicly accessible, which the README says simplifies the testing and deployment process, and it asks for proper authentication mechanisms to be applied in their place.
CAP samples generating email through SAP AI Core with anonymization
Every CDS service in both samples is marked `@requires: 'any'` and left publicly accessible, which the README says simplifies the testing and deployment process, and it asks for proper authentication mechanisms to be applied in their place.
Shows @cap-js/mcp query results as a table inside the agent host
Value-help recommendations and SAP AI Core as a CAP service
CAP service kind putting eleven model providers behind one API
CAP service for typed decisions about one text or JSON state
CAP Java is outside it: the plugin is written for CAP Node.js applications, and `cds add decisions` prints a message and writes nothing in a Java project. A decision needs an answer, so the service cannot be queued: a truthy `queued`, `outboxed` or `outbox` setting fails with `INVALID_CONFIG`, which rules out handing a call to the outbox. The package is not yet on npm, so it is installed from a GitHub release archive, and the subclass hooks, the HTTP mock server, the `cds add` facet and the provider test kit are marked experimental.
CDS plugin and UI5 controls for AI text features via SAP AI Core
It is text processing, not an agent: there is no tool calling, no retrieval and no conversation. It needs SAP AI Core, and the backend half needs [@sap-ai-sdk/orchestration](artifact:sap-ai-sdk-orchestration) installed alongside it — an optional peer, so a frontend-only install stays lean.
Worked example of the cap-agent-ui5-webui plugin
Neither the package manifest nor the repository tree declares a licence.
CAP samples calling SAP AI Core through the SAP Cloud SDK for AI
Every CDS service in both samples is marked `@requires: 'any'` and left publicly accessible, which the README says simplifies the deployment process, and it asks for proper authentication mechanisms to be applied in their place.
Product-review screen consuming ui5-cap-ai-features on CAP
Neither the package manifest nor the repository tree declares a licence.
CAP service kind putting eleven model providers behind one API
CAP samples using SAP AI Core's Prompt Registry for templates
Every CDS service in both samples is marked `@requires: 'any'` and left publicly accessible, which the README says simplifies the testing and deployment process, and it asks for proper authentication mechanisms to be applied in their place.
CAP samples filling a prompt template sent to SAP AI Core
Every CDS service in both samples is marked `@requires: 'any'` and left publicly accessible, which the README says simplifies the testing and deployment process, and it asks for proper authentication mechanisms to be applied in their place.
Value-help recommendations and SAP AI Core as a CAP service
LangChain vector store on SAP AI Core Document Grounding
LangChain vector store with CDS entities for embeddings
CAP Node.js runtime
CAP service kind putting eleven model providers behind one API
Vector storage and similarity search on SAP HANA from CAP
CAP samples embedding CSV rows into the SAP HANA Cloud vector store
Every CDS service in both samples is marked `@requires: 'any'` and left publicly accessible, which the README says simplifies the testing and deployment process, and it asks for proper authentication mechanisms to be applied in their place.
CAP samples running RAG similarity queries over SAP HANA Cloud vectors
Every CDS service in both samples is marked `@requires: 'any'` and left publicly accessible, which the README says simplifies the testing and deployment process, and it asks for proper authentication mechanisms to be applied in their place.
Toolkit turning a CAP service into tools for agent frameworks
CAP Node.js runtime
Token validation and security context for XSUAA and IAS
Authorization from DCL policies for Node.js apps on SAP Cloud Identity
CAP Node.js runtime
Change history for annotated CAP entities
CAP Node.js runtime
CAP Node.js runtime
Six CAP features in one package, from replication cache to rate limits
It is a bundle, not a plugin with one job. Depending on it for one feature brings the rest.
CAP Node.js runtime
Generates Helm charts for the CAP Operator on Kubernetes
Command line client and development toolkit for CAP
Live-updatable feature toggles for CAP, backed by Redis
Multitenancy, tenant provisioning and extensibility for CAP
CAP Node.js runtime
Transactional processing of asynchronous and periodic CAP events
If you need sub-second fan-out to external consumers this is the wrong layer — reach for [Event Mesh](artifact:btp-event-mesh) or Kafka. Without [Redis](external:redis), periodic processing still works but instant dispatch degrades to polling.
CAP Node.js runtime
CLI for operating tenants of multitenant CAP applications
CAP Node.js runtime
Multitenancy, tenant provisioning and extensibility for CAP
Business-level metrics from CDS annotations via @cap-js/telemetry
OpenTelemetry instrumentation for CAP services
CAP caching plugin for query results and remote service responses
When user-dependent responses are cached without user-aware or explicit operation keys, or translated responses share keys across locales. These cases require key isolation; locale-aware keys are off by default.
Multitenancy, tenant provisioning and extensibility for CAP
Command line client and development toolkit for CAP
Connects a running CAP application to the CAP console
Inspects database entities and contents at CAP service level
Command line client and development toolkit for CAP
OData annotation features for the @sap/vscode-cds extension
Command line client and development toolkit for CAP
Six CAP features in one package, from replication cache to rate limits
It is a bundle, not a plugin with one job. Depending on it for one feature brings the rest.
CAP Node.js runtime
Command line client and development toolkit for CAP
Serves a Vite app through cds watch and imports .cds files
CAP project simulating S/4HANA Private Edition OData APIs locally
Command line client and development toolkit for CAP
Command line client and development toolkit for CAP
Compares a CAP project's CSV data with its database rows
CAP Node.js runtime
Test support for CAP Node.js: server start, HTTP client, assertions
Generates TypeScript types from a CDS model
Type definitions for the CAP Node.js SDK
CAP Node.js runtime
CAP Node.js runtime
Wrapper around the CDS compiler for annotation handling
OData annotation features for the @sap/vscode-cds extension
Singleton entity whose flags drive Fiori elements feature control
CLI for the SAP BTP Application Frontend service
CAP Node.js runtime
Playback-only SAP Companion (Help4) workarea served from CAP
Not behind a managed approuter: SAP Build Work Zone does not expose the `/$companion/**` routes, so Companion never reaches CAP, and the README names managed approuter and Work Zone as out of scope for v1. Not where help has to be authored in a browser, since the editor, the producer and writes are absent and content lives in files the plugin compiles.
CAP Node.js runtime
UI5 CLI middlewares running inside the CDS server
For a deployed application's UI. The README adds it with `npm add cds-plugin-ui5 -D`, a development dependency of the CDS server, and states nothing about a build or a deployment.
CAP Node.js runtime
Triggers n8n workflows from a CAP application
MCP server searching seventeen SAP documentation repositories
It reads documentation, never a system: nothing in it opens a package.json, a CDS model or an ABAP client, so a question about what your own project does has to be answered elsewhere. The offline half is only as fresh as the submodules the last build pinned, and the index answers where something is written down rather than which of two packages fits a task.
CAP agent writing reports into a shared SDM document workspace
CAP and SAPUI5 demo of recovery from a supply disruption
No license Neither the package manifest nor the repository tree declares a licence.
Functional boundary The data is illustrative: availability is binary and backup capacity unlimited, and the model carries no inventory; nothing in it is forecast or priced. The recall half runs only against classic ABAP, because its openCypher trace goes through ADBC, which is not released for ABAP Cloud, and it expects an SSH tunnel to the A4H system it was built against. A plain `npm start` passes no model key, so the agent cannot be used on a server started that way.