Everything in the atlas
Type
Domain
Origin
Signals: Last 6 months
More: 2
Group by: Ecosystem
Interactive generator for CAP event handler files
Shared ESLint configuration for SAPUI5 and CAP projects
Decorator-driven handler registration for CAP in TypeScript
Typed BaseRepository over CAP entities
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
CAP plugin uppercasing strings on write via @cds.uppercase
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.
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
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
Convention-based handler layer for CAP with draft lifecycle hooks
MCP server generating tools from a CAP or OData V4 service's metadata
Policy enforcement and field masking for MCP-enabled CAP apps
Fills db/data with relationally consistent CSV from a .cds schema
User details and quickview links for createdBy and modifiedBy
MCP server scaffolding CAP and CDS checked by cds compile
Toolkit turning a CAP service into tools for agent frameworks
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.
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
Scheduled READ, MAP, WRITE pipelines between CAP services
Captures CAP service errors, deduplicates them and mails alerts
Alerting by mail is not telemetry — if you need traces and metrics correlated across handlers, that is a different layer. It also publishes no repository, so the package is the only thing to read.
Fills a CDS element from a database-backed number range
CDS build task compiling TypeScript sources during cds build
Swagger UI for a CAP service's OpenAPI definition
ESLint rules flagging deprecated CAP configuration
Regex naming rules for SAP HANA artifacts in a CAP project
Everything it checks is a name: a file name under `rootDir`, or an identifier a parser extracted from a file, so a convention that cannot be written as a regex over one name has no rule shape here. Content rules targeting `.hdbanalyticalprivilege` or `.hdbconstraint` return no results, which the README states as not yet implemented, so conventions centred on those two artifact types go unchecked.
CAP agent writing reports into a shared SDM document workspace
Attaches a debugger to a CAP app running on Cloud Foundry
Terminal UI running Bruno collections against a CAP service
Serves a Vite app through cds watch and imports .cds files
Authenticating a CAP service against Azure AD B2C
CAP project simulating S/4HANA Private Edition OData APIs locally
UI5 custom control that runs an abap2UI5 app inside a host app
The page and the [abap2UI5](artifact:abap2ui5-abap2ui5) service have to share an origin: an `endpoint` that resolves to another origin is refused, and abap2UI5 rejects a POST whose `Origin` names another host. A host that routes by the URL hash, such as a Fiori elements app or an app with a UI5 router, needs abap2UI5 1.146.0 or later, because 1.145.0 clears the host's hash after every roundtrip. One frontend per page: the first control that starts decides which endpoint the frontend comes from.
Babel transformer from modern ES or TypeScript to UI5 module syntax
Yeoman generator for Application Frontend config in UI5 libraries
It targets the Application Frontend service only — not the HTML5 application repository — fixes authentication to IAS, and always creates new service instances, so reusing existing ones means editing the generated `mta.yaml` afterwards. Version 0.1.0 is the only release.
OpenUI5 JSONModel extension with CRUD over HTTP
Agent skill generating a Joule Frontend Actions bridge for UI5 apps
Command line running UI5 QUnit and OPA tests in parallel
VS Code side bar view of the SAPUI5 and OpenUI5 API reference
VS Code extension generating OData mock data from service metadata
WebdriverIO service running QUnit test pages