Everything in the atlas
Type
Domain
Origin
Signals: Last 3 months
More: 3
Group by: Capability
CAP Node.js runtime
GraphQL protocol adapter generated from the CDS model
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 plugin serving the Cardano blockchain as OData V4
CAP plugin indexing the Midnight blockchain, exposed as OData V4
Compiler from a CDS service to SEGW model and data provider classes
The generated files are copied or deployed into the ABAP system by hand, the fourth step of its own usage list, so nothing keeps an activated service in step with the model it was generated from. Its peer dependency is `@sap/cds` ^9.8, so it does not install into a project on an earlier CAP release.
CAP Node.js runtime
Simple CDS bookshop model used across CAP explanations
Neither the package manifest nor the repository tree declares a licence.
Generates OpenAPI documents from a CDS service
Swagger UI for a CAP service's OpenAPI definition
CAP Node.js runtime
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
CodeJam on LLM-backed integration flows and MCP via API Management
CAP travel-booking app built on xflights master data
WebSocket and Socket.IO adapter for CDS services
MCP server with forty-five tools across a Datasphere tenant
It writes and it administers — ETL extraction and database user management are not read operations, and the same connection that profiles a column can move data out of the tenant. Masking is only as good as the configuration naming the fields, so an unlisted sensitive column is an unmasked one.
MCP server for BW/4HANA modelling objects
Its README says it plainly and so does this entry: this is not a simulation, every tool call reaches a live BW system, and write operations produce real changes. BW modelling objects are the definition of a warehouse — the blast radius of a wrong one is every report built on it.
Tutorials and use cases for SAP HANA database and analytics products
TechEd 2025 jump-start on a semantic model in SAP Datasphere and SAC
TechEd 2025 workshop on Just Ask natural-language questions
TechEd 2025 workshop on seamless planning for xP&A in BDC
CAP Node.js runtime
CAP Node.js attachments with database, S3, Azure or GCP storage
CAP attachments stored in an SAP Document Management repository
If document versions are required, [@cap-js/sdm](artifact:cap-js-sdm) excludes versioned repositories in its [documented restrictions](https://raw.githubusercontent.com/cap-js/sdm/ad13b61f21816ebead2d08264a74521cfb75846c/README.md).
CAP Node.js runtime
CAP Node.js attachments plugin with database or cloud storage
CAP Java attachments with database storage and an Object Store module
For deployed environments, the [README](https://raw.githubusercontent.com/cap-java/cds-feature-attachments/302f61c8bb76a0f54f43482ad91d89bf7dc5540f/README.md) excludes the cds-feature-attachments-fs file-system target, which is intended only for local development and testing.
CAP Java plugin for attachments in SAP Document Management
If document versions are required, the [documented restrictions](https://raw.githubusercontent.com/cap-java/sdm/673769f24ef66fd97daa6a6be41262d45065d3fe/README.md) exclude versioned repositories.
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.
CAP Node.js runtime
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
MCP server with forty-five tools across a Datasphere tenant
It writes and it administers — ETL extraction and database user management are not read operations, and the same connection that profiles a column can move data out of the tenant. Masking is only as good as the configuration naming the fields, so an unlisted sensitive column is an unmasked one.
MCP tooling for SAP Business Data Cloud discovery and contracts
Business Source License 1.1: source-available, with production use restricted until the change date — settle that before anything technical. And the governed execution path in v0.2 does act on data, which is a different grant from the discovery the v0.1 baseline offered.
CAP Node.js runtime
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.
CAP Node.js runtime
Data federation for CAP via delegation, caching and replication
Scheduled READ, MAP, WRITE pipelines between CAP services
CAP-to-CAP data federation over SAP HANA synonyms
When your adoption policy excludes experimental dependencies: the [maintainer’s README](https://github.com/cap-js/cds-federation-synonyms#about-this-project) explicitly labels this plugin experimental.
CAP Node.js runtime
Compiler from CDS models to CSN, EDMX and database schemas
CAP's getting-started bookshop sample
Five-part workshop on CDS, from a first service to constraints
CAP reuse package serving Airlines, Airports and Flights data
CAP Java reuse package for Airlines, Airports and Flights data
Developer-centric command line for SAP HANA
Base service shared by CAP's SQLite, PostgreSQL and HANA services
SAP HANA database service for CAP
PostgreSQL database service for CAP
SQLite database service for CAP, in memory during development
CAP plugin casting read values back to CDS model types
CAP Node.js runtime
SAP's Node.js driver for SAP HANA
Tunnels CAP Node.js to a private PostgreSQL via Cloud Connector
Pure JavaScript SAP HANA driver for Node.js
Its own feature comparison marks connection pooling, automatic reconnect, active-active reads, client-side data encryption, statement distribution, Kerberos authentication, the hdbuserstore, promises and TypeScript types as [@sap/hana-client](https://www.npmjs.com/package/@sap/hana-client) only, so a service that wants a pool or a promise API writes both itself over a callback interface. OpenSSL is its one security provider where the other driver lists SAP CommonCryptoLib, OpenSSL and MSCrypto, and it runs on Node.js 18 or later.
Promise-based wrappers around the SAP HANA client libraries
Simple CDS bookshop model used across CAP explanations
Neither the package manifest nor the repository tree declares a licence.
Composite CAP app from separately deployed services
CodeJam building a full-stack CAP app on SAP HANA Cloud
Starting project for a tutorial on NoSQL, graph and spatial in HANA
MCP server with forty-five tools across a Datasphere tenant
It writes and it administers — ETL extraction and database user management are not read operations, and the same connection that profiles a column can move data out of the tenant. Masking is only as good as the configuration naming the fields, so an unlisted sensitive column is an unmasked one.
MCP server for BW/4HANA modelling objects
Its README says it plainly and so does this entry: this is not a simulation, every tool call reaches a live BW system, and write operations produce real changes. BW modelling objects are the definition of a warehouse — the blast radius of a wrong one is every report built on it.
CAP Node.js runtime
Command line client and development toolkit for CAP
CAP-to-CAP data federation over SAP HANA synonyms
When your adoption policy excludes experimental dependencies: the [maintainer’s README](https://github.com/cap-js/cds-federation-synonyms#about-this-project) explicitly labels this plugin experimental.
Developer-centric command line for SAP HANA
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.
CAP Node.js runtime
Multitenancy, tenant provisioning and extensibility for CAP
CAP Node.js runtime
CAP Node.js runtime
CAP Node.js runtime
CAP plugin stripping whitespace from strings on write via @cds.trim
CAP plugin uppercasing strings on write via @cds.uppercase
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 Node.js runtime
TechEd 2025 workshop on exactly-once, in-order delivery
Destination lookup and connectivity proxy for the Cloud SDK
HTTP client carrying a destination's credentials
Shared machinery under the Cloud SDK's OData and OpenAPI clients
Generated OpenAPI clients for the Cloud SDK
Timeouts, retries and circuit breaking around remote calls
General utilities shared across the Cloud SDK packages
CAP Node.js runtime
Prebuilt SAP S/4HANA integration package for CAP projects
App-to-app setups between CAP Java and CAP Node.js under AMS and IAS
Neither the package manifest nor the repository tree declares a licence.
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
CAP Java plugin for SAP Integration Suite, advanced event mesh
Connects CAP Java messaging to SAP Cloud Application Event Hub
Proof of concept turning AWS IoT events into S/4HANA notifications
Spring Boot apps messaging over SAP Event Mesh's Java JMS client
Java Swing tool maintaining Partner Directory entries for the Pipeline
CodeJam on LLM-backed integration flows and MCP via API Management
Business notifications from CAP to SAP Build WorkZone
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
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.
Calling ABAP function modules over RFC from a CAP service
Neither the package manifest nor the repository tree declares a licence.
CAP Node.js runtime
Composite CAP app from separately deployed services
CAP travel-booking app built on xflights master data
CAP Node.js runtime
Command line client and development toolkit for CAP
Prebuilt SAP S/4HANA integration package for CAP projects
Data federation for CAP via delegation, caching and replication
CAP reuse package serving Airlines, Airports and Flights data
CAP travel-booking app built on xflights master data
MCP server for CAP development: model and docs search
The tools are documented as meant for AI models and not a stable API, so anything built to parse `cds-mcp` output rather than to feed a model can break between releases. Its corpus is the CAP documentation, so Fiori elements, BTP service or ABAP questions are not in what `search_docs` indexes.
MCP server with five tools for Mobile Development Kit work
It expects a real landscape, not just a project: a `.service.metadata` file naming the Mobile Services app, endpoint and destination, the Cloud Foundry CLI, and access to a BTP Cloud Foundry environment. From 0.4.0 macOS support is ARM64 only — Intel Macs are not supported — alongside Linux and Windows on x64 and ARM64.
MCP server for BW/4HANA modelling objects
Its README says it plainly and so does this entry: this is not a simulation, every tool call reaches a live BW system, and write operations produce real changes. BW modelling objects are the definition of a warehouse — the blast radius of a wrong one is every report built on it.
MCP server scaffolding CAP and CDS checked by cds compile
MCP server with forty-five tools across a Datasphere tenant
It writes and it administers — ETL extraction and database user management are not read operations, and the same connection that profiles a column can move data out of the tenant. Masking is only as good as the configuration naming the fields, so an unlisted sensitive column is an unmasked one.
BTP Core Services as MCP tools with in-chat dashboards
It administers a real account through Core Services, so what it can change is what the caller can change. And the UI half depends on hosts that render mcp-ui or MCP Apps resources; elsewhere those five tools return markup nobody displays.
MCP server with read tools over the SAP Cloud ALM APIs
MCP server generating tools from a CAP or OData V4 service's metadata
MCP server for schema discovery and guarded SQL on SAP HANA
This is the database, not an application in front of it, so what an agent can read is whatever the connection user can read — the guardrails bound the shape of a query, not the sensitivity of what it returns. Grant the connection the rights you would grant a person.
Config-driven proxy turning OData and REST endpoints into MCP tools
It fronts APIs you already have; nothing here reads a system's source or model, and a config file is only as good as the entity sets somebody wrote into it. OData V2 is the query surface it names.
MCP tooling for SAP Business Data Cloud discovery and contracts
Business Source License 1.1: source-available, with production use restricted until the change date — settle that before anything technical. And the governed execution path in v0.2 does act on data, which is a different grant from the discovery the v0.1 baseline offered.
Claude Code plugin registering hana-cli's MCP server
Developer-centric command line for SAP HANA
CAP service kind putting eleven model providers behind one API
Agent skills for CAP development, each a SKILL.md with references
Collection of 41 agent skills, 37 for SAP development tasks
TechEd 2025 session on benchmarking and optimising prompts