Everything in the atlas
Type
Domain: 2
Origin
Signals
More: 2
Group by: Capability
CDS plugin adding embedded analytics to CAP for SAP Analytics Cloud
Not in a project on CAP 7 or earlier: the package declares `@sap/cds` >=8 and `@sap/cds-compiler` >=5 as peer dependencies.
CAP Node.js runtime
Captures CAP service errors, deduplicates them and mails alerts
Alerting by mail is not telemetry — if you need traces and metrics correlated across handlers, that is a different layer. It also publishes no repository, so the package is the only thing to read.
Maven bill of materials pinning CAP Java module versions
Ten short CAP Java references, one document per topic
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.
Exports AsyncAPI documents for a CAP service's events
Generates Open Resource Discovery documents from a CAP model
CAP Node.js runtime
Generates Open Resource Discovery documents from a CAP Java model
Exposes a CAP service as OData V2
CAP Node.js runtime
OData V2 protocol adapter built into the CAP Java runtime
OData V4 protocol adapter for CAP Java Application Services
Local ABAP server serving /IWBEP/ OData v2 without an SAP system
Not a system to run a business application on: there is no business application in it, and what it implements of the language, the dictionary and Gateway is a stated subset of each. It is a clean-room reimplementation of the `/IWBEP/` interfaces that bundles no SAP source and no standard DDIC, so a service that reads standard objects has nothing to read, and `ANORMALIES.md` records every place the runtime differs from SAP before any workaround is written.
Calling an unbound CAP Java function from freestyle UI5
Neither the package manifest nor the repository tree declares a licence.
UI5 apps calling CAP OData actions and functions from custom code
Neither the package manifest nor the repository tree declares a licence.
Generates ABAP client classes and server stubs from OpenAPI
CAP Java service calling role collection APIs via a generated client
Neither the package manifest nor the repository tree declares a licence.
CAP Node.js runtime
Maven bill of materials pinning CAP Java module versions
Eclipse plug-in turning JSON or XML into ABAP types and DDIC objects
On an [SAP BTP ABAP environment](artifact:btp-abap-environment) system only the generated code is left: DDIC creation is not supported on ABAP Cloud, because classic DDIC object creation over REST is not available there. Create DDIC is also disabled where ADT is not installed in the same Eclipse, and Insert into Editor then works with any editor implementing `ITextEditor` instead of the ABAP one.
Exposes CAP services as MCP servers for AI agents
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.
MCP server inside a CAP application with model and query tools
MCP server exposing the ODATANO Cardano-to-OData bridge as tools
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.
MCP server exposing the NIGHTGATE Midnight attestation layer
MCP server answering plain-English questions against a CDS schema
MCP server for SAP BTP and Cloud Foundry acting as the logged-in user
MCP server generated from a CDS model, forked from @gavdi/cap-mcp
Not published to npm. Install from source.
MCP adapter turning a CAP Java service into an MCP server
SAP prohibits gateway/proxy use for SAP Application APIs; the Atlas separately excludes CAP wrappers around those APIs from its assessed scope. Data changes require application-defined unbound actions, and the adapter supplies no rate limiting, agent-action audit logging, approval workflows or policy enforcement.
Local chat client for SAP questions with a CAP LangGraph backend
Neither the package manifest nor the repository tree declares a licence.
CAP plugin letting the REST adapter accept XML payloads
Transactional processing of asynchronous and periodic CAP events
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.
SDK for SAP Advanced Financial Closing scheduling providers on CDS
CAP plugin watching Cardano addresses and emitting events
CAP Node.js runtime
Stores, browses and resends messages a CAP service receives
NATS messaging service for the CAP Node.js runtime
Last released December 2022. Nothing says it fails on current cds, but nothing says it was tried either. 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.
Maven bill of materials pinning CAP Java module versions
CAP Node.js runtime
Node module for CAP calling external APIs through a destination
Quiet Release and repository quiet for 57 months.
Functional boundary The package declares `@sap/cds` ^4.5.2 among its dependencies and pins `@sap-cloud-sdk/core` at 1.37.1, so a project on CAP 5 or later is outside the range it states.
Yeoman generator for Cloud Connector mappings and BTP destinations
Destination resolution and axios calls from CAP configuration
Release and repository quiet for 46 months.
Remote Services for consuming OData V2 and V4 APIs in CAP Java
SAP Cloud SDK integration for remote REST services in CAP Java
CAP project reaching S/4 via SAP BTP Private Link Service for Azure
Neither the package manifest nor the repository tree declares a licence.
CAP service serving Northwind's external OData Products as its own
CAP service actions calling OpenAI chat completions two ways
Neither the package manifest nor the repository tree declares a licence.
CAP Java service calling role collection APIs via a generated client
Neither the package manifest nor the repository tree declares a licence.
On-premise ABAP OData V2 service read from CAP over Connectivity
Neither the package manifest nor the repository tree declares a licence.
CAP Node.js action calling BAPI_EPM_BP_CREATE over RFC
Neither the package manifest nor the repository tree declares a licence.
MTA deploying CAP, HDI container and a Fiori elements app
Spring Boot apps routing AWS SDK traffic over SAP Private Link
Prints documents held in CAP entities through SAP Print service
CAP plugin wrapping the SAP Forms service by Adobe on BTP
CAP integration with SAP Integration Suite advanced event mesh
Exports AsyncAPI documents for a CAP service's events
Consumes events from SAP Cloud Application Event Hub in CAP
CAP Node.js runtime
Stores, browses and resends messages a CAP service receives
Kafka adapter exposing topics as a CDS messaging service
CAP Java plugin for SAP Integration Suite, advanced event mesh
Connects CAP Java messaging to SAP Event Mesh
Connects CAP Java messaging to SAP Cloud Application Event Hub
Connects CAP Java messaging to Apache Kafka
Beta connector from CAP Java messaging to Redis Pub/Sub
Maven bill of materials pinning CAP Java module versions
Event-driven RAG app with CAP, Cloud Integration and SAP HANA Cloud
Neither the package manifest nor the repository tree declares a licence.
CAP and Fiori elements app for managing Cloud Integration datastores
Annotation-driven mail on CAP entity lifecycle events
Node below 22, or [@sap/cds](artifact:sap-cds) below 9: the package declares the first in engines and the second as a peer dependency. Any mail path other than Microsoft Graph, until a provider is written for it: graph is the only kind that sends, and basic, the kind configured by default, is the base class such a provider extends.
Copy of @cap-js/notifications published under another scope
Reach for the original unless you know why you are not. This is a republished copy rather than a fork with a direction of its own: the README points at cap-js/notifications for the details, and nothing here says what was changed or why.
Business notifications from CAP Java via SAP Alert Notification
Calls to ABAP function modules over RFC from a CAP service
RFC client for Node.js and TypeScript without the NW RFC SDK
BUSL-1.1 rather than node-rfc's Apache-2.0, so a product you distribute has to be read against the licence and its Additional Use Grant first, and the source is closed: the GitHub repository is the issue tracker and the documentation, nothing else. `RfcServerOptions.bgRfcHandlers` raises instead of accepting handlers, so a server receiving inbound bgRFC units is outside what this does. An ABAP `MESSAGE`-raised failure still arrives with its T100 template rather than the rendered sentence, and the dump name is not reported as `key` for that case.
SDK-free TypeScript client for SAP synchronous RFC on Node.js
The maintainer states 0.x is beta with no production SLA, and scopes support deliberately narrowly: direct application-server transport, classic serialization and password authentication on S/4HANA 2023 and NetWeaver 7.50. Anything outside that is untested rather than unsupported.
CAP Node.js action calling BAPI_EPM_BP_CREATE over RFC
Neither the package manifest nor the repository tree declares a licence.
CAP Node.js runtime
Maven bill of materials pinning CAP Java module versions
CAP Node.js runtime
Command line client and development toolkit for CAP
Data federation for CAP via delegation, caching and replication
Remote Services for consuming OData V2 and V4 APIs in CAP Java
CAP services and a UI for trying role restrictions with mock users
Neither the package manifest nor the repository tree declares a licence.
CAP service serving Northwind's external OData Products as its own
CAP Java service consuming a Business Partner API mocked in Node.js
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.
On-premise ABAP OData V2 service read from CAP over Connectivity
Neither the package manifest nor the repository tree declares a licence.