Everything in the atlas
Type
Domain
Origin
Signals
More: CAP
Group by: Domain
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
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.
Generates an MCP server from annotated CDS entities and actions
Protocol adapter serving CAP data as TOON instead of JSON
Vercel AI SDK provider for SAP AI Core
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
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
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.
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
CAP service kind putting eleven model providers behind one API
Vector storage and similarity search on SAP HANA from CAP
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.
LangGraph agent and UI5 chat screen over four BTP MCP servers
Neither the package manifest nor the repository tree declares a licence.
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.
Bridge from CAP Java to SAP AI Core, with Fiori field recommendations
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.
MCP server generating tools from a CAP or OData V4 service's metadata
MCP server generated from a CDS model, forked from @gavdi/cap-mcp
Not published to npm. Install from source.
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.
MCP server scaffolding CAP and CDS checked by cds compile
Agent skills for CAP development, each a SKILL.md with references
Toolkit turning a CAP service into tools for agent frameworks
A2A adapter turning a CAP Java service into an LLM-backed agent
Collection of 41 agent skills, 37 for SAP development tasks
Joule's generative AI inside SAP Build Code
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.
CAP agent writing reports into a shared SDM document workspace
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.
Event-driven RAG app with CAP, Cloud Integration and SAP HANA Cloud
Neither the package manifest nor the repository tree declares a licence.
CAP service computing embeddings with HANA Cloud vector_embedding
CAP service actions calling OpenAI chat completions two ways
Neither the package manifest nor the repository tree declares a licence.
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.
VECTOR_EMBEDDING in a CDS entity for FAQ similarity search
Neither the package manifest nor the repository tree declares a licence.
Local chat client for SAP questions with a CAP LangGraph backend
Neither the package manifest nor the repository tree declares a licence.
CAP samples calling SAP AI Core through the SAP Cloud SDK for AI
Every CDS service in both samples is marked `@requires: 'any'` and left publicly accessible, which the README says simplifies the deployment process, and it asks for proper authentication mechanisms to be applied in their place.
CAP samples comparing SAP AI Core responses with content filtering
Every CDS service in both samples is marked `@requires: 'any'` and left publicly accessible, which the README says simplifies the testing and deployment process, and it asks for proper authentication mechanisms to be applied in their place.
CAP samples generating email through SAP AI Core with anonymization
Every CDS service in both samples is marked `@requires: 'any'` and left publicly accessible, which the README says simplifies the testing and deployment process, and it asks for proper authentication mechanisms to be applied in their place.
CAP samples using SAP AI Core's Prompt Registry for templates
Every CDS service in both samples is marked `@requires: 'any'` and left publicly accessible, which the README says simplifies the testing and deployment process, and it asks for proper authentication mechanisms to be applied in their place.
CAP samples filling a prompt template sent to SAP AI Core
Every CDS service in both samples is marked `@requires: 'any'` and left publicly accessible, which the README says simplifies the testing and deployment process, and it asks for proper authentication mechanisms to be applied in their place.
CAP samples embedding CSV rows into the SAP HANA Cloud vector store
Every CDS service in both samples is marked `@requires: 'any'` and left publicly accessible, which the README says simplifies the testing and deployment process, and it asks for proper authentication mechanisms to be applied in their place.
CAP samples running RAG similarity queries over SAP HANA Cloud vectors
Every CDS service in both samples is marked `@requires: 'any'` and left publicly accessible, which the README says simplifies the testing and deployment process, and it asks for proper authentication mechanisms to be applied in their place.
CAP app validating invoices with Document Information Extraction
CAP reference app for GenAI email support with RAG on HANA Cloud
CAP sample for semantic search with Generative AI Hub and HANA Cloud
A2A reference letting Joule delegate to a CAP pro-code agent
Financial Risk Analyzer built by an agent grounded in SAP MCP servers
CodeJam on a CAP job posting service using SAP AI Core over OData
Product-review screen consuming ui5-cap-ai-features on CAP
Neither the package manifest nor the repository tree declares a licence.
CAP integration with SAP Data Privacy Integration
Authorization from DCL policies for Node.js apps on SAP Cloud Identity
Custom messages and handler classes for CAP input validation
Azure AD and Azure AD B2C authentication strategy for CAP
Last released January 2022 at 0.0.21, against a passport strategy Microsoft has since deprecated.
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.
Zod schemas as CAP validation middleware
CDS plugin for OData change tracking in CAP applications
CAP Java plugin sending audit log events to SAP Audit Log service
CAP Java handler for SAP Audit Log service API version 2
Change log of annotated entity fields for CAP Java
OAuth2 token validation from XSUAA and SAP Cloud Identity Services
Former XSUAA JWT validation for CAP Java, removed in CAP Java 3.0
CAP plugin validating input against @Validator JSON Schema rules
Quiet Release and repository quiet for 30 months.
Functional boundary The annotation sits on a single element, so a rule that spans two fields, or one that needs a lookup, has nowhere in it to go.
Which CAP paths trigger @assert.target and which do not
Neither the package manifest nor the repository tree declares a licence.
CAP services and a UI for trying role restrictions with mock users
Neither the package manifest nor the repository tree declares a licence.
CAP bookshop wired to the Authorization Management Service
Neither the package manifest nor the repository tree declares a licence.
CAP microservice on XSUAA managing users and authorizations
CAP and Fiori app showing BTP Application Vulnerability Report data
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
CAP Java authorization checks tried case by case
Neither the package manifest nor the repository tree declares a licence.
OWASP Top 10 workshop exploiting and fixing flaws in a CAP Node.js app
TechEd 2025 workshop on OWASP Top 10 risks in CAP applications
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.
Live-updatable feature toggles for CAP, backed by Redis
CLI for operating tenants of multitenant CAP applications
CAP integration with the SAP Audit Log service
Generates Helm charts for the CAP Operator on Kubernetes
Type definitions for the CAP Node.js SDK
Change history for annotated CAP entities
Connects a running CAP application to the CAP console
Generates Open Resource Discovery documents from a CAP model
OpenTelemetry instrumentation for CAP services
Tool completing a CAP project's deployment configuration
Tied to a specific training repository and last released August 2023. 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 wrapping the SAP Forms service by Adobe on BTP
CAP plugin controlling CDS logger and OpenTelemetry log verbosity
VS Code Multi-Target Application tools
Library for sending usage telemetry data
CAP Node.js runtime
Fiori draft handling and UI-facing behaviour for CAP services
Multitenancy, tenant provisioning and extensibility for CAP
WebAssembly sandbox for tenant-specific extension code in CAP
Token validation and security context for XSUAA and IAS
Policy enforcement and field masking for MCP-enabled CAP apps
UI5 frontend performance and error capture for CAP
Feature-toggle pattern for CAP CDS
Last released June 2022 at 0.0.6, and no repository is declared on the package.
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.
GitHub Action setting up the Cloud Foundry CLI
Reads bound service credentials on SAP BTP, Cloud Foundry for CAP Java
Reads SAP BTP Operator service bindings on Kyma for CAP Java
Multitenancy for CAP Java: tenant lifecycle and per-tenant containers
Maven bill of materials pinning CAP Java module versions
OpenTelemetry support for the CDS Node.js runtime
reCAP 2025 workshop on cutting a CAP app into microservices
Approuter session held in a bound Redis cache instance
No license Neither the package manifest nor the repository tree declares a licence.
Functional boundary Not a descriptor to deploy as it stands: the approuter's `sessionSecret` is written out in `mta.yaml`.
MTA deploying CAP, HDI container and a Fiori elements app
Multitenant CAP application using cds-mtxs
Neither the package manifest nor the repository tree declares a licence.
Companion repo deploying a CAP app to Cloud Foundry two ways
Poetry Slam Manager, a multi-tenant SaaS reference app on SAP BTP
Customer-specific catering extension to the Poetry Slam Manager
CAP sample sharing one domain model and database across apps
Not in production. SAP states it is just a sample, not optimised for performance or security.
CAP Java sample sharing one domain model across several apps
Not in production. SAP states it is just a sample, not optimised for performance or security.
Guide migrating the hana-shine-xsa demo from XS Advanced to CAP
Directed at single-tenant applications, which the guide states as its scope. The migration path it uses also has no option to select individual containers, so it migrates every container in the given space.
Guide to migrating XS Advanced database artefacts to CAP
Guide to migrating XS Classic database artefacts to CAP
Directed at single-tenant applications, which the guide states as its scope. Migration of the whole delivery unit or package fails if any source file has errors; the README gives JavaScript files containing unknown characters as its example.