Everything in the atlas
Type
Domain
Origin
Signals: Last 6 months
Content
More
Group by: Ecosystem
Compares a CAP project's CSV data with its database rows
Interactive generator for CAP event handler files
Business-level metrics from CDS annotations via @cap-js/telemetry
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.
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.
Live-updatable feature toggles for CAP, backed by Redis
CLI for operating tenants of multitenant CAP applications
Exposes a CAP service as OData V2
SDK for SAP Advanced Financial Closing scheduling providers on CDS
WebSocket and Socket.IO adapter for CDS services
CAP integration with SAP Integration Suite advanced event mesh
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.
Value-help recommendations and SAP AI Core as a CAP service
Exports AsyncAPI documents for a CAP service's events
CAP Node.js attachments with database, S3, Azure or GCP storage
CAP integration with the SAP Audit Log service
Generates Helm charts for the CAP Operator on Kubernetes
Monorepo of CAP's SQL database services
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
Change history for annotated CAP entities
Connects a running CAP application to the CAP console
Inspects database entities and contents at CAP service level
CAP integration with SAP Data Privacy Integration
Base service shared by CAP's SQLite, PostgreSQL and HANA services
Consumes events from SAP Cloud Application Event Hub in CAP
GraphQL protocol adapter generated from the CDS model
SAP HANA database service for CAP
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 for CAP development: model and docs search
The tools are documented as meant for AI models and not a stable API, so anything built to parse `cds-mcp` output rather than to feed a model can break between releases. Its corpus is the CAP documentation, so Fiori elements, BTP service or ABAP questions are not in what `search_docs` indexes.
Triggers n8n workflows from a CAP application
Business notifications from CAP to SAP Build WorkZone
Generates OpenAPI documents from a CDS service
Generates Open Resource Discovery documents from a CAP model
PostgreSQL database service for CAP
Prints documents held in CAP entities through SAP Print service
Starts and manages SAP Build Process Automation processes from CAP
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).
SQLite database service for CAP, in memory during development
OpenTelemetry instrumentation for CAP services
Shared ESLint configuration for SAPUI5 and CAP projects
Decorator-driven handler registration for CAP in TypeScript
Typed BaseRepository over CAP entities
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.
Generates an MCP server from annotated CDS entities and actions
Vercel AI SDK provider for SAP AI Core
Interactive project installer for CAP Node.js
LangChain vector store on SAP AI Core Document Grounding
LangChain vector store with CDS entities for embeddings
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
CLI starting several CAP services and an AppRouter locally together
MCP server inside a CAP application with model and query tools
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.
CAP plugin casting read values back to CDS model types
CAP plugin stripping whitespace from strings on write via @cds.trim
CAP plugin uppercasing strings on write via @cds.uppercase
CAP plugin serving the Cardano blockchain as OData V4
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.
CAP plugin indexing the Midnight blockchain, exposed as OData V4
MCP server exposing the NIGHTGATE Midnight attestation layer
CAP plugin watching Cardano addresses and emitting events
SAP's capire/skills packaged for the pi coding agent
If your tool reads the open skill standard directly, install [capire/skills](artifact:capire-skills) and skip the wrapper.
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.
CLI of CAP development tools for Cloud Foundry workflows
There is no repository and no README: what the eight commands do is only readable from the compiled dist that ships in the package. Three of them — npmrc, install, project — are written for "SimpleMDG" projects rather than for CAP generally, so the reusable part is bind-local, run-local and debug. Seven releases up to July 2026. Its binding step writes the resolved VCAP_SERVICES into default-env.json in the project, where [@sap/cds-dk](artifact:sap-cds-dk) keeps only the place the credentials can be fetched from, so a project using it needs that file kept out of version control.
CAP plugin controlling CDS logger and OpenTelemetry log verbosity
VS Code Multi-Target Application tools
AI Core control plane API surface of SAP's AI SDK
Shared internals of SAP's AI SDK
Client for foundation models via SAP AI Core and Generative AI Hub
Orchestration Service client for templating, grounding and masking
Client for prompts kept in SAP's prompt registry
Destination lookup and connectivity proxy for the Cloud SDK
HTTP client carrying a destination's credentials
Shared machinery under the Cloud SDK's OData and OpenAPI clients
Generated OpenAPI clients for the Cloud SDK
Timeouts, retries and circuit breaking around remote calls
General utilities shared across the Cloud SDK packages
Writer module for changing a CAP project's configuration from code
There is nothing to run: it is published for a generator or a script to call, not for a developer to invoke in a project, and it declares Node.js 22 or later.
Parser for annotations in CDS source
Converter from CDS annotations to their OData form
ESLint rules for projects the Fiori tools generators produce
Fiori Elements mock server plugin taking a CDS file as metadata
Programmatic API for reading and writing project annotations
Fiori documentation indexed as embeddings
Shared functions and types of the Fiori generators
Library for sending usage telemetry data
Authorization from DCL policies for Node.js apps on SAP Cloud Identity
Compiler from AMS DCL policies to DCN for local runs and tests
Its own account of itself is local running and tests: the DCN it writes serves as input for running an application using AMS on the DCL bundle locally. It carries the SAP Developer License Agreement rather than an open-source licence, and the repository named in its package metadata is an internal SAP host, so the npm page is the only thing to read.
CLI for the SAP BTP Application Frontend service
CAP Node.js runtime
ISO content for CAP's countries, languages, currencies and timezones
Compiler from CDS models to CSN, EDMX and database schemas
Command line client and development toolkit for CAP
Language server for CDS
Multitenancy, tenant provisioning and extensibility for CAP
WebAssembly sandbox for tenant-specific extension code in CAP
Calls to ABAP function modules over RFC from a CAP service
SAP's ESLint plugin for CDS
CAP project generator behind SAP Business Application Studio's wizard
CDS project generator, deprecated in favour of @sap/cds-dk
Entry point for generating a Fiori application from a template
Node.js deployer for SAP HANA Deployment Infrastructure containers
Wrapper around the CDS compiler for annotation handling
OData annotation features for the @sap/vscode-cds extension
CDS language support for VS Code and Business Application Studio
Token validation and security context for XSUAA and IAS
CAP service kind putting eleven model providers behind one API
Vector storage and similarity search on SAP HANA from CAP
Endpoint discovery for CAP services deployed to Cloud Foundry
Workspace-wide CSN cache for querying CAP entities and columns
Static end-to-end tracer of one CAP operation across repositories
MCP server answering plain-English questions against a CDS schema
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.
CAP review skill for coding agents with gates and prohibitions
No license Neither the package manifest nor the repository tree declares a licence.
Functional boundary There is no licence, so there is no grant to use or redistribute it. Everything else is secondary to that. Note too that its 'verified' claim means the skill text was checked against itself by an evaluation suite — not that the advice was run against a CAP version.
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.
CAP Node.js attachments plugin with database or cloud storage
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.
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.
Convention-based handler layer for CAP with draft lifecycle hooks
Bridge from CAP Java to SAP AI Core, with Fiori field recommendations
MCP server generating tools from a CAP or OData V4 service's metadata
Policy enforcement and field masking for MCP-enabled CAP apps
MCP server generated from a CDS model, forked from @gavdi/cap-mcp
Not published to npm. Install from source.
Fills db/data with relationally consistent CSV from a .cds schema
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.
Integration of CAP with n8n workflows and triggers
Tunnels CAP Node.js to a private PostgreSQL via Cloud Connector
Sample CAP plugin adding a generic data browser
Its own readme carries a caution: this is a sample, not intended for production use. It exists to demonstrate the plugin mechanism, and the bookstore sample is where it is used.
Showcase for dev-approuter in front of two UI5 apps
CAP bookshop wired to the Authorization Management Service
Neither the package manifest nor the repository tree declares a licence.
Simple CDS bookshop model used across CAP explanations
Neither the package manifest nor the repository tree declares a licence.
Java implementation of the capire/bookshop getting-started sample
Java implementation of the capire/bookstore composite app
CAP microservice on XSUAA managing users and authorizations
Worked example of the cap-agent-ui5-webui plugin
Neither the package manifest nor the repository tree declares a licence.
App-to-app setups between CAP Java and CAP Node.js under AMS and IAS
Neither the package manifest nor the repository tree declares a licence.
Authenticating a CAP service against Azure AD B2C
Event-driven RAG app with CAP, Cloud Integration and SAP HANA Cloud
Neither the package manifest nor the repository tree declares a licence.
CAP services reading each other's HANA tables across HDI containers
Neither the package manifest nor the repository tree declares a licence.
Singleton entity whose flags drive Fiori elements feature control
Consumer side of a CAP Java parent pom promotion model with Renovate
Neither the package manifest nor the repository tree declares a licence.
Maven parent pom pinning cds-services-bom and Spring Boot for CAP Java
Neither the package manifest nor the repository tree declares a licence.
Ten short CAP Java references, one document per topic
reCAP 2025 workshop on cutting a CAP app into microservices
Development container definition for CAP Node.js
CAP service actions calling OpenAI chat completions two ways
Neither the package manifest nor the repository tree declares a licence.
Calling ABAP function modules over RFC from a CAP service
Neither the package manifest nor the repository tree declares a licence.