Everything in the atlas
Type
Domain
Origin: 2
Signals: No date
More
Group by: Capability
Maven bill of materials pinning CAP Java module versions
HL7 FHIR implementation for storing and exchanging health data
OData V2 protocol adapter built into the CAP Java runtime
OData V4 protocol adapter for CAP Java Application Services
Builds OData batch request payloads from an uploaded $metadata file
Marked BETA on its own page.
Maven bill of materials pinning CAP Java module versions
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.
ABAP add-on serving business data and transactions as MCP tools
Its maker offers it commercially.
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.
Ready-to-use web application for enterprise content
APIs and a UI5 component for document management in apps
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.
Maven bill of materials pinning CAP Java module versions
Cloud service replicating master data across a hybrid landscape
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.
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
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
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
Binding onto hyperscaler object storage, chosen by plan
Maven bill of materials pinning CAP Java module versions
Maven bill of materials pinning CAP Java module versions
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
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
Adobe Document Services on BTP for print and interactive PDFs
Print queues between cloud applications and local printers
Connects CAP Java messaging to SAP Event Mesh
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
Guided workflow for configuring SAP cloud solution integration
SAP's on-premises agent linking SAP BTP to customer-network systems
Proxy from cloud apps to on-premise systems via Cloud Connector
Maven bill of materials pinning CAP Java module versions
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
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.
Go MCP server that writes, activates and runs ABAP classes via ADT
Not reachable Not reachable since 2026-10-20.
Functional boundary `run_class` executes code in your system — that is the point and it is also the risk.
MCP server for ABAP on the ADT session, in Eclipse or standalone
In the Eclipse mode the server lives in a developer's IDE, binds to 127.0.0.1 and answers any request carrying an `Origin` header with HTTP 403, so a pipeline or a remote agent has nothing to reach; the standalone mode on the runtime of the ADT for VS Code extension is the documented route with no IDE open. A new connection starts in write mode, so the 11 write tools are live against a connected system until someone presses Toggle Read-Only. The dropins route for the two bundles is documented as untested.
Native macOS code editor for ABAP and CDS
It runs on macOS only. Hammer Core Services, the part installed into the SAP system, needs that system on ABAP Platform 2023 or newer with SAP_BASIS 758 or newer, and installing it needs a user who can create development objects and run background jobs in that system.
MCP server in ABAP inside the application server, with agent skills
Its maker offers it commercially.
SAP's AI for ABAP development in ADT for Eclipse and VS Code
ABAP add-on serving business data and transactions as MCP tools
Its maker offers it commercially.
MCP server in ABAP inside the application server, with agent skills
Its maker offers it commercially.
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.
ABAP add-on serving business data and transactions as MCP tools
Its maker offers it commercially.
MCP server in ABAP inside the application server, with agent skills
Its maker offers it commercially.
A2A adapter turning a CAP Java service into an LLM-backed agent
SAP's managed environment for building custom agents and workflows
Low-code SAP Build capability for custom Joule skills and agents
SAP's AI engagement layer across SAP applications
SAP's workspace for conversations, Spaces and directing agents
AI runtime on BTP with the Generative AI Hub
AI runtime on BTP with the Generative AI Hub
Extracts header fields and line items from business documents
SAP reuse library for calling large language models from ABAP
AI runtime on BTP with the Generative AI Hub
ML models that classify records and predict attributes
Machine learning recommendations over browsing history via REST
AI runtime on BTP with the Generative AI Hub
AI runtime on BTP with the Generative AI Hub
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.
API proxies with security and traffic policies and Developer Hub
CAP Java handler for SAP Audit Log service API version 2
Maven bill of materials pinning CAP Java module versions
Ingests and retains compliance audit data from BTP
SAP's on-premises agent linking SAP BTP to customer-network systems
Identity Authentication and Identity Provisioning as one tenant
OAuth2 token validation from XSUAA and SAP Cloud Identity Services
Former XSUAA JWT validation for CAP Java, removed in CAP Java 3.0
OAuth 2.0 grant flows for applications and APIs in Neo regions
OAuth server issuing JWTs and holding scopes for BTP apps
Registration, login and consent for customer-facing sites
Maven bill of materials pinning CAP Java module versions
OAuth 2.0 grant flows for applications and APIs in Neo regions
OAuth server issuing JWTs and holding scopes for BTP apps
Serves BTP applications under the customer's own domain
Change log of annotated entity fields for CAP Java
Registration, login and consent for customer-facing sites
APIs for retention, deletion and personal data reports
Retention rules triggering blocking, deletion and archiving
Service answering data subjects about their stored personal data
Key and certificate repository in SAP BTP's Neo data centres
Provisioning jobs carrying users and groups between systems
Maven bill of materials pinning CAP Java module versions
Scans uploaded files over REST with ClamAV
API proxies with security and traffic policies and Developer Hub
Vault for an application's passwords, keys and keyrings
Tracks vulnerabilities in open-source components of BTP apps
Converts classic Open SQL SELECTs to released CDS entities
In beta by its own page's account, where conversion bugs may occur and not all functions and variants are supported yet. The shapes named as not yet supported are sub selects, FOR ALL ENTRIES, functions such as count and sum, and the IN operator with a value list, so a statement built on one of those is outside what the converter sets out to do.
Hosted workspace redrawing custom ABAP as BPMN and grading it
Not reachable Not reachable since 2026-10-20.
Functional boundary The Level A–D grade merges SAP's two published files in the tool's own engine: it is an orientation rather than an ATC result and is left out of the signed audit pack, and the repository documents state by state where the grade is expected to differ from what the clean core ATC check reports. Nothing here runs ABAP Unit — on the RAP track that result is recorded from your own SAP system, and generated CAP tests run against mocks in an isolated runner rather than in a real SAP S/4HANA system. Tenants, organisation accounts, single sign-on, a self-hosted edition and write access through an API are deliberately not built, and one account has five analysis runs before a Gemini API key of its own is needed.
Browser form over SAP's Cloudification Repository for ABAP Cloud
Not for an automated check: the answer arrives as a page in a browser, so a rule that has to run over a codebase, or an agent mid-task, needs the repository as data rather than as a form.
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.
REST APIs for administering a BTP account
Registry for service brokers, instances and environments on SAP BTP
ABAP runtime on BTP for the ABAP Cloud model
1 of 8 plans deprecated.
Cloud Foundry runtime of SAP BTP for polyglot applications
Managed Kubernetes runtime on SAP BTP based on Kyma
MCP server for ABAP on the ADT session, in Eclipse or standalone
In the Eclipse mode the server lives in a developer's IDE, binds to 127.0.0.1 and answers any request carrying an `Origin` header with HTTP 403, so a pipeline or a remote agent has nothing to reach; the standalone mode on the runtime of the ADT for VS Code extension is the documented route with no IDE open. A new connection starts in write mode, so the 11 write tools are live against a connected system until someone presses Toggle Read-Only. The dropins route for the two bundles is documented as untested.
Native macOS code editor for ABAP and CDS
It runs on macOS only. Hammer Core Services, the part installed into the SAP system, needs that system on ABAP Platform 2023 or newer with SAP_BASIS 758 or newer, and installing it needs a user who can create development objects and run background jobs in that system.
MCP server in ABAP inside the application server, with agent skills
Its maker offers it commercially.
Moves MTA archives and content between SAP BTP accounts
Reads bound service credentials on SAP BTP, Cloud Foundry for CAP Java
Reads SAP BTP Operator service bindings on Kyma for CAP Java
Maven bill of materials pinning CAP Java module versions
REST APIs for SAP BTP usage per metric and monthly cost
Scales Cloud Foundry app instances by policy rules and schedules
Moves MTA archives and content between SAP BTP accounts
Assembles BTP service content into an MTAR for transport
Deploys and manages MTA-based Solutions in the Neo environment
Maven bill of materials pinning CAP Java module versions
Boolean and string flags read by applications at runtime
Calls an application endpoint on a schedule and logs each run
Maven bill of materials pinning CAP Java module versions
Collects Cloud Foundry or Kyma logs into a searchable Kibana
OpenSearch-based store for logs, metrics and traces
Multitenancy for CAP Java: tenant lifecycle and per-tenant containers
Maven bill of materials pinning CAP Java module versions
Registers a multitenant application for subaccount subscriptions