Everything in the atlas
Type
Domain
Origin: SAP official
Signals
More
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
Maven bill of materials pinning CAP Java module versions
GraphQL protocol adapter generated from the CDS model
HL7 FHIR implementation for storing and exchanging health data
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
CAP Node.js runtime
OData V2 protocol adapter built into the CAP Java runtime
OData V4 protocol adapter for CAP Java Application Services
Generates OpenAPI documents from a CDS service
CAP Node.js runtime
Maven bill of materials pinning CAP Java module versions
Open-source Z* version of /UI2/CL_JSON for ABAP to JSON
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.
API proxies with security and traffic policies and Developer Hub
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.
SaaS for business intelligence, planning and predictive analytics
A tenant with its own model layer, its own transport and its own user administration — content moves between tenants through export and import jobs rather than through your pipeline, and planning brings a calendar and a workflow that a reporting-only use never touches.
Cloud data warehouse with spaces, views and analytic models
A tenant with spaces and a role model, not a database you point an application at — privileges are granted per space, and what somebody can model depends on the scoped role they hold. Federation is the default answer to moving data, and where it is not, a load has to be scheduled and watched.
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
SAP's UI elements as standard custom elements
Not where the UI library itself is expected to bind data: the documentation leaves binding a component's content and events to the host framework. Not from a CDN script tag: the project publishes none, so it assumes a build step.
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.
Ready-to-use web application for enterprise content
APIs and a UI5 component for document management in apps
CAP Node.js runtime
Managed Redis from the hyperscaler via a BTP service binding
Data products, a governed catalog and a path to SAP Databricks
It presumes the estate it governs: intelligent content is installed and viewed rather than authored, and the catalog is only as useful as what has been published into it. The Databricks path is a direction data goes, which is a decision about where analytics happens and not only about a tool.
Cloud data warehouse with spaces, views and analytic models
A tenant with spaces and a role model, not a database you point an application at — privileges are granted per space, and what somebody can model depends on the scoped role they hold. Federation is the default answer to moving data, and where it is not, a load has to be scheduled and watched.
CAP Node.js runtime
Maven bill of materials pinning CAP Java module versions
CAP Node.js runtime
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.
Cloud service replicating master data across a hybrid landscape
CAP Node.js runtime
ISO content for CAP's countries, languages, currencies and timezones
Compiler from CDS models to CSN, EDMX and database schemas
Modelling layer of ABAP Cloud above database tables
Nothing to choose here and nothing to install: it is what an ABAP Cloud system gives you. It shares a name and a lineage with CAP's CDS but is a different language in a different runtime, and a model does not move between them.
Maven bill of materials pinning CAP Java module versions
Managed SAP HANA database service on BTP
Provisioned per plan and per component, so capacity and cost are decisions taken before any model exists. And it is the database, not a warehouse — modelling, loading and cataloguing are the products above it, and reaching it directly bypasses every semantic they add.
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 Node.js runtime
Database adapter for SAP HANA in CAP
SAP's Node.js driver for SAP HANA
SAP HANA Cloud datasource for CAP Java applications
JDBC runtime for H2 and SQLite in CAP Java
PostgreSQL datasource for CAP Java applications
Maven bill of materials pinning CAP Java module versions
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.
Managed PostgreSQL from the hyperscaler via a BTP service binding
Managed SAP ASE databases on BTP for Java applications
SAP's relational database platform, on-premise and in HANA Cloud
For provisioning a managed database on BTP, see [SAP HANA Cloud](artifact:btp-hana-cloud). Features differ between HANA versions; an on-premise deployment and a cloud instance are not interchangeable without compatibility checks.
Managed SAP HANA database service on BTP
Provisioned per plan and per component, so capacity and cost are decisions taken before any model exists. And it is the database, not a warehouse — modelling, loading and cataloguing are the products above it, and reaching it directly bypasses every semantic they add.
Managed SAP HANA 2.0 databases in fixed sizes on SAP BTP
Promise-based wrappers around the SAP HANA client libraries
dbt adapter targeting SAP HANA Cloud as its warehouse
SaaS for business intelligence, planning and predictive analytics
A tenant with its own model layer, its own transport and its own user administration — content moves between tenants through export and import jobs rather than through your pipeline, and planning brings a calendar and a workflow that a reporting-only use never touches.
Cloud data warehouse with spaces, views and analytic models
A tenant with spaces and a role model, not a database you point an application at — privileges are granted per space, and what somebody can model depends on the scoped role they hold. Federation is the default answer to moving data, and where it is not, a load has to be scheduled and watched.
APIs for address cleansing, geocoding and suggestions
APIs for geocoding, map tiles and routing
CAP Node.js runtime
Command line client and development toolkit for CAP
Node.js deployer for SAP HANA Deployment Infrastructure containers
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
Binding onto hyperscaler object storage, chosen by plan
CAP Node.js runtime
Multitenancy, tenant provisioning and extensibility for CAP
Node.js deployer for SAP HANA Deployment Infrastructure containers
CAP Node.js runtime
Maven bill of materials pinning CAP Java module versions
CAP Node.js runtime
CAP Node.js runtime
Maven bill of materials pinning CAP Java module versions
CAP Node.js runtime
Maven bill of materials pinning CAP Java module versions
Managed queues and topics over AMQP, MQTT and REST
B2B interface and mapping specification in Integration Suite
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
Yeoman generator for Cloud Connector mappings and BTP destinations
Prebuilt SAP S/4HANA integration package for CAP projects
Remote Services for consuming OData V2 and V4 APIs in CAP Java
SAP Cloud SDK integration for remote REST services in CAP Java
Named, credentialed addresses of other systems resolved at runtime
Private network link between a BTP service and a partner cloud
Prints documents held in CAP entities through SAP Print service
Adobe Document Services on BTP for print and interactive PDFs
Print queues between cloud applications and local printers
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 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
Managed queues and topics over AMQP, MQTT and REST
Distributes business events between SAP cloud applications
Event streaming and management platform in Integration Suite
Event broker inside SAP Integration Suite
Builds and runs integration flows between cloud and on premise
Java Swing tool maintaining Partner Directory entries for the Pipeline
Guided workflow for configuring SAP cloud solution integration
Business notifications from CAP to SAP Build WorkZone
Business notifications from CAP Java via SAP Alert Notification
Calls to ABAP function modules over RFC from a CAP service
SAP's on-premises agent linking SAP BTP to customer-network systems
Proxy from cloud apps to on-premise systems via Cloud Connector
CAP Node.js runtime
ISO content for CAP's countries, languages, currencies and timezones
Maven bill of materials pinning CAP Java module versions
CAP Node.js runtime
Command line client and development toolkit for CAP
Prebuilt SAP S/4HANA integration package for CAP projects
Remote Services for consuming OData V2 and V4 APIs in CAP Java
Prebuilt connectors to non-SAP cloud applications as REST APIs
Partner profiles and agreements for B2B exchange in Integration Suite
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 for creating and editing Fiori applications
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 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.
SAP's ABAP tools in VS Code for editing, debugging, ATC and transports
Local HTTP MCP server started from ABAP Development Tools for VS Code
There is nothing to install and nothing to deploy, and equally nothing to run headless: in VS Code it exists only while ADT for VS Code is running with a logged-on ABAP project, so it is a developer's local surface rather than anything a pipeline or a hosted agent can reach. No public repository, so what it exposes is what the documentation says it exposes.
SAP's AI for ABAP development in ADT for Eclipse and VS Code
SAP-hosted MCP endpoint for BTP account administration
It acts on a real account. Authorisation is the caller's own — single sign-on through the SAP Default Identity Provider, across the global accounts that identity reaches — so what it can change is what you can change, and an agent invoking it is doing administration rather than proposing it. No public source, so what it exposes is what the documentation says it exposes.
Hosted MCP endpoint onto an SAP LeanIX instance
This is enterprise-architecture data, not a development surface — it answers what your landscape contains, never what your code does, and nothing in it belongs in a build. Entered here because it is a first-party SAP MCP endpoint and the catalogue that tracks this corner lists it; the atlas maps SAP development, so treat it as adjacent rather than as tooling for a project.
Claude Code plugin registering hana-cli's MCP server
Developer-centric command line for SAP HANA
Agent skills for CAP development, each a SKILL.md with references