NewSAP Business Technology Platform, also named SAP Business AI Platform
Origin Community

Today
1 change
BASEnvSyncadded to the atlasCarries home-directory dotfiles from one BAS dev space to anotherIDE extension,
Sat 24
1 change
btp-agentadded to the atlasLangGraph agent and UI5 chat screen over four BTP MCP serversSample,
Fri 23
3 changes
BTP MCP Serverserves ecosystems revisedThe tag came in with the entry on 2026-09-10 and nothing sourced it: the README names BTP Core Services and the proxy it runs on, never CAP. It read as a routing leftover from when the MCP servers capability lived on the CAP door; the entry stays on BTP, its home.MCP server,
hana-mcp-serverserves ecosystems revisedThe tag came in with the entry on 2026-09-10 and nothing sourced it: the README names HANA and no CAP stack. Removed with the other unsourced tags from that sweep; the entry stays on BTP, its home.MCP server,
odata-mcp-proxyserves ecosystems revisedThe tag came in with the entry on 2026-09-10 and nothing sourced it: the README describes a config-driven proxy on BTP Cloud Foundry and names no CAP stack. Removed with its sibling configs; the entry stays on BTP, its home.MCP server,
Thu 22
1 change
scecadded to the atlasDocker Compose IoT edge stack that connects to SAP BTPSample,
Mon 19
3 changes
Building Code-Based AI Agents on the BAIPpublishedA Devtoberfest 2026 session on writing the agent yourself rather than configuring one, which is the agent tooling edge: an agent is a model with tools, skills, memory and context around it, and the session reads the code of one built in CAP as a LangGraph state graph, with an agent node that calls the model, a tools node holding the MCP clients, and the edge between them looping until no tool is needed. It then shows the shorter route, a CDS service annotated for the agent protocol with its instructions and skills in an agent.md file. SAP AI Core carries both, with the CAP service in front of it as middleware so the credentials never reach the browser, and that is what cap-agent-ui5-webui is demonstrated against: added as a dependency, it gives the annotated service a UI5 chat interface that can be deployed rather than only previewed. A Python multi-agent application on Cloud Foundry, where an orchestrator delegates to per-stack specialists so no single model sees every tool, closes the session.Talk,
@marianfoo/sap-mcp-authdescription, type properties, connects revisedRe-read against the README as it stands today. "No token endpoint" and "there is no client-credentials flow to use instead" were absence claims about SAP's portals that no source makes, so they are gone and the paragraph now says what the module does and whom it serves. The maintainer's own unofficial caveat, and the origins password login refuses, are in when_not_to_use. The package block states that it is imported into the caller's own program and installed from npm. The README names Cloud Identity Services as the tenant the login goes to, which is an edge rather than a phrase in a paragraph.Package,
secondsky/sap-skillstype properties, flavors revisedRead today in the two plugins that answer the CAP and the UI5 door, which the ABAP pass had not opened. The sap-cap-capire skill's frontmatter states that it covers Node.js and Java runtimes, so CAP's two flavors rest on the maintainer's sentence where the entry previously answered in both by the serves-another-door fallback, which is the same reading off an absence. The sapui5 skill's frontmatter names freestyle apps and Fiori elements apps in one clause, so freestyle is stated, and fiori-elements moves onto that sentence from the README line about which request activates sap-fiori-tools, which said what triggers a plugin rather than what it covers. Nothing read names UI5 Web Components, so that flavor stays unstated. Stating freestyle changes an answer: the entry answered no there while it stated one UI5 flavor and now answers yes, which a reader comparing that flavor's options will see. The ABAP pair is unchanged.Skill,
Sun 18
1 change
Modernization Agents for SAP on AWSadded to the atlasAWS agents for ABAP, PI/PO and BW modernisation workApp,
Sat 17
16 changes
abap2UI5 mobile shelladded to the atlasNative iOS and Android shell for one abap2UI5 endpointDesktop app,
Agentic AI on BTP: a Multi‑Agent App with Pydantic 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).Blog,
Agentic AI on BTP: a Single Agent with LangGraphexplains 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).Blog,
BTP Audit Log MCP Server: Security Monitoring with AI Assistantsexplains 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).Blog,
Show 12 more
BTP Cloud Foundry MCP Server: Managing CF Environments with 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).Blog,
CAP multitenancy with Work Zoneexplains 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).Blog,
Extend Upload Set to Fiori Elements and utilize Document Management Serviceexplains 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).Blog,
Extend Upload Set with Table to Fiori Elements and utilize Object Storeexplains 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).Blog,
Hey ABAP Cloud please let me save my data export to Azure Storage please🥺🙏- part 4explains 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).Blog,
Nice patch SAP! Revisiting your SAP BTP security measures after AI Core vulnerability fixexplains 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).Blog,
Perform SAP Principal Propagation with Microsoft Entra ID for SAP SuccessFactors!explains 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).Blog,
Sharing SAP HANA Cloud instance to multiple subaccounts and creating HDI containersexplains 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).Blog,
Testing SAP Build Process Automation task UI in SAP Business Application Studioexplains 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).Blog,
Tips for running CAP nodejs in 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).Blog,
UI for the BTP Application Vulnerability Reportexplains 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).Blog,
Understanding and Developing Fiori Plugins with Extension API & TypeScriptexplains 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).Blog,
Thu 15
25 changes
@saptools/brunoadded to the atlasRunner for Bruno collections against XSUAA-protected CF appsCLI,
@saptools/cf-debuggeradded to the atlasNode.js inspector tunnel over cf ssh to Cloud Foundry appsCLI,
@saptools/cf-exploreradded to the atlasFile search in apps deployed to SAP BTP Cloud Foundry over cf sshCLI,
@saptools/cf-function-traceadded to the atlasStep-by-step state recorder for one JavaScript function in Node.jsCLI,
Show 21 more
@saptools/cf-hanaadded to the atlasSQL runner against the SAP HANA Cloud database bound to a CF appCLI,
@saptools/cf-inspectoradded to the atlasShell debugger for remote Node.js over the Chrome DevTools ProtocolCLI,
@saptools/cf-live-traceadded to the atlasHTTP trace hook streaming a running CF Node.js app's trafficCLI,
@saptools/cf-logsadded to the atlasLog fetcher and parser for one Cloud Foundry appCLI,
@saptools/cf-metricsadded to the atlasRead-only query tool for metrics in SAP Cloud LoggingCLI,
@saptools/cf-oteladded to the atlasRead-only query tool for OpenTelemetry spans in SAP Cloud LoggingCLI,
@saptools/cf-syncadded to the atlasCloud Foundry topology cache for the other @saptools packagesCLI,
@saptools/cf-tailadded to the atlasMerged log tail of every started app in a Cloud Foundry spaceCLI,
@saptools/cf-xsuaaadded to the atlasOAuth2 token fetcher for a Cloud Foundry app's XSUAA bindingCLI,
@saptools/sqltoolsadded to the atlasSQLTools connection from a Cloud Foundry app's HANA bindingCLI,
cap-reuse-html5added to the atlasFiori elements app in the HTML5 Application Repository with cdm.jsonSample,
@arc-mcp/xsuaa-authprovides[capability:authentication] revisedThe BTP door now compares its authentication options on whether the signed-in identity reaches the next system. The README's sentence about the ./btp entrypoint states it for this package, and it was read again on this date.Package,
@saptools/cf-xsuaaprovides[capability:authentication] revisedOn a capability page the edge put a token command line beside an OAuth server and an identity provider with nothing to tell them apart. The edge now says which part of the concern it answers, that it validates nothing, and states the property the BTP door compares on: a token with no user present.CLI,
abap-skillsprovides revisedcapability:agent-guidance widened installs_into to the ABAP door. The README read on 2026-10-15 names the five clients the skills command line supports and adds "and other compatible agents", so the five named ones are the value; the README also documents separate routes for Claude Code, OpenCode and GitHub Copilot in VS Code, which name no client the sentence does not. system_reach is left out: the repository states nothing about needing a system or bringing one, and absent is not a no.Skill,
btp-solution-diagram-generatorprovides revisedThe edge said the rules are packaged and not what the package holds, which is the thing that separates this option from the other three skill sets behind the door that carry the same guideline. The README's own list was read on 2026-10-15 and its three lines are now the edge's sources.Skill,
DanKromp/skillOverflowprovides revisedThe entry's own prose said the collection covers UI5 and Fiori work and the edge cited only the total count. The UI5 pass needed to know what that coverage is, because this entry states no flavor and so answers in all of a door's flavors; the two rows name the skills the fallback rests on, which is what the capability's freestyle and web-components readings now cite.Skill,
drawio-skill-sapprovides, description revisedThe entry carried the one-line install command and not the path the README's own first option uses, which is what a reader on Copilot needs.Skill,
SAP Power for Kiroprovides, description revisedThe entry said it is packaged as a Kiro power and not how it gets there or which Kiro it needs; the README read on 2026-10-15 states both.Skill,
sap-architectureprovides, description revisedThe entry said other agents can run it and not what that costs. The README's own caveat, read on 2026-10-15, is that the auto-load is Claude's alone, which is the difference between this option and a Claude-only one.Skill,
sap-cloud-integration-pipeline-assistantprovides revisedcapability:agent-guidance declared the installs_into property on the BTP door. The README names GitHub Copilot agent mode in its install step and gives a .claude/skills/ path beside it under the heading "For Claude", which names a product family rather than one of the property's values, so only Copilot is entered and the Claude line is kept as a source on the edge.Skill,
secondsky/sap-skillslinks, flavors, requires, provides, description revisedThe same correction as description.what_it_solves, on the edge that carries this artifact's answer to the capability, so the two do not state the repository's evidence model differently. The rewording also removes the two em dashes the prose scan reported in this field.Skill,
Wed 14
1 change
midasol/sap-mcp-serverdescription revisedThe whole paragraph was the policy, which Agent access to your systems carries as a condition sourced to the policy.MCP server,
Tue 13
1 change
Nice patch SAP! Revisiting your SAP BTP security measures after AI Core vulnerability fixpublishedWritten after the SAPwned disclosure in SAP AI Core, it argues SAP BTP's shared-responsibility model still requires the customer's own hardening: scope SAP BTP, Cloud Foundry Runtime and SAP BTP, Kyma runtime app access, rotate OAuth2 client-credentials secrets, and enforce MFA and Conditional Access through a corporate identity provider rather than relying on SAP's patch alone. It then explains how the SAP Audit Log service writes standardized events for most Cloud Foundry BTP services, and walks through onboarding a BTP subaccount into Microsoft Sentinel for SAP BTP to query those logs with Kusto and build detection rules that flag unexpected login countries or known-bad IPs and trigger automatic user blocks.Blog,
Mon 12
1 change
Microsoft Sentinel for SAP goes agentlesspublishedExplains how Microsoft Sentinel for SAP's new agentless data connector drops its Docker-based collector agent by reusing an existing SAP Cloud Connector setup together with SAP Integration Suite: on SAP NetWeaver 750 and later, a small set of RFC function modules must be reachable from Integration Suite, added as an RFC connection in the subaccount's Destinations maintenance view, with a user authorised to call them (RFC connectivity). It also covers calling the audit log API remotely, which on older releases needs SAP note 3054326 and a different integration-package configuration.Blog,
Sun 11
2 changes
calmcpadded to the atlasMCP server with read tools over the SAP Cloud ALM APIsMCP server,
calmcpentry revisedThe repository was handed over directly. Written from the README, the repository's own record and the product page at consetto.com. Filed on the BTP door because Cloud ALM has no door of its own and the server deploys to Cloud Foundry, binds XSUAA and resolves a destination there, the same strain recorded on cloud-alm-itsm-mcp. origin_ring is independent because the product page states it: "calmcp is an independent open-source project."MCP server,
Fri 9
31 changes
sap-cloud-integration-pipeline-assistantadded to the atlasAgent skill for the Pipeline Concept in SAP Cloud IntegrationSkill,
sap-cx-developer-companionadded to the atlasAgent skill for SAP Customer Experience APIs, CDS and errorsSkill,
sap-mdk-appsadded to the atlasAgent skill for Mobile Development Kit projectsSkill,
@mariodefe/sap-datasphere-mcpprovides 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.MCP server,
Show 27 more
abap-skillsentry 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. Written from the repository's README, its SKILLS_INDEX.md, the skills directory listing and the abap-cloud SKILL.md; hard rule 7: skills are indexed, never authored here.Skill,
AI Core 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.MCP server,
BTP CF 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.MCP server,
BTP 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.MCP server,
btp-sap-odata-to-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.MCP server,
CI 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.MCP server,
cloud-alm-itsm-mcpprovides 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.MCP server,
CostingGeek/sap-mcpprovides 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.MCP server,
cpi-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.MCP server,
drawio-skill-sapentry 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. Written from the repository's README, its LICENSE and the skill's own SKILL.md; hard rule 7: skills are indexed, never authored here. It is a fourth independent BTP diagram skill beside marianfoo-btp-drawio-skill, lemaiwo-btp-drawio-skill and miyasuta-claude-drawio-btp-diagram, and GitHub reports it as not a fork of any of them.Skill,
hana-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.MCP server,
mcp-integration-suiteprovides 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.MCP server,
mcp-is-tpmprovides 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.MCP server,
mcp-sap-cpiprovides 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.MCP server,
mcp-sap-datasphere-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.MCP server,
mcp-sap-focusedrunprovides 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.MCP server,
midasol/sap-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.MCP server,
odata_mcpprovides 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.MCP server,
odata_mcp_goprovides 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.MCP server,
odata-mcp-proxyprovides 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.MCP server,
sap_analytics_cloud_mcpprovides 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.MCP server,
sap-bdc-mcpprovides 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.MCP server,
sap-bdc-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.MCP server,
sap-cloud-integration-pipeline-assistantentry revisedA new repository in the SAP AI Skills Library registry snapshot of 2026-10-09, registering one skill at skills/sap-cloud-integration-pipeline-assistant; the repository documents the same skill under .github/skills/ and .claude/skills/, which is where a reader copies it from. Written from the repository's own README; hard rule 7: skills are indexed, never authored here.Skill,
sap-cx-developer-companionentry revisedA new repository in the SAP AI Skills Library registry snapshot of 2026-10-09, registering one skill at skills/sap-cx-developer-companion. Written from the repository's own README and SKILL.md; hard rule 7: skills are indexed, never authored here. Placed behind the SAP Commerce door because the CX API explorer and the error resolver are written against Commerce Cloud OCC and Sales and Service Cloud, with CAP and BTP as served doors for the CDS half.Skill,
sap-mdk-appsentry revisedA repository new to the SAP AI Skills Library registry snapshot of 2026-10-09, with no prior processed record in the collection cache, registering one skill at skills/sap-mdk-apps. Written from the repository's README and that skill's own SKILL.md; hard rule 7: skills are indexed, never authored here. Placed behind the BTP door, where the atlas already holds @sap/mdk-tools and @sap/mdk-mcp-server.Skill,
sap-pi-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.MCP server,
Thu 8
4 changes
auth-transportadded to the atlasUI5 app and CAP service copying role collections between subaccountsApp,
auth-transport2added to the atlasMTA projects sharing a role collection across role templatesSample,
btp-ui5-show-userinfoadded to the atlasUI5 app reading the signed-in user via launchpad and approuterSample,
btp-user-role-requestadded to the atlasFiles for two Japanese posts on BTP user registration with SAP BuildSample,
Tue 6
1 change
sap-ai-dev-toolkitdescription, provides, requires, connects, type properties revisedRe-read against the README, tools.md and inventory.md at 0.9.3, published the same day; the entry was written on 2026-10-01 against 0.7.9, and npm records 41 releases in the eleven days since 0.2.5. Three cited sentences no longer exist in the source: the feature row now reads "Discover BAS destinations or local SAP GUI systems", the architecture flow now names "VSP + configured route (BAS, CF, or local SAP GUI)", and the row quoted for authentication ("No credentials in mcp.json") has become "Credential-aware setup", which states the BAS and local halves separately. So Business Application Studio is now a conditional requirement rather than an unconditional one, and the single destination authentication mode is joined by the local ones the README documents. The fourteen facets, the curated ADT surface and every other guardrail quote were re-verified unchanged.MCP server,
Thu 1
2 changes
sap-ai-dev-toolkitadded to the atlasMCP proxy pinning an agent's ABAP tools to one SAP systemMCP server,
sap-ai-dev-toolkitentry revisedDrafted from the repository's own README and LICENSE after the URL was handed over directly. Typed as an MCP server because what it gives an agent is a generated stdio entry per BAS destination; the setup command and the HANA inspector ship in the same package.MCP server,

Tue 29
5 changes
Agentic AI on BTP: a Multi‑Agent App with Pydantic AIpublishedSplits a single CAP/TypeScript agent that had grown to juggle five BTP MCP servers behind one bloated tool list into btp-multiagent-app, a Python and Pydantic AI rewrite where the Cloud Foundry and BTP Core MCP servers each get a dedicated specialist agent, with an audit log specialist scaffolded but left disabled, behind an orchestrator whose only tools are delegation calls to those specialists, which is the agent-tooling pattern the piece works through. Each specialist authenticates to its MCP server over Streamable HTTP with OAuth 2.1, and a shared module centralises the SAP AI Core GenAI Hub model setup behind two credential layouts, one for local runs and one for the Cloud Foundry service binding, the LLM integration side of the rewrite. Tool lists per agent drop from well over a hundred to a dozen or two, and routing failures become separable from tool-misuse failures by reading the trace.Blog,
Agentic AI on BTP: a Single Agent with LangGraphpublishedA CAP TypeScript agent puts a LangGraph StateGraph in front of AzureOpenAiChatClient from @sap-ai-sdk/langchain, reaching SAP AI Core's Generative AI Hub, and lets its tool-calling loop draw on five deployed MCP servers — OData MCP Proxy, CI MCP Server, AI Core MCP Server, BTP MCP Server and BTP CF MCP Server — through @langchain/mcp-adapters' MultiServerMCPClient. Because agent, servers and APIs share one XSUAA tenant, the chat service forwards the signed-in user's own JWT instead of a service account, so each downstream server enforces that user's own authorizations. Past roughly a hundred combined tools the single prompt slows down and stops separating concerns, which is why the author's next post splits it into one specialist agent per MCP server behind an orchestrator.Blog,
BTP Audit Log MCP Server: Security Monitoring with AI AssistantspublishedWouter Lemaire builds an MCP server over SAP BTP's Audit Log Retrieval API using odata-mcp-proxy, with a single entity set and zero custom code, so an AI assistant can answer natural-language questions like "Were there any configuration changes yesterday?" by calling AuditLogRecords_list against a BTP destination authenticated with the Audit Log service's service key. It covers the destination setup, the entity-set configuration that maps the PascalCase entity name to a lowercase auditlogrecords path, and handling the API's 500-record pagination limit.Blog,
sap-knowledge-pipelineadded to the atlasPython library turning OData or HANA records into chunked documentsPackage,
Show 1 more
sap-knowledge-pipelineentry revisedHanded over as a URL. Filed behind the BTP door because what it reads is an SAP OData service and SAP HANA, and neither the library nor its recipes touch CAP, UI5 or ABAP; the repository's own topics are rag, rag-pipeline, sap, sap-btp and sap-hana. One edge, retrieval-augmented generation: the capability's CAP coverage says the layer above the vector, splitting long text into chunks and deciding what goes into the prompt, is hand-written in every entry there, and that layer is what this library is. Data import and export was considered and left off, since that capability is about a file somebody supplies rather than records read out of a live service, and OData is about serving a model as OData rather than consuming one. The optional SAP hdbcli driver is named in the prose and carries no edge: SAP's Node.js driver is the artifact @sap/hana-client, so its Python sibling belongs in the graph the same way and not as an external, which is an editorial decision rather than one for this batch.Package,
Mon 28
2 changes
ARC-DRAWadded to the atlasMCP server drawing BTP solution diagrams on a draw.io canvasMCP server,
ARC-DRAWdescription revisedThe README declares the status early (v0.x), installation from source and testing with Claude Code alone, and the entry carried none of it. The maturity label is the maintainer's own, dated here, and the live-canvas requirement is what separates this option from the ones that write a file.MCP server,
Sun 27
3 changes
Perform SAP Principal Propagation with Microsoft Entra ID for SAP SuccessFactors!publishedWalks through SAP Principal Propagation for SAP SuccessFactors through SAP Integration Suite's API Management, using the OAuth2SAMLBearer flow with Microsoft Entra ID as the external identity provider. Covers the SuccessFactors-specific policy from the SAP Business Accelerator Hub, the API key and company id SuccessFactors uses in place of an OAuth2 client id, and the Entra ID app registration and key value map that exchange an Entra ID token for a SAP-authorized named user, so a consumer such as Power Automate runs under the mapped SAP user rather than a shared technical account.Blog,
BTP MCP Serverprovides revisedThe README lists create, update and delete on subaccounts and directories and entitlement assignment; the only edge was to the MCP-server capability, so the account-provisioning page did not list it.MCP server,
CostingGeek/sap-mcpdescription, connects, type properties revisedRead from the README and from saptools.py, which were the entry's sources from the start and state all three: the Claude Desktop config launches it from a local directory, the server runs on stdio, and the key travels in an apikey header. tool_count is left out — the README enumerates one tool and states no number, and the field rests on a stated count elsewhere in the corpus.MCP server,
The last 30 days. Older changes stay in each entry's history.