sjvans
Entries
Business-level metrics from CDS annotations via @cap-js/telemetry
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.
Transactional processing of asynchronous and periodic CAP events
Exposes a CAP service as OData V2
WebSocket and Socket.IO adapter for CDS services
CAP integration with SAP Integration Suite advanced event mesh
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
Value-help recommendations and SAP AI Core as a CAP service
Exports AsyncAPI documents for a CAP service's events
CAP Node.js attachments with database, S3, Azure or GCP storage
CAP integration with the SAP Audit Log service
Monorepo of CAP's SQL database services
Test support for CAP Node.js: server start, HTTP client, assertions
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
Consumes events from SAP Cloud Application Event Hub in CAP
GraphQL protocol adapter generated from the CDS model
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
Business notifications from CAP to SAP Build WorkZone
Generates OpenAPI documents from a CDS service
Generates Open Resource Discovery documents from a CAP model
PostgreSQL database service for CAP
SQLite database service for CAP, in memory during development
OpenTelemetry instrumentation for CAP services
Destination lookup and connectivity proxy for the Cloud SDK
HTTP client carrying a destination's credentials
Shared machinery under the Cloud SDK's OData and OpenAPI clients
Generated OpenAPI clients for the Cloud SDK
Timeouts, retries and circuit breaking around remote calls
General utilities shared across the Cloud SDK packages
CAP's getting-started bookshop sample
Composite CAP app from separately deployed services
Sources of capire, the CAP documentation
Incident Management reference application for CAP
The declared repository is archived.
PostgreSQL adapter for SAP CDS from the SAP Mentors community
CAP Java plugin for SAP Integration Suite, advanced event mesh
CAP Java plugin sending audit log events to SAP Audit Log service
Connects CAP Java messaging to SAP Cloud Application Event Hub
Not in production. SAP states it is just a sample, not optimised for performance or security.
Sample CAP reuse service for reviews, with a Fiori UI
Travel-booking reference app on CAP Node.js and Java backends
CAP reuse package serving 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
For your agent
- Ref
actor:sjvans- JSON
- /actors/sjvans.json
- MCP
- Connecting an agent