Everything in the atlas
Type
Domain: 2
Origin
Signals
More: BTP/BAIP
Group by: Ecosystem
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.
SAP's Node.js driver for SAP HANA
Business data graph queried with OData V4 or GraphQL
Yeoman generator for Cloud Connector mappings and BTP destinations
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.
SAP's on-premises agent linking SAP BTP to customer-network systems
Builds and runs integration flows between cloud and on premise
Guided workflow for configuring SAP cloud solution integration
dbt adapter targeting SAP HANA Cloud as its warehouse
Managed queues and topics over AMQP, MQTT and REST
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.
B2B interface and mapping specification in Integration Suite
Java Swing tool maintaining Partner Directory entries for the Pipeline
Read-only MCP server for exploring SAP Datasphere
Business Source License 1.1, which is source-available rather than open source: reading and evaluating are fine, and production use is restricted until the licence's change date. That is a procurement question, not a technical one, and it is the thing to settle first. Read-only also means read-only — no modelling, no loads.
Binding onto hyperscaler object storage, chosen by plan
Prebuilt connectors to non-SAP cloud applications as REST APIs
Managed PostgreSQL from the hyperscaler via a BTP service binding
Managed Redis from the hyperscaler via a BTP service binding
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.
Managed SAP ASE databases on BTP for Java applications
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.
Distributes business events between SAP cloud applications
Proxy from cloud apps to on-premise systems via Cloud Connector
APIs for address cleansing, geocoding and suggestions
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.
Eighteen Datasphere skills over a bundled MCP server
It reaches a data warehouse, so what an agent can see is business data by definition — the SQL sanitisation and PII filtering in the server are there because of that, not instead of a decision about it. And the guidance is Datasphere-shaped: nothing here transfers to a HANA Cloud database used directly.
Named, credentialed addresses of other systems resolved at runtime
Ready-to-use web application for enterprise content
APIs and a UI5 component for document management in apps
Adobe Document Services on BTP for print and interactive PDFs
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
APIs for geocoding, map tiles and routing
Integration service on BTP with Cloud Integration and API Management
Event streaming and management platform in Integration Suite
Event broker inside SAP Integration Suite
Cloud service replicating master data across a hybrid landscape
Print queues between cloud applications and local printers
Private network link between a BTP service and a partner cloud
MCP server for the SAP Analytics Cloud REST API
Ninety tools is a large surface to put in front of a model at once, and client-credentials OAuth means the tenant sees one identity rather than the person asking. Content transport and user management sit in the same tool list as reading a story.
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.
MCP server managing Delta shares in SAP Business Data Cloud
Developer-centric command line for SAP HANA
Promise-based wrappers around the SAP HANA client libraries
Docker Compose IoT edge stack that connects to SAP BTP
Partner profiles and agreements for B2B exchange in Integration Suite
CodeJam on LLM-backed integration flows and MCP via API Management
Instructions for deploying Edge Integration Cell onto Microsoft Azure
@sap/approuter patterns in front of SAP Private Link Service
Integration flows pulling SAP Ariba spend data into SAP Datasphere
CAP and Fiori elements app for managing Cloud Integration datastores
SQL scripts and a notebook for SAP HANA's built-in graph algorithms
Tutorials and use cases for SAP HANA database and analytics products
Java demo running Spring and Hibernate against SAP HANA
Spring Boot apps routing AWS SDK traffic over SAP Private Link
Proof of concept turning AWS IoT events into S/4HANA notifications
CodeJam building an integration flow in SAP Integration Suite
CodeJam moving from polling to pub-sub on advanced event mesh
Spring Boot apps messaging over SAP Event Mesh's Java JMS client
Node.js samples for SAP Event Mesh's AMQP 1.0 messaging client
Starting project for a tutorial on NoSQL, graph and spatial in HANA
Course files for Developing Data Models with SAP HANA Cloud
Guides connecting hyperscaler sources into SAP Datasphere in BDC
TechEd 2025 workshop on SAP Business Data Cloud connectivity options
TechEd 2025 jump-start on a semantic model in SAP Datasphere and SAC
TechEd 2025 workshop piping business events into HANA vectors
TechEd 2025 workshop on exactly-once, in-order delivery
TechEd 2023 session on SAP HANA features over HDI
TechEd 2024 session on Integration Suite between SAP IBP and others
TechEd 2025 workshop on SAP HANA Cloud's AI capabilities
TechEd 2025 workshop on Just Ask natural-language questions
TechEd 2025 workshop on seamless planning for xP&A in BDC