Everything in CAP / Node.js
Type
Domain: 2
Origin
Signals
Node.js: Answers in Node.js
More: 2
Group by: Capability
MCP server for UI5 development with ten tools
It reads a UI5 project and the framework's own documentation, not a running system or a backend: a question about the service behind the app is answered somewhere else. Node.js v20.17 or v22.9 and above.
MCP server generating tools from a CAP or OData V4 service's metadata
Developer-centric command line for SAP HANA
CAP service kind putting eleven model providers behind one API
Local desktop workspace for AI conversations with SAP connectors
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
CLI for Joule digital assistants and Joule Studio solutions
Pro-code CLI for building and deploying Joule Studio solutions
CAP service kind putting eleven model providers behind one API
Exposes an annotated CDS service as an Agent-to-Agent agent
No public repository is declared on the package, so the README is the documentation.
Toolkit turning a CAP service into tools for agent frameworks
Worked example of the cap-agent-ui5-webui plugin
Neither the package manifest nor the repository tree declares a licence.
Local chat client for SAP questions with a CAP LangGraph backend
Neither the package manifest nor the repository tree declares a licence.
CAP samples comparing SAP AI Core responses with content filtering
Every CDS service in both samples is marked `@requires: 'any'` and left publicly accessible, which the README says simplifies the testing and deployment process, and it asks for proper authentication mechanisms to be applied in their place.
CAP samples generating email through SAP AI Core with anonymization
Every CDS service in both samples is marked `@requires: 'any'` and left publicly accessible, which the README says simplifies the testing and deployment process, and it asks for proper authentication mechanisms to be applied in their place.
Shows @cap-js/mcp query results as a table inside the agent host
Value-help recommendations and SAP AI Core as a CAP service
Protocol adapter serving CAP data as TOON instead of JSON
CAP service kind putting eleven model providers behind one API
MCP server answering plain-English questions against a CDS schema
CAP service for typed decisions about one text or JSON state
CAP Java is outside it: the plugin is written for CAP Node.js applications, and `cds add decisions` prints a message and writes nothing in a Java project. A decision needs an answer, so the service cannot be queued: a truthy `queued`, `outboxed` or `outbox` setting fails with `INVALID_CONFIG`, which rules out handing a call to the outbox. The package is not yet on npm, so it is installed from a GitHub release archive, and the subclass hooks, the HTTP mock server, the `cds add` facet and the provider test kit are marked experimental.
CDS plugin and UI5 controls for AI text features via SAP AI Core
It is text processing, not an agent: there is no tool calling, no retrieval and no conversation. It needs SAP AI Core, and the backend half needs [@sap-ai-sdk/orchestration](artifact:sap-ai-sdk-orchestration) installed alongside it — an optional peer, so a frontend-only install stays lean.
Worked example of the cap-agent-ui5-webui plugin
Neither the package manifest nor the repository tree declares a licence.
CAP service actions calling OpenAI chat completions two ways
Neither the package manifest nor the repository tree declares a licence.
Chat app on CAP and SAPUI5 against the OpenAI API
It calls the OpenAI API directly with a key in the environment. It was written in early 2023 and last touched in May 2023, which is before SAP AI Core and the CAP LLM plugins existed — so read it for the shape of the application, not for how a CAP service should reach a model today.
Local chat client for SAP questions with a CAP LangGraph backend
Neither the package manifest nor the repository tree declares a licence.
CAP samples calling SAP AI Core through the SAP Cloud SDK for AI
Every CDS service in both samples is marked `@requires: 'any'` and left publicly accessible, which the README says simplifies the deployment process, and it asks for proper authentication mechanisms to be applied in their place.
Product-review screen consuming ui5-cap-ai-features on CAP
Neither the package manifest nor the repository tree declares a licence.
CAP service kind putting eleven model providers behind one API
CAP samples using SAP AI Core's Prompt Registry for templates
Every CDS service in both samples is marked `@requires: 'any'` and left publicly accessible, which the README says simplifies the testing and deployment process, and it asks for proper authentication mechanisms to be applied in their place.
CAP samples filling a prompt template sent to SAP AI Core
Every CDS service in both samples is marked `@requires: 'any'` and left publicly accessible, which the README says simplifies the testing and deployment process, and it asks for proper authentication mechanisms to be applied in their place.
Value-help recommendations and SAP AI Core as a CAP service
LangChain vector store on SAP AI Core Document Grounding
LangChain vector store with CDS entities for embeddings
CAP Node.js runtime
CAP service kind putting eleven model providers behind one API
Vector storage and similarity search on SAP HANA from CAP
Event-driven RAG app with CAP, Cloud Integration and SAP HANA Cloud
Neither the package manifest nor the repository tree declares a licence.
CAP service computing embeddings with HANA Cloud vector_embedding
CAP samples embedding CSV rows into the SAP HANA Cloud vector store
Every CDS service in both samples is marked `@requires: 'any'` and left publicly accessible, which the README says simplifies the testing and deployment process, and it asks for proper authentication mechanisms to be applied in their place.
CAP samples running RAG similarity queries over SAP HANA Cloud vectors
Every CDS service in both samples is marked `@requires: 'any'` and left publicly accessible, which the README says simplifies the testing and deployment process, and it asks for proper authentication mechanisms to be applied in their place.
Exposes an annotated CDS service as an Agent-to-Agent agent
No public repository is declared on the package, so the README is the documentation.
Toolkit turning a CAP service into tools for agent frameworks
Command line client and development toolkit for CAP
Groups npm audit findings by root dependency, with failing thresholds
It audits through npm: a project that resolves its dependencies with another package manager, or has no `package.json`, has nothing for it to run. What it reports is what `npm audit` knows, so a vulnerability outside the npm advisory data is not in its table.
CAP project built and deployed to Cloud Foundry by GitHub Actions
Connects a running CAP application to the CAP console
Inspects database entities and contents at CAP service level
Command line client and development toolkit for CAP
OData annotation features for the @sap/vscode-cds extension
Command line for changing features of an existing Fiori project
Writer of flexible programming model elements into Fiori elements apps
Writer that adds an OData service to an existing UI5 project
Command line client and development toolkit for CAP
Six CAP features in one package, from replication cache to rate limits
It is a bundle, not a plugin with one job. Depending on it for one feature brings the rest.
CLI starting several CAP services and an AppRouter locally together
Compiler from AMS DCL policies to DCN for local runs and tests
Its own account of itself is local running and tests: the DCN it writes serves as input for running an application using AMS on the DCL bundle locally. It carries the SAP Developer License Agreement rather than an open-source licence, and the repository named in its package metadata is an internal SAP host, so the npm page is the only thing to read.
CAP Node.js runtime
Command line client and development toolkit for CAP
Serves a Vite app through cds watch and imports .cds files
CAP Java service consuming a Business Partner API mocked in Node.js
Neither the package manifest nor the repository tree declares a licence.
CAP project simulating S/4HANA Private Edition OData APIs locally
Command line client and development toolkit for CAP
Command line client and development toolkit for CAP
Compares a CAP project's CSV data with its database rows
CAP Node.js runtime
CSV seed data generated from @Mockdata annotations with Faker
Quiet Release and repository quiet for 27 months.
Functional boundary Not a test-data factory. It writes files at build time to seed a database, so it does not build fixtures inside a unit test. The declared peer range stops at cds 7 — nothing says it fails on 9, but nothing says it was tried either.
Test support for CAP Node.js: server start, HTTP client, assertions
Static check that each exported TypeScript function has a test
It reads TypeScript exports only; a project written in plain JavaScript has no exported functions for it to extract. A call to the function name in a test file counts as tested, and a call through property access such as `.foo(` does not.
Convention-based handler layer for CAP with draft lifecycle hooks
Typed class-based service layer over CAP ApplicationService
Last released July 2022, and no repository is declared on the package.
One handler file per entity in CAP services
Chat app on CAP and SAPUI5 against the OpenAI API
It calls the OpenAI API directly with a key in the environment. It was written in early 2023 and last touched in May 2023, which is before SAP AI Core and the CAP LLM plugins existed — so read it for the shape of the application, not for how a CAP service should reach a model today.
Generates TypeScript types from a CDS model
Type definitions for the CAP Node.js SDK
Reusable internals for authors of CAP extensions
Explicitly internal utilities, so the surface is not a stable public API and last moved in March 2024. The repository the package declares has been deleted — verified against the GitHub API, not just a failed fetch. The package is still on npm, so it installs; the source it was published from is no longer readable, which is a harder thing to discover than a stale version number.
CAP service in TypeScript using types from @cap-js/cds-typer
LangGraph agent and UI5 chat screen over four BTP MCP servers
Neither the package manifest nor the repository tree declares a licence.
CAP agent writing reports into a shared SDM document workspace