Everything in CAP / Node.js
Type
Domain
Origin
Signals: Last 30 days
Node.js: Answers in Node.js
More: 3
Group by: Capability
MCP server inside a CAP application with model and query tools
CAP plugin uppercasing strings on write via @cds.uppercase
MCP server generating tools from a CAP or OData V4 service's metadata
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
LangChain vector store on SAP AI Core Document Grounding
LangChain vector store with CDS entities for embeddings
Versioned specification of the abap2UI5 roundtrip protocol
Neither suite has been run against an ABAP system: the reference backends are the framework transpiled to Node and cap2UI5 on CAP, so what a check does on a real system is open. The portable profile is a subset of 61 controls, filled from a census of 247 core apps of which 64.8 % run unchanged, so an app outside it renders placeholders in the terminal and Adaptive Cards renderers.
CAP agent writing reports into a shared SDM document workspace