Sören Leibach
Entries
The maintainer marks this under active development; public APIs, annotation names and OData contracts may still change.
Collaborative draft support for CAP Node.js services
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.
Playback-only SAP Companion (Help4) workarea served from CAP
Not published to npm. Install from source.
MCP server generated from a CDS model, forked from @gavdi/cap-mcp
Integration of CAP with n8n workflows and triggers
The maintainer marks this early development; expect the contract to move.
CAP database adapter for Snowflake with OData V4 support
UI5 frontend performance and error capture for CAP
Value-help recommendations and SAP AI Core as a CAP service
Business notifications from CAP to SAP Build WorkZone
OpenTelemetry instrumentation for CAP services
Source repository of SAP's reference architectures
Writing and topics
Details
History
- cap-ui-telemetryTelemetry curation for the CAP door. This is the one option in the corpus answering the boundary the core states, that traces begin when a request arrives, and the entry did not say how it does it or that its records are logs rather than spans. Read against the README at commit 78e5d75.
- cap-mcp-pluginThe comparison distinguishes execution and surface selection at the stated runtime, retaining conditional operations and target restrictions.
- cap-mcp-pluginConverts the text answer to controlled list values. Its documented conditions remain in the capability relationship; original citations and runtime scope are retained.
- cap-mcp-pluginConverts the text answer to controlled list values. Its documented conditions remain in the capability relationship; original citations and runtime scope are retained.
- cap-mcp-pluginConverts the text answer to controlled list values. Its documented conditions remain in the capability relationship; original citations and runtime scope are retained.
- cap-mcp-pluginConverts the text answer to controlled list values. Its documented conditions remain in the capability relationship; original citations and runtime scope are retained.
- cap-mcp-pluginResolves the requested review findings while preserving the structured comparison values, runtime scopes and implementation restrictions.
- cap-collaborative-draftRefresh 2026-09-28. The plugin acquires a lock per OData property name in DRAFT.DraftFieldLocks and answers HTTP 409 when another participant holds a non-expired one, which is the job concurrency-control names; the edge was missing and both edges now carry what_it_does with the README's sentences.
- cap-collaborative-draftPlacement copied the package's own npm description. Replaced with a line written for this graph — what it does and where it sits — because an unattributed sentence is an unattributed claim.
- cap-collaborative-draftThe page had no answer to what it does; the paragraph states what it adds, what turns it on, and where it stops — the UI snippets the application owns, conflicts logged rather than merged, and the per-process WebSocket relay.
- cap-collaborative-draftThe README names it a required peer dependency for the real-time relay while its own compatibility table calls it optional; recorded as conditional on real-time presence, with both sentences quoted.
- cap-collaborative-draftThe README and the package's peerDependencies both state @sap/cds >= 8.0; the entry carried the runtime and not the range.
- cap-collaborative-draftStated rather than left to the cds-plugin fallback: the README's first line says CAP Node.js backends.
- First entry seenDiscovered via GitHub API · sleibach, npm registry.
For your agent
- Ref
actor:sleibach- JSON
- /actors/sleibach.json
- MCP
- Connecting an agent