Everything in the atlas
Type
Domain
Origin: Not from SAP
Signals
More: 3
Group by: Capability
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.
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
Compiler from a CDS service to SEGW model and data provider classes
The generated files are copied or deployed into the ABAP system by hand, the fourth step of its own usage list, so nothing keeps an activated service in step with the model it was generated from. Its peer dependency is `@sap/cds` ^9.8, so it does not install into a project on an earlier CAP release.
Generates an MCP server from annotated CDS entities and actions
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
MCP server generated from a CDS model, forked from @gavdi/cap-mcp
Not published to npm. Install from source.
WebSocket and Socket.IO adapter for CDS services
CAP Node.js attachments plugin with Object Store and malware scanning
CAP Node.js attachments plugin with database or cloud storage
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.
Collaborative draft support for CAP Node.js services
The maintainer marks this under active development; public APIs, annotation names and OData contracts may still change.
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 plugin casting read values back to CDS model types
Tunnels CAP Node.js to a private PostgreSQL via Cloud Connector
CAP database adapter for Snowflake with OData V4 support
The maintainer marks this early development; expect the contract to move.
MongoDB as a CAP database service through Mongoose
It declares no peer range on [@sap/cds](artifact:sap-cds) and publishes no repository, so there is nothing to read but the package itself and no CI to look at.
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 plugin stripping whitespace from strings on write via @cds.trim
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 plugin watching Cardano addresses and emitting events
NATS messaging service for the CAP Node.js runtime
Last released December 2022. Nothing says it fails on current cds, but nothing says it was tried either. 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.
Renamed copy of @cap-js/notifications under another scope
Release and repository quiet for 24 months.
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 service kind putting eleven model providers behind one API
Collection of 41 agent skills, 37 for SAP development tasks
Agent skill for CAP multitenancy scaffolding
Local scaffolding only. Its own Out of Scope list names deployment to Cloud Foundry or Kyma, XSUAA and IAS configuration or any other BTP service binding, the SaaS Registry and subscription flow to real tenants, and automatic migration from the legacy `@sap/cds-mtx`. For the concepts rather than the scaffolding step, the README points at the `multitenancy` skill in [skillOverflow](artifact:dankromp-skilloverflow) by [Daniel Krompaß](actor:dankromp), which covers the MTX sidecar, `xs-security.json`, tenant lifecycle hooks and the deployment path and runs no commands at all.
Collection of 41 agent skills, 37 for SAP development tasks
CAP service kind putting eleven model providers behind one API
Exposes an annotated CDS service as an Agent-to-Agent agent
No public repository is declared on the package, so the README is the documentation.
UI5 web interface for an agent built in a CAP service
Not where the agent is reached over anything other than A2A: the README states the plugin does not speak anything other than A2A as @cap-js/agents serves it. Not where an upgrade has to be uneventful either — it pins @cap-js/agents to exactly 0.9.1, calls that package pre-1.0 and days old at the time of writing, and says this plugin inherits that instability and to expect breakage on upgrade.
Generative AI in CAP with fields anonymised through SAP HANA
Not where the records sit anywhere but [SAP HANA Cloud](artifact:btp-hana-cloud): the similarity search and the single retrieval method are both written against its vector engine, and the embeddings and the chat call go through [SAP AI Core](artifact:btp-ai-core), so a project without both has nothing here to call. Not where the dependency has to be an SAP-supported one either: the README states that the plugin is not an official SAP product and is published as a community contribution.
Vercel AI SDK provider for SAP AI Core
CAP service kind putting eleven model providers behind one API
Generative AI in CAP with fields anonymised through SAP HANA
Not where the records sit anywhere but [SAP HANA Cloud](artifact:btp-hana-cloud): the similarity search and the single retrieval method are both written against its vector engine, and the embeddings and the chat call go through [SAP AI Core](artifact:btp-ai-core), so a project without both has nothing here to call. Not where the dependency has to be an SAP-supported one either: the README states that the plugin is not an official SAP product and is published as a community contribution.
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.
Chat app on CAP and SAPUI5 against the OpenAI API
It calls the OpenAI API directly with a key in the environment. It was written in early 2023 and last touched in May 2023, which is before SAP AI Core and the CAP LLM plugins existed — so read it for the shape of the application, not for how a CAP service should reach a model today.
CAP service kind putting eleven model providers behind one API
CAP service kind putting eleven model providers behind one API
Vector storage and similarity search on SAP HANA from CAP
Generative AI in CAP with fields anonymised through SAP HANA
Not where the records sit anywhere but [SAP HANA Cloud](artifact:btp-hana-cloud): the similarity search and the single retrieval method are both written against its vector engine, and the embeddings and the chat call go through [SAP AI Core](artifact:btp-ai-core), so a project without both has nothing here to call. Not where the dependency has to be an SAP-supported one either: the README states that the plugin is not an official SAP product and is published as a community contribution.
Exposes an annotated CDS service as an Agent-to-Agent agent
No public repository is declared on the package, so the README is the documentation.
JWT authentication for CAP without xsuaa or xssec
Last released April 2022 at 0.0.2, and no repository is declared on the package.
Maps Microsoft Entra ID groups and app roles onto cds.User roles
Quiet Release and repository quiet for 25 months.
Functional boundary It performs no authentication flow of its own. The app must already be protected by Entra ID OAuth 2.0 at the App Service level; this only maps the resulting claims. It is explicitly not intended to run locally.
Custom messages and handler classes for CAP input validation
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.
Rate-limit pattern for CAP Node.js applications
Last released January 2024 at 0.0.6. 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.
Live-updatable feature toggles for CAP, backed by Redis
Feature-toggle pattern for CAP CDS
Last released June 2022 at 0.0.6, and no repository is declared on the package.
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.
CLI for operating tenants of multitenant CAP applications
Business-level metrics from CDS annotations via @cap-js/telemetry
UI5 frontend performance and error capture for CAP
OpenTelemetry support for the CDS Node.js runtime
Repository template with LICENSE, REUSE and compliance files
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.
Dev-time wrapper for the SAP Application Router
Showcase for dev-approuter in front of two UI5 apps
AWK script sketching an ER diagram from .cds files
No published releases; repository quiet for 26 months.
Compares a CAP project's CSV data with its database rows
Gherkin scenarios driving a running CAP service
Typed class-based service layer over CAP ApplicationService
Last released July 2022, and no repository is declared on the package.
One handler file per entity in CAP services
Chat app on CAP and SAPUI5 against the OpenAI API
It calls the OpenAI API directly with a key in the environment. It was written in early 2023 and last touched in May 2023, which is before SAP AI Core and the CAP LLM plugins existed — so read it for the shape of the application, not for how a CAP service should reach a model today.
Reusable internals for authors of CAP extensions
Explicitly internal utilities, so the surface is not a stable public API and last moved in March 2024. 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.
Collaborative draft support for CAP Node.js services
The maintainer marks this under active development; public APIs, annotation names and OData contracts may still change.
CAP plugin generating value help for enum fields from an annotation
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.
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 bookshop showing UI5 development with cds-plugin-ui5
CAP plugin rendering UI5 views with entity data on the server
On the UI5 path what comes back is an XML view or fragment with the data already substituted, streamed as the entity's media content, rather than an HTML page — the README calls this pre-rendering, and only the Vue path produces markup. The view kept under `srv/` has its UI5 bindings replaced by Handlebars expressions, so it is a second copy of the view, separate from the one the application ships. Version 1.0.8 declares `@sap/cds` `>=8` as its peer dependency, which puts a project on CAP 7 outside its stated range.
Integration of CAP with n8n workflows and triggers
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.
cds add plugin adding the incidents-app model to a project
Chat app on CAP and SAPUI5 against the OpenAI API
It calls the OpenAI API directly with a key in the environment. It was written in early 2023 and last touched in May 2023, which is before SAP AI Core and the CAP LLM plugins existed — so read it for the shape of the application, not for how a CAP service should reach a model today.