Everything in CAP / Node.js
Type
Domain
Origin
Signals: Last 3 months
Node.js: Answers in Node.js
More: MIT
Group by: Capability
Swagger UI for a CAP service's OpenAPI definition
MCP server inside a CAP application with model and query tools
MCP server answering plain-English questions against a CDS schema
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
Data federation for CAP via delegation, caching and replication
Scheduled READ, MAP, WRITE pipelines between CAP services
CAP plugin uppercasing strings on write via @cds.uppercase
Data federation for CAP via delegation, caching and replication
MCP server generating tools from a CAP or OData V4 service's metadata
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.
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
Toolkit turning a CAP service into tools for agent frameworks
MCP server answering plain-English questions against a CDS schema
LangChain vector store on SAP AI Core Document Grounding
LangChain vector store with CDS entities for embeddings
Toolkit turning a CAP service into tools for agent frameworks
Shows which feature branches reached which environment branch
A team that does not keep one long-lived branch per environment has no environment branches for it to compare feature branches against. What it reports is the merge state of branches in Git, so it says nothing about whether a merged change has been built or deployed to the environment.
Policy enforcement and field masking for MCP-enabled CAP apps
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.
Endpoint discovery for CAP services deployed to Cloud Foundry
Static end-to-end tracer of one CAP operation across repositories
Workspace-wide CSN cache for querying CAP entities and columns
Interactive generator for CAP event handler files
Interactive project installer for CAP Node.js
Shared ESLint configuration for SAPUI5 and CAP projects
ESLint rules flagging deprecated CAP configuration
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.
Serves a Vite app through cds watch and imports .cds files
CAP project simulating S/4HANA Private Edition OData APIs locally
Decorator-driven handler registration for CAP in TypeScript
Typed BaseRepository over CAP entities
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