Everything in the atlas
Type
Domain
Origin
Signals: Last 30 days
More: CAP
Group by: Capability
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
Connects a running CAP Java app to CAP console for monitoring
Language server for CDS
OData annotation features for the @sap/vscode-cds extension
CDS language support for VS Code and Business Application Studio
SAP CDS language support for IntelliJ IDEA
Interactive generator for CAP event handler files
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.
Shared functions and types of the Fiori generators
Command line client and development toolkit for CAP
ESLint rules for projects the Fiori tools generators produce
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.
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 Node.js runtime
Command line client and development toolkit for CAP
Dev-time wrapper for the SAP Application Router
Showcase for dev-approuter in front of two UI5 apps
Development container definition for CAP Node.js
Command line client and development toolkit for CAP
Command line client and development toolkit for CAP
Sample CAP plugin extending @sap/cds/common with reuse data
Sample CAP reuse service for orders, with a Fiori UI
Not in production. SAP states it is just a sample, not optimised for performance or security.
CAP Node.js runtime
Test support for CAP Node.js: server start, HTTP client, assertions
Fiori Elements mock server plugin taking a CDS file as metadata
Generates TypeScript types from a CDS model
Type definitions for the CAP Node.js SDK
API documentation extracted from SAP-published npm packages
CAP Node.js runtime
Simple CDS bookshop model used across CAP explanations
Neither the package manifest nor the repository tree declares a licence.
Event registration app showing OData V4 draft with UI5 and CAP
Parser for annotations in CDS source
Converter from CDS annotations to their OData form
Programmatic API for reading and writing project annotations
CAP Node.js runtime
Entry point for generating a Fiori application from a template
OData annotation features for the @sap/vscode-cds extension
Incident Management reference application for CAP
Travel-booking reference app on CAP Node.js and Java backends
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 bookshop showing UI5 development with cds-plugin-ui5
CAP Node.js runtime
CAP Node.js runtime
Triggers n8n workflows from a CAP application
Triggers n8n workflows from CAP Java through the outbox
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.
Fiori documentation indexed as embeddings
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.
Sources of capire, the CAP documentation
Simple CDS bookshop model used across CAP explanations
Neither the package manifest nor the repository tree declares a licence.
CAP's getting-started bookshop sample
Composite CAP app from separately deployed services
Incident Management reference application for CAP
Incident Management CAP app for the SAP BTP Developer's Guide
Travel-booking reference app on CAP Node.js and Java backends
Bookshop app demonstrating the CAP Java SDK end to end
CAP-based PWA for EV drivers proxying SAP E-Mobility OData APIs
Event registration app showing OData V4 draft with UI5 and CAP
CAP travel-booking app built on xflights master data
CAP Java travel-booking app built on xflights-java master data
Monorepo of CAP's SQL database services
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.