NewSAP Business Technology Platform, also named SAP Business AI Platform
97 changes
Sat 24
SAP HANA Cloudprovides revisedThe capability was added on 2026-10-24 for administering a database instance; SAP HANA Cloud ships its administration tools, so it is the core answer on BTP.Database connectors
SAP-samples/hana-developer-cli-tool-exampleprovides, serves ecosystems, domain, provides revisedIts performance analysis, privilege grants and backup and recovery commands had no capability to sit under; Database administration was added for them the same day.Database administration
Fri 23
SAP Analytics Cloudlinks revisedSAP moved the What's New entries for SAP Business Data Cloud, SAP Datasphere and SAP Analytics Cloud to the Business Data Cloud feed; the old BTP feed had stopped carrying them.Analytic modelling
SAP Business Data Cloudlinks revisedSAP publishes the What's New entries for SAP Business Data Cloud on its own feed; the entry linked none before.Cataloguing and lineage
SAP Dataspherelinks revisedSAP moved the What's New entries for SAP Business Data Cloud, SAP Datasphere and SAP Analytics Cloud to the Business Data Cloud feed; the old BTP feed had stopped carrying them.Analytic modelling
Sun 18
SAP Developers MCPentry revisedNEIGHBOURS §5.1 named the hosted MCP as a companion to index as an artifact, and the graph had no entry for it. ecosystem: umbrella because its content covers SAP technologies across stacks (llms.txt names ABAP Cloud, CAP, Fiori, HANA Cloud and integration) and no single door holds it. No read_only: the anonymous mounts are read-only, but the signed-in tier writes progress (complete_step). No tool_count: the quickstart and the API page list different tools per mount. The site also serves a GraphQL API, not recorded as an interface here for want of a page read. /mcp/homepage is left out of the description: the quickstart lists it as anonymous and the API page as signed-in.Agent guidance
Sat 17
Access to Generative AI Modelsexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).LLM integration
Agentic CAP: Build MCP servers and enterprise AI agentsexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Serve your application over MCP
AI-native North Star architecture — Platform Layerexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Agent tooling
Architecting Multi-Region HA/DR resiliency patternsexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Deployment
Show 17 more
Building an LLM Agent in CAP Java with Spring AIexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Agent tooling
Building an LLM Agent using CAPexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Agent tooling
Designing Event-Driven Applicationsexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Event Mesh
DevOps with SAP BTPexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Deployment
Document Groundingexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Retrieval-augmented generation
Establish a central entry point with SAP Build Work Zoneexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Launchpad and site content
Establish a central inbox with SAP Task Centerexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Task and approval UIs
Explore your Hyperscaler data with SAP Business Data Cloudexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Cataloguing and lineage
Generative AI on SAP BTPexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).LLM integration
HANA AI Toolkit — Local MCP Serverexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Serve your application over MCP
Integrating and Extending Jouleexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Agent tooling
Medallion Reference Architecture for Big Data Processing in SAP HANA Cloudexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Database connectors
Multitenant SaaS Application using CAPexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Multitenancy
SAP Document AIexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Document extraction
SAP IAM integration with SAP Cloud Identity Servicesexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Authentication
Secure Service Consumption Across Hyperscalersexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Authentication
The fastest way to a deployable CAP app on SAP BTP Cloud Foundryexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Deployment
Thu 15
@sap/approuterprovides[capability:authentication], requires[0] revisedThe UAA sentence was read again in the 23.0.0 README during this pass and was still there.App hosting
@sap/joule-studio-clidescription, provides, links revisedCurrent npm README for 2.0.4, published 2026-10-07, says "Installing
@sap/joule-studio-cli gives you two commands:" and lists joule and jl. SAP Help now installs this package for the new Studio workflow. The historical alpha package stays separately indexed; no unverified rename or lineage relationship is inferred.Agent toolingaicore-skillsprovides revisedcapability:agent-guidance declared the installs_into property on the BTP door, and the README's Installation section names the harnesses in one sentence. The entry's own description already carried the same four; the value puts it where the door's options can be compared on it. Two sentences from the lifecycle skill were read on the same day and added as sources for the edge, since they state how an operation is run and what a mutating script requires.Agent guidance
Cloud Connectorprovides[capability:authentication] revisedThe edge read as though the connector propagated the user by itself. SAP's own page names three authentication types towards an internal system and says the calling application's destination configuration picks one, and that trust to the cloud entities whose tokens are accepted has to be configured explicitly. The property the BTP door compares on rests on the same sentence.RFC connectivity
Show 9 more
Cloud Identity Servicesprovides[capability:authentication] revisedThe only sentence about this service was its one-liner, so the capability page listed it beside the OAuth server with nothing to tell the two apart. SAP's trust and federation page states what the service is and what a tenant's own policies cover, and the default identity provider page states the corporate identity provider behind it, which is the property the BTP door now compares on.Authentication
Joule Studioecosystem, artifact type, links revisedThe browser builder and managed runtime do not establish a separately subscribed and bound BTP service. Keep CAP and BTP as served views: the product overview names CAP development, and the current SAP Help tutorial requires "An SAP S/4HANA system configured with an SAP BTP destination." The architecture chapter is titled "Building AI Agents with SAP Joule Studio on SAP BTP" while distinguishing the SAP-managed runtime from Bring Your Own Agent in a customer subaccount. The CLI link is backed by the current npm README, which now ships both joule and jl; its atlas record is revised in the same batch. The positive basis for web-tool is SAP’s description of a visual browser-based builder with no local setup. It identifies the hosted development interface, including provisioned access; it does not classify the runtime as an unbound or customer-hosted service.Agent tooling
Joule Workecosystem, artifact type, ecosystem revisedThe three-record acceptance on 2026-10-15 established the workspace as a separate part of SAP Joule. Retain that family split: SAP Joule records the BTP formation and identity integration, while Work records the user-facing experience across systems. RA0029 says "The experience is available across web, desktop and mobile"; there is no separate BTP subscription or binding documented for Work. Its BTP served view describes interaction with customer-managed agents connected to Joule, not a BTP runtime or core-coverage claim.Agent workspaces
OAuth 2.0 on SAP BTPlifecycle, provides[capability:authentication] revisedThe BTP door now compares its authentication options on whether a token can be had with no person present. The catalogue sentence about the client credentials grant states it for this service, and it was read again on this date.Authentication
SAP Authorization and Trust Management serviceprovides[capability:authentication] revisedThe edge said only that the service answers authentication, so the page could not say which part of the concern it answers. SAP's architecture page states the three: the trust, the assertion it receives, and the token it signs. The two properties the BTP door now compares options on are stated from the same page: a token with no user present, and a corporate identity provider behind it.Authentication
SAP-samples/html5-applications-migration-skills-for-sap-btpprovides, description revisedThe entry said the plugin needs no network access, which the README states, and said nothing about the four command lines the same README requires before anything is built or deployed. A reader who stopped at the first half would take the migration for the whole job. The cleanup skill's own sentence, which undeploys from Cloud Foundry, is added as a source on the edge beside it, because the two statements sit in one README and both are true of different steps.Agent guidance
SAP-samples/joule-a2a-agent-toolkitprovides, description revisedThe entry said the skills generate commands, which the README states of btp-cli, cf-cli and joule-cli, and said nothing about
/sap-a2a-agent-toolkit:deploy-agent, which the Quick Start uses to deploy the scaffolded agent. The distinction decides whether anything here reaches an account, so it is now on the entry, and the README's own cf login and joule login step is named in the warning where the account conditions already were.Agent guidanceSAP/automation-pilot-agent-skillsprovides, description revisedThe README read on 2026-10-15 lists
curl and jq in the same prerequisites table as Claude Code, for the API calls and the JSON parsing, and the entry named neither. The two API sentences read the same day are added as sources on the edge, since what the skills do through the Content Management and Executions APIs was described in the entry without a quote behind it.Agent guidanceSAP/leanix-ai-pluginsprovides, requires revisedThe edge rested on one phrase, "designed to work with the LeanIX MCP Server", which says the skills are written for it but not that a reader has to do anything. The sentence read on 2026-10-15 states the connection and the sign-in flow, which is what makes the requirement concrete.Agent guidance
Mon 12
API Managementprovides[mcp-servers], provides, description revisedIndependent source review supports prompts guiding agent interaction rather than templates; retains both sourced tool-count limits as an explicit MCP-specific discrepancy.Rate limiting
Fri 9
AI-native North Star architecture — Platform Layerparts revisedFilled from SAP's own pages at the maintainer's request (docs/concepts/product-doors.md was the occasion; the AI-native door reads these designs). Every part names what the graph holds; what it lacks is listed as candidates in the curation note.Agent tooling
aicore-skillsdescription revisedThe SAP AI Skills Library registry snapshot of 2026-10-09 lists a fourth skill under plugins/aicore-skills, genai-hub-tabular-orchestration, and plugin.json names four skill directories where the entry of 2026-09-25 described three. Read from that skill's own SKILL.md and plugin.json: the Context Registry layers, the sap-rpt tabular prediction models and the BTP command line it wants for HDL access are added, and the sentence about the DO NOT USE FOR clauses is corrected, because the new skill sends what it declines to genai-hub-orchestration, which plugin.json does not list.Agent guidance
Generative AI on SAP BTPparts, roles, paths revisedThe readme names the place for plugins and SDKs by example and leaves it open, and the RAG page names SAP's standardized services or a custom-built approach as the choice (docs/concepts/design-roles-and-interfaces.md §3). The three scenario pages are overlapping flows over the same parts, so they are not ways; the two runtimes are.LLM integration
Integrating and Extending Jouleparts revisedFilled from SAP's own readmes at the maintainer's request; the AI-native door reads these designs. Every part names what the graph holds; what it lacks is listed as candidates in the curation note.Agent tooling
Show 3 more
MCP Server for SAP BTP Administrationprovides revisedThe concern it answers is reaching into an SAP system from outside, split out of MCP servers on this day; the sentence on the edge is unchanged.Agent access to your systems
SAP LeanIX MCP Serverprovides revisedThe concern it answers is reaching into an SAP system from outside, split out of MCP servers on this day; the sentence on the edge is unchanged.Agent access to your systems
sap-tutorials-contententry revisedA repository the SAP AI Skills Library collection cache carries as processedBy baseline-2026-09-18 and that was never drafted into the atlas, so the changed registry record of 2026-10-09 is the first occasion to enter it; first_seen keeps the baseline date and no revises flag applies, since there is no published entry to revise. One of the three skills the repository registers: the other two name no SAP stack and stay out. Written from the skill's own SKILL.md and GitHub's record for the repository and the sap-tutorials organisation, which GitHub marks verified with the email sapdocs@sap.com and the tutorial navigator as its site. Hard rule 7: skills are indexed, never authored here.Agent guidance
Tue 29
sap-fiori-iosentry revisedRead out of the SAP AI Skills Library repository, which the atlas holds as source:sap-ai-skills-library rather than as an artifact because the registry keeps other people's code in their own repositories. This skill is SAP's own code in that repository, so it is entered from its SKILL.md, README and references directory, as plugins/aicore-skills was on 2026-09-25. The BTP door is where the atlas answers native iOS work (capability:mobile-apps names the SAP BTP SDK for iOS), and capability:agent-guidance exists on that door. Hard rule 7: skills are indexed, never authored here.Agent guidance
Sun 27
API Compositionentry revisedAn impact assessment of CostingGeek/sap-mcp found the API the whole entry rests on had no node: the prose named SAP Graph and nothing pointed at it. Written from SAP's own API Composition documentation in SAP-docs/btp-integration-suite, pinned at commit 33f3395. No provides edge yet — the capabilities the atlas holds for serving OData and GraphQL are scoped to the CAP and ABAP doors and describe serving your own model, which is a different concern from composing several systems' APIs; whether this answers an existing capability or needs one is an editorial call.
Cloud Integrationprovides[integration-flows] revisedThe option states the protocols its adapters speak, one sentence per value, from SAP Help's introduction page: its transport-channel sentence and its adapter table, which names each of the others one adapter at a time (docs/concepts/design-roles-and-interfaces.md, P2). JMS is an adapter name there and no sentence names it as a protocol, so it stays out.Integration flows
Designing Event-Driven Applicationsparts, areas, edges, explains revisedThe record states what its source draws around and between the parts (docs/concepts/reference-architectures.md §9.2): SAP cloud applications, SAP BTP and the third-party landscape as areas, the extension application the readme's flow names, and the event flow from an SAP cloud application to the hub and from a third-party broker over the bridge to SAP's event services. The checker's reading of the first draft: the bridge's SAP end now rests on the two sentences that name advanced event mesh and the Event Mesh capability as SAP's event brokers; SAP BTP is a zone of SAP's cloud, since the readme names no subaccount, and the two capabilities stand beside Integration Suite rather than within it; and the piece no longer explains async-processing, which is in-process work its own summary sets aside.Event Mesh
MCP Server for SAP BTP Administrationprovides revisedSAP's page says the server manages the BTP account structure, which is what account provisioning is; the only edge was to the MCP-server capability, so the account-provisioning page did not list it.Agent access to your systems
Show 4 more
Multitenant SaaS Application using CAPparts, areas, edges revisedThe record states what its source draws around and between the parts (docs/concepts/reference-architectures.md §9.2): the provider and consumer subaccounts, the users and API clients, and the flow of subscription, data and authentication as the architecture page states it. On the checker's reading of the first draft: only the application is placed in the provider subaccount, since the page places nothing else there; the registration with the SaaS Provisioning service is the stated direction, not events the service raises; and API Management's policies are stated with no path, so no arrow.Multitenancy
SAP Cloud Management Service for SAP BTPinterfaces revisedSAP's page on account administration through this service's APIs names the four and says they are included in the core services for SAP BTP; the hub's catalogue states each one's title, version and state (docs/concepts/design-roles-and-interfaces.md §3.2, P7). What an application reaches this service over is then a named surface with a page. No status is entered: the hub's state is a crawled claim reported beside the interface.Account provisioning
SAP Document AIinterfaces revisedAn interface may be named and stays a field (docs/concepts/design-roles-and-interfaces.md §3.2, P7): the hub's catalogue states the two APIs' titles, versions and states, and SAP's Help pages name the channels and the workspace, so a design's arrow can say which surface it lands on and a reader has the page to open. The inbound channels read mail: SAP's Help page names mail as the only channel type, so the SharePoint folders the reference architecture mentions are its claim and not the maker's. No status is entered: the hub's state is a crawled claim reported beside the interface.Document extraction
SAP Document AIparts, areas, edges, roles, edges[client to docai] revisedThe ingestion page links the upload operation of document_information_extraction_api_v2 as the API-based integration, and the service now names that surface (docs/concepts/design-roles-and-interfaces.md §3.2, P7), so the arrow says which API it lands on and wears its protocol.Document extraction
Fri 25
aicore-skillsentry revisedRead out of the SAP AI Skills Library repository, which the atlas holds as source:sap-ai-skills-library rather than as an artifact. The plugin was added there on 2026-09-21 and the registry front end at skills.cloud.sap had not listed it when the registry was crawled on 2026-09-25, so it is entered from its own plugin.json, README and three SKILL.md files. Hard rule 7: skills are indexed, never authored here.Agent guidance
Tue 22
SAP Authorization and Trust Management serviceconnects[0] revisedThe second reader read the connects batch of 2026-09-19 on 2026-09-22, after its acceptance, and found: neither quote names this service, and only one names Cloud Identity Services, so the page's title, which names both parties, is quoted beside them.Authentication
SAP Build Work Zone, advanced editionbundles revisedSAP's Discovery Center lists these among the plan's included services, and npm run check:catalogue listed the relation with no edge. An entitlement and not a dependency: a bundles edge, read by the commercial perspective (vocab PERSPECTIVES, 2026-09-22), listed and never drawn. Mobile Services and UI theme designer are listed too and have no entry.Launchpad and site content
SAP Build Work Zone, standard editionbundles revisedSAP's Discovery Center lists these among the plan's included services, and npm run check:catalogue listed the relation with no edge. An entitlement and not a dependency: a bundles edge, read by the commercial perspective (vocab PERSPECTIVES, 2026-09-22), listed and never drawn. Mobile Services and UI theme designer are listed too and have no entry.Launchpad and site content
SAP Integration Suitebundles revisedSAP's Discovery Center lists these among the plan's included services, and npm run check:catalogue listed the relation with no edge. An entitlement and not a dependency: a bundles edge, read by the commercial perspective (vocab PERSPECTIVES, 2026-09-22), listed and never drawn.
Show 2 more
SAP Private Link Servicerequires revisedSAP's Discovery Center lists the runtime as a required service of the plan, and npm run check:catalogue listed the relation with no edge. Basis entitlement: the catalogue says a plan cannot be bought without it, which is commercial and is not drawn as a runtime dependency (vocab PERSPECTIVES, 2026-09-22).Destinations
SAP Task Centerrequires revisedSAP's Discovery Center lists both Work Zone editions as required services of the all-tasks plan, and npm run check:catalogue listed the relations with no edge. Basis entitlement and conditional: the plan's own description says either edition serves (vocab PERSPECTIVES, 2026-09-22).Task and approval UIs
Sun 20
API Managementprovides revisedMoved here from SAP Integration Suite. SAP files MCP Server under API Management in its documentation, and every creation path read lists the activated API Management capability as a prerequisite.Rate limiting
Cloud Integrationconnects revisedThe use case for receiving Kafka messages lists the Kafka sender adapter as a documented contribution, and the graph held no edge from Cloud Integration to Kafka. From SAP's adapter pages, which name the Kafka protocol and, in the adapter's General tab, TCP as its transport.Integration flows
SAP Integration Suiteprovides revisedMoved to API Management, the part SAP's documentation names as doing it. An edge sits on the smallest thing the documentation names.
SAP Integration Suite, advanced event meshpart of, connects revisedThe use case for receiving Kafka messages lists the Kafka bridge as a documented contribution, and the graph held no edge from the broker to Kafka, so a generated diagram could not draw the path. From SAP's Kafka bridging pages; no protocol is entered because neither page names one.Event Mesh
Sat 19
@sap/approuterconnects revisedThe router's five service bindings said that it needs each service and not how it talks to it. Each is now also a connection, with what the README states about it and nothing it does not: OAuth2 is named for the UAA and for no other.App hosting
Cloud Connectorconnects revisedThe Connectivity service required the Cloud Connector, and nothing said which of the two opens the connection. SAP's documentation does: the connector registers with the service.RFC connectivity
SAP Authorization and Trust Management serviceconnects revisedThe two security services had no edge between them, although most BTP diagrams draw one. SAP's administration guide states the trust and the protocol it is established with.Authentication
SAP Cloud Identity Services - Identity Provisioningpart of revisedSAP's catalogue names Identity Provisioning as one of the services SAP Cloud Identity Services include. The first
part_of on an artifact.Identity provisioningThu 17
Object Store on SAP BTPprovides revisedPlace the service under its direct job of object storage. CAP attachment integration remains represented by existing dependency edges from the attachment plugins.Object storage
SAP Document Management service, integration optionserves ecosystems revisedAdd CAP to served ecosystems from documented CAP integration; preserve the existing BTP/UI5 contribution and source dates. CAP plugin restrictions do not apply to the service itself.Attachments
Wed 16
@sap/artifact-managemententry revisedplace.mjs scaffolds a stub with guessed defaults; this fills it in from the package's own record.Deployment and operator
@sap/mdk-toolsentry revisedplace.mjs scaffolds a stub with guessed defaults; this fills it in from the package's own record.Deployment and operator
Tue 15
@sap/approuterrequires, alternative to revisedSAP's own Application Frontend service page names the HTML5 Application Repository and the application router as what to stay on where those meet your needs better, and the service entry already carries the edge to the repository.App hosting
SAP Connectivity servicerequires revisedThe Cloud Connector entered in intake-20260915-cloud-connector; the service's description already named it in plain words.RFC connectivity
Mon 14
Generative AI on SAP BTPcapability revisedThe capability moved to a neutral id when it opened to HANA, BTP and ABAP; the concern and this entry's edge to it are unchanged.LLM integration
SAP HANA Cloudprovides revisedRAG on CDS reads that HANA Cloud supplies the vector column and the similarity function, and the capability opened to the BTP door on 2026-09-14, yet the service carried no edge to it; the store the CAP-door pipelines write into is now an option on the capability.Database connectors
Thu 10
Cloud Identity Servicesserves ecosystems revisedABAP authorisation is authorisation objects and roles, a different concern that an identity service does not answer, and on UI5 token validation happens in the router or the service rather than in the frontend. Listed behind both doors, it grouped under nothing on either.Authentication
PostgreSQL on SAP BTP, hyperscaler optionprovides revisedEntered with a delivers edge and no provides, so it was behind the BTP door with nothing to group under. database-connectors gained the BTP door the same day.Database connectors
SAP Analytics Cloudentry, serves ecosystems revisedAdded by me the day it was entered, and it did not hold: the data and analytics capabilities are on the BTP door only, so on CAP this was counted behind the door and grouped under nothing. A CAP service reaches it through a destination, which is the BTP door's concern.Analytic modelling
SAP Authorization and Trust Management serviceserves ecosystems revisedThe same as Cloud Identity Services: ABAP's authorisation model is not XSUAA's, and a UI5 frontend does not validate the JWT — the router and the service do.Authentication
Show 5 more
SAP Business Data Cloudentry revisedEntered so the data and analytics capabilities have SAP's answer as an artifact rather than as a paragraph with a citation — the asymmetry every one of those three coverage notes admitted to. Written from SAP Help, read today, which is what the checked date means.Cataloguing and lineage
SAP Connectivity serviceserves ecosystems revisedIt provides RFC connectivity, a CAP-side concern; a UI5 frontend reaches a backend through its router, not through the Connectivity service.RFC connectivity
SAP Datasphereentry, serves ecosystems revisedAdded by me the day it was entered, and it did not hold: the data and analytics capabilities are on the BTP door only, so on CAP this was counted behind the door and grouped under nothing. A CAP service reaches it through a destination, which is the BTP door's concern.Analytic modelling
SAP Destination serviceserves ecosystems revisedThe destination is resolved by the router or the service, not by UI5 code, so the decision is made on the CAP and BTP doors.Destinations
SAP HANA Cloudentry, serves ecosystems revisedAdded by me the day it was entered, and it did not hold: an ABAP developer does not choose the database — S/4 runs on HANA — so database-connectors is not a decision made on the ABAP door.Database connectors
Wed 9
@sap/mdk-mcp-serverentry revisedEntered from the sap-ai-mcp-servers catalogue, which is credited as the source; the description is written from the project's own README and documentation rather than from the catalogue's line about it.Agent access to your code
MCP Server for SAP BTP Administrationentry revisedEntered from the sap-ai-mcp-servers catalogue, which is credited as the source; the description is written from the project's own README and documentation rather than from the catalogue's line about it.Agent access to your systems
SAP Application Frontend serviceentry revised@sap/appfront-cli was in the corpus and the service it drives was not, so the BTP door listed a CLI with nothing behind it. SAP's own page names the HTML5 Application Repository as the thing to stay on where it fits better, which is why the two carry an alternative_to edge rather than one quietly superseding the other.App hosting
SAP LeanIX MCP Serverentry revisedEntered from the sap-ai-mcp-servers catalogue, which is credited as the source; the description is written from the project's own README and documentation rather than from the catalogue's line about it. Classified btp because the ecosystem list has no door for enterprise architecture and hard rule 9 allows only one; the strain is recorded here rather than hidden in the choice.Agent access to your systems
Show 3 more
SAP-samples/joule-a2a-agent-toolkitentry revisedEntered from the sap-ai-mcp-servers catalogue, which is credited as the source; written from the repository's own README rather than from the catalogue's line about it. Hard rule 7: skills are indexed, never authored here.Agent guidance
SAP/automation-pilot-agent-skillsentry revisedEntered from the sap-ai-mcp-servers catalogue, which is credited as the source; written from the repository's own README rather than from the catalogue's line about it. Hard rule 7: skills are indexed, never authored here.Agent guidance
SAP/leanix-ai-pluginsentry revisedEntered from the sap-ai-mcp-servers catalogue, which is credited as the source; written from the repository's own README rather than from the catalogue's line about it. Hard rule 7: skills are indexed, never authored here. Filed under btp for the same reason its MCP server is: hard rule 9 allows one ecosystem and there is no door for enterprise architecture.Agent guidance
Mon 6
API CompositionchangedSearching the current documentation for Graph, and reading a page that says Graph as a page about something else. Nothing about the behaviour moved, so a source using the old name is out of date on the name alone and predates 2026-07-06.