Everything in CAP
Type
Domain
Origin: Not from SAP
Signals: Last 3 months
More
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.
Simple CDS bookshop model used across CAP explanations
Neither the package manifest nor the repository tree declares a licence.
Swagger UI for a CAP service's OpenAPI definition
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
MCP server answering plain-English questions against a CDS schema
WebSocket and Socket.IO adapter for CDS services
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.
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
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.
Data federation for CAP via delegation, caching and replication
Scheduled READ, MAP, WRITE pipelines between CAP services
CAP plugin casting read values back to CDS model types
Tunnels CAP Node.js to a private PostgreSQL via Cloud Connector
Simple CDS bookshop model used across CAP explanations
Neither the package manifest nor the repository tree declares a licence.
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
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
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.
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.
Calling ABAP function modules over RFC from a CAP service
Neither the package manifest nor the repository tree declares a licence.
Data federation for CAP via delegation, caching and replication
MCP server scaffolding CAP and CDS checked by cds compile
MCP server generating tools from a CAP or OData V4 service's metadata
CAP service kind putting eleven model providers behind one API
Collection of 41 agent skills, 37 for SAP development tasks
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.
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.
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
Agent skill for SAP Customer Experience APIs, CDS and errors
Forty SAP development plugins for coding agents
GPL-3.0, which is a licence to read before vendoring any of it into something you ship. Forty plugins is also a lot of always-available surface — the ledger is there because breadth and verification pull in opposite directions, and it does not resolve that so much as report it.
Local desktop workspace for AI conversations with SAP connectors
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
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.
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.
Vercel AI SDK provider for SAP AI Core
CAP service kind putting eleven model providers behind one API
MCP server answering plain-English questions against a CDS schema
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.
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
LangChain vector store on SAP AI Core Document Grounding
LangChain vector store with CDS entities for embeddings
CAP service kind putting eleven model providers behind one API
Vector storage and similarity search on SAP HANA from CAP
Toolkit turning a CAP service into tools for agent frameworks
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.
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.
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.
Shows which feature branches reached which environment branch
A team that does not keep one long-lived branch per environment has no environment branches for it to compare feature branches against. What it reports is the merge state of branches in Git, so it says nothing about whether a merged change has been built or deployed to the environment.
Live-updatable feature toggles for CAP, backed by Redis
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
Policy enforcement and field masking for MCP-enabled CAP apps
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.
Consumer side of a CAP Java parent pom promotion model with Renovate
Neither the package manifest nor the repository tree declares a licence.
Endpoint discovery for CAP services deployed to Cloud Foundry
Static end-to-end tracer of one CAP operation across repositories
Workspace-wide CSN cache for querying CAP entities and columns
Interactive generator for CAP event handler files
Interactive project installer for CAP Node.js
Shared ESLint configuration for SAPUI5 and CAP projects
ESLint rules flagging deprecated CAP configuration
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.
Dev-time wrapper for the SAP Application Router
Serves a Vite app through cds watch and imports .cds files
Showcase for dev-approuter in front of two UI5 apps
CAP project simulating S/4HANA Private Edition OData APIs locally
Compares a CAP project's CSV data with its database rows
Decorator-driven handler registration for CAP in TypeScript
Typed BaseRepository over CAP entities
API documentation extracted from SAP-published npm packages
Simple CDS bookshop model used across CAP explanations
Neither the package manifest nor the repository tree declares a licence.
Singleton entity whose flags drive Fiori elements feature control
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
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.
Simple CDS bookshop model used across CAP explanations
Neither the package manifest nor the repository tree declares a licence.
Versioned specification of the abap2UI5 roundtrip protocol
Neither suite has been run against an ABAP system: the reference backends are the framework transpiled to Node and cap2UI5 on CAP, so what a check does on a real system is open. The portable profile is a subset of 61 controls, filled from a census of 247 core apps of which 64.8 % run unchanged, so an app outside it renders placeholders in the terminal and Adaptive Cards renderers.
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.
UI5 app consuming the cds-bookshop server via ui5-middleware-cap