Everything in the atlas
Type
Domain: 2
Origin
Signals
More: BTP/BAIP
Group by: Capability
HL7 FHIR implementation for storing and exchanging health data
API proxies with security and traffic policies and Developer Hub
MCP server for SAP BTP and Cloud Foundry acting as the logged-in user
UI5 app and CAP service copying role collections between subaccounts
Quiet No published releases; repository quiet for 54 months.
No license Neither the package manifest nor the repository tree declares a licence.
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.
Containerised script setting up an SAP BTP account from JSON config
The declared repository is archived.
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
Terraform and OpenTofu provider for SAP BTP global accounts
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
Moves MTA archives and content between SAP BTP accounts
REST APIs for SAP BTP usage per metric and monthly cost
Python agent alerting on SAP AI Core capacity unit consumption
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
MTA generation and Cloud Foundry deploy for VS Code workspaces
A library a VS Code extension calls, not something installed and run on its own; there is no documented standalone CLI. No public repository either, so what it does is read from its own README rather than checked against source.
CLI to build, deploy, migrate and validate MDK projects
Specific to MDK metadata projects — nothing here builds or deploys a CAP service or a plain Fiori app. Closed-source, under SAP's own developer licence rather than a public repository.
Boolean and string flags read by applications at runtime
Calls an application endpoint on a schedule and logs each run
Log fetcher and parser for one Cloud Foundry app
Merged log tail of every started app in a Cloud Foundry space
Collects Cloud Foundry or Kyma logs into a searchable Kibana
OpenSearch-based store for logs, metrics and traces
Registers a multitenant application for subaccount subscriptions
Scales Cloud Foundry app instances by policy rules and schedules
Publishing and subscribing to alerts about BTP resources and apps
Runs operations commands on BTP by hand, schedule or event
Metrics, availability checks and alerts for apps in Neo regions
SAP Passport handling for Node.js components
Read-only query tool for metrics in SAP Cloud Logging
Read-only query tool for OpenTelemetry spans in SAP Cloud Logging
Injects the Dynatrace agent into Java applications on SAP BTP
OpenSearch-based store for logs, metrics and traces
Metrics, availability checks and alerts for apps in Neo regions