Steffen Waldmann
Entries
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.
CDS plugin for building agents inside a CAP service
Exports AsyncAPI documents for a CAP service's events
CAP integration with the SAP Audit Log service
Generates Helm charts for the CAP Operator on Kubernetes
Monorepo of CAP's SQL database services
Type definitions for the CAP Node.js SDK
Change history for annotated CAP entities
Base service shared by CAP's SQLite, PostgreSQL and HANA services
SAP HANA database service for CAP
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.
Exposes CAP services as MCP servers for AI agents
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.
MCP server for CAP development: model and docs search
Generates OpenAPI documents from a CDS service
PostgreSQL database service for CAP
SQLite database service for CAP, in memory during development
CAP's getting-started bookshop sample
Composite CAP app from separately deployed services
Sources of capire, the CAP documentation
GitHub Action setting up the Cloud Foundry CLI
Its own feature comparison marks connection pooling, automatic reconnect, active-active reads, client-side data encryption, statement distribution, Kerberos authentication, the hdbuserstore, promises and TypeScript types as [@sap/hana-client](https://www.npmjs.com/package/@sap/hana-client) only, so a service that wants a pool or a promise API writes both itself over a callback interface. OpenSSL is its one security provider where the other driver lists SAP CommonCryptoLib, OpenSSL and MSCrypto, and it runs on Node.js 18 or later.
Pure JavaScript SAP HANA driver for Node.js
Bookshop app demonstrating the CAP Java SDK end to end
Not in production. SAP states it is just a sample, not optimised for performance or security.
CAP sample sharing one domain model and database across apps
CAP reuse package serving Airlines, Airports and Flights data
CAP Java reuse package for Airlines, Airports and Flights data
CAP travel-booking app built on xflights master data
CAP Java travel-booking app built on xflights-java master data
Details
Profile
For your agent
- Ref
actor:swaldmann- JSON
- /actors/swaldmann.json
- MCP
- Connecting an agent