Everything in CAP / Node.js
Type: CDS plugin
Domain
Origin
Signals: Last 30 days
Node.js: Answers in Node.js
More
Group by: Capability
Distributed through
GraphQL protocol adapter generated from the CDS model
Exports AsyncAPI documents for a CAP service's events
Generates Open Resource Discovery documents from a CAP model
Exposes a CAP service as OData V2
CAP plugin serving the Cardano blockchain as OData V4
CAP plugin indexing the Midnight blockchain, exposed as OData V4
Generates OpenAPI documents from a CDS service
Swagger UI for a CAP service's OpenAPI definition
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
WebSocket and Socket.IO adapter for CDS services
CAP Node.js attachments with database, S3, Azure or GCP storage
CAP attachments stored in an SAP Document Management repository
If document versions are required, [@cap-js/sdm](artifact:cap-js-sdm) excludes versioned repositories in its [documented restrictions](https://raw.githubusercontent.com/cap-js/sdm/ad13b61f21816ebead2d08264a74521cfb75846c/README.md).
CAP-to-CAP data federation over SAP HANA synonyms
When your adoption policy excludes experimental dependencies: the [maintainer’s README](https://github.com/cap-js/cds-federation-synonyms#about-this-project) explicitly labels this plugin experimental.
SAP HANA database service for CAP
PostgreSQL database service for CAP
SQLite database service for CAP, in memory during development
CAP plugin casting read values back to CDS model types
CAP-to-CAP data federation over SAP HANA synonyms
When your adoption policy excludes experimental dependencies: the [maintainer’s README](https://github.com/cap-js/cds-federation-synonyms#about-this-project) explicitly labels this plugin experimental.
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.
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
Business notifications from CAP to SAP Build WorkZone
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.
CDS plugin for building agents inside a CAP service
Not as a gateway or proxy for SAP Application APIs: capire's guide states that CAP-level agents are intended only for exposing custom CAP application services and are not an SAP-endorsed architecture or pathway for agentic access to those APIs, and sends the reader to the SAP Architecture Center for the endorsed routes. Not as the screen a user of the application talks to, either — the chat preview in the generic index.html page is marked experimental and for local development.
LangGraph Store keeping agent memory as CDS entities
LangGraph checkpointer backed by CDS for CAP agents
Shows @cap-js/mcp query results as a table inside the agent host
Value-help recommendations and SAP AI Core as a CAP service
Value-help recommendations and SAP AI Core as a CAP service
CAP integration with the SAP Audit Log service
Authorization from DCL policies for Node.js apps on SAP Cloud Identity
Change history for annotated CAP entities
CAP integration with SAP Data Privacy Integration
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 integration with the SAP Audit Log service
Business-level metrics from CDS annotations via @cap-js/telemetry
OpenTelemetry instrumentation for CAP services
Connects a running CAP application to the CAP console
Inspects database entities and contents at CAP service level
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.
Triggers n8n workflows from a CAP application