NewABAP, RAP and ABAP Cloud
In the last 30 days
133 changes
Today
ABAP Cloud readinesscore coverage revisedReassessed against the graph (check:capabilities): the state changed, so the block now says what the added providers do, as kinds with the defining ones linked.ABAP Cloud readiness
Agent access to your codecoverage by ecosystem, coverage by flavor revisedReassessed against the graph (check:capabilities): removed the tool count and the two absence claims about who has built something.Agent access to your code
Agent evalscore coverage, coverage by ecosystem revisedReassessed against the graph (check:capabilities): albertmink-agentic-abap-evals, an independent set of ABAP tasks and a grader for coding agents, was entered after the block was written; the count is dropped and the second kind named. State unchanged.Agent evals
Agent guidancecoverage by ecosystem, coverage by flavor revisedReassessed against the graph (check:capabilities): docs/WRITING.md §3 rules out provider counts and absence claims in every capability field.Agent guidance
Show 9 more
Change promotioncore coverage, id, ecosystems, name revisedPublic feedback issue #9. The ABAP name is kept in framing_by_ecosystem.abap; the default name and description now state the cross-door concern.Change promotion
Configurationcoverage by ecosystem revisedReassessed against the graph (check:capabilities): config-management arrived as a provider after the block was last looked at; the state stays core-and-community.Configuration
Extensibilitycore coverage revisedReassessed against the graph (check:capabilities): a provider of a second kind, a discovery report for existing enhancement points, arrived after the block was last assessed and the text never named it. State unchanged (core-and-community).Extensibility
Knowing the maintenance status of a releasecore coverage, coverage by ecosystem revisedui5-task-check-eocp, from public feedback issue #6, is the first independent provider on the UI5 door, beside SAP's SAPUI5 version overview.Knowing the maintenance status of a release
LLM integrationcoverage by ecosystem, core coverage, coverage by flavor revisedReassessed against the graph (check:capabilities): the note claimed who provides the capability behind this flavor, which moves with the corpus. The flavor state is unchanged.LLM integration
Loggingcoverage by ecosystem revisedReassessed against the graph (check:capabilities): the state is now community-only and the block needed to say what the community adds.Logging
Retrieval-augmented generationcoverage by ecosystem, core coverage revisedReassessed against the graph (check:capabilities): a CAP-door provider reaches Document Grounding through the LangChain vector store interface, a shape the two plugins do not cover.Retrieval-augmented generation
Telemetrycoverage by ecosystem, coverage by flavor revisedReassessed against the graph (check:capabilities): removes a universal claim about the providers that goes stale as they arrive.Telemetry
Tool governancedescription, core coverage, coverage by ecosystem, framing by ecosystem, coverage by flavor revisedReassessed against the graph (check:capabilities): a count of providers removed.Tool governance
Yesterday
Agent access to your codecoverage by ecosystem revisedRewritten at the maintainer's request (2026-10-25): what SAP ships named whole, and what the community adds written from what its ABAP MCP servers state about how they run, connect and sign in.Agent access to your code
Fri 23
EPOD ADT MCP Serveradded to the atlasMCP server for ABAP on the ADT session, in Eclipse or standaloneAgent access to your code
Thu 22
Klystronadded to the atlasMCP server in ABAP inside the application server, with agent skillsAgent access to your code
Skybuffer AI MCP serveradded to the atlasABAP add-on serving business data and transactions as MCP toolsAgent access to your systems
Mon 19
agentic-abap-evalsadded to the atlasABAP navigation tasks and a grader for coding agentsAgent evals
ABAP Select Converterflavors, description, links revisedThe flavor rests on the page's own "It is primarily used to migrate existing code to ABAP Cloud."; nothing on either page places the tool in standard ABAP. The page's "Additional infos" link was read for the first time and is now links.docs: it states the beta and lists what the converter supports and does not, which replaces the earlier "nothing for a batch of statements", a limit read off what the form does not show. The my-ide-actionsmy-ide-actionsA collection of eight ABAP Development Tools IDE Actions covering class creation, conversion of classic Open SQL to ABAP SQL, code snippets and RAP tooling.independent, abap sentence now follows that repository's own words, "The basis is the SwH tool" and the security table's "SELECT Converter | Software-Heroes API | -> Full SELECT Statement", and calls it an IDE Action rather than a package, which is the type that entry carries.ABAP Cloud readiness
Cloudification Repository Viewerflavors revisedThe documentation's Introduction places what the viewer shows in one flavor: "The Cloudification Repository is part of the new ABAP Cloud development model and lists released standard APIs that can be used to build the TIER 1 layer." Neither page states a standard ABAP use, so that flavor is left unstated.ABAP Cloud readiness
Loggingecosystems revisedSRBJSLogger and openui5-error-collector were staged in intake-20261019-bestofui5 with no capability edge, because this capability was not open on the UI5 door. The UI5 reading comes from the sap/base/Log API documentation and the OpenUI5 Logging and Tracing page.Logging
Show 2 more
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.Agent guidance
Werkbankprovides revisedWhat Werkbank adds for ABAP, CAP and UI5 is its catalog of development skills; the workspace itself is not specific to any of those stacks. Agent workspaces is narrowed back to BTP.Agent guidance
Sun 18
abapsmithadded to the atlasABAP MCP server over ADT with a local journal that can undo writesAgent access to your code
Modernization Agents for SAP on AWSadded to the atlasAWS agents for ABAP, PI/PO and BW modernisation workAgent access to your code
SAP Developers MCPadded to the atlasHosted MCP server of developers.sap.com tutorials and missionsAgent guidance
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
@abap2ui5/mcp-serveradded to the atlasMCP server for the abap2UI5 check, deploy and run loopAgent access to your code
abap-agent-runtimeadded to the atlasABAP-native MCP endpoint that drives opted-in abap2UI5 appsLLM integration
admin-cockpitadded to the atlasUsage, error and response-time monitor for abap2UI5Telemetry
Clean-Core.ioadded to the atlasHosted workspace redrawing custom ABAP as BPMN and grading itABAP Cloud readiness
Show 25 more
Cloudification Repositoryadded to the atlasSAP's list of released APIs for SAP Cloud ERP with successorsABAP Cloud readiness
config-managementadded to the atlasTheme, CSS and CSP settings of abap2UI5 pages kept in tablesConfiguration
ABAP + MCP: Let AI Do Real Development in Your SAP Systemexplains 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 access to your code
ABAP development tools for Visual Studio Code: Patch 1.0.1 releasedexplains 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 guidance
ABAP development tools for Visual Studio Code: Version 1.1 releasedexplains 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 access to your code
Agent access to your systemsdescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.cap. Maintainer-requested scope audit.Agent access to your systems
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
Calling Claude from ABAP: How I Wired SAP AI Core into a Real Business Scenarioexplains 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
Capturing Background Job Errors in SAP Using the Application Log (SLG0/SLG1)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).Logging
Change promotiondescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.abap. Maintainer-requested scope audit.Change promotion
Claude Code via MCP: Poor man's Joule, or a practical tool?explains 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 access to your code
Cloudification Repository Viewerrequires, connects revisedSAP's Cloudification Repository entered the graph, so the repository this reads is a node rather than a name in a sentence. Both edges rest on the viewer's own documentation: the repository "lists released standard APIs that can be used to build the TIER 1 layer", and the Repository field is a "Selection of the different release statuses that are made available by SAP in different JSON files". No protocol, direction or condition: the documentation states none.ABAP Cloud readiness
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
From SEGW and Legacy UI5 to RAP with ARC-1explains 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 access to your code
How I Use AI for Development and Why Context Mattersexplains 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 access to your code
How to Connect Claude Code to ABAP with Zero-Config MCPexplains 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 access to your code
Introducing ARC-1: A Secure ADT MCP Server for Enterprise SAP Developmentexplains 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 access to your code
OData to outcomes—Build AI-enabled SAP Fiori apps using SAP Fiori elementsexplains 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 access to your code
Patterns for using LLMs in ABAP developmentexplains 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 access to your code
S/4HANA Observability: Streaming SAP Cloud ALM & LogServ Telemetry to BigQuery & Vertex 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).Telemetry
SAP's API Policy on AI Agents: What It Prohibits, Allows, and Leaves Openexplains 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
Scheduling a Background Job for the BDC Session Method Using RSBDCSUBexplains 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).Job scheduling
Spec first: The disciplined way to develop ABAP with agentsexplains 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 access to your code
Transform your configuration of SAP S/4HANA Cloud with agentic 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 access to your systems
Using Claude for SAP ABAP development on RFC-only / SAProuter systems (even ECC R/3)explains 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 access to your code
Thu 15
open-abap-baladded to the atlasApplication logging for ABAP transpiled to JavaScript on Node.jsLogging
sap-mcp-serveradded to the atlasReads SAP ECC and S/4HANA for an agent over Gateway OData and RFC, with a Node bridge that speaks the RFC protocol without the proprietary SAP NetWeaver RFC SDK.Agent access to your systems
Werkbankadded to the atlasLocal desktop workspace for AI conversations with SAP connectorsAgent guidance
abap-offstack-aunitprovides revisedcapability:agent-guidance widened installs_into to the ABAP door and declared system_reach there. The README read on 2026-10-15 names four clients beside its install command and adds "and others", so the four named ones are the value and the open end is not read as a fifth. This is the only entry behind the door that states the third system_reach state, in a sentence of its own: nothing requires a provisioned SAP system. The boundary it states elsewhere, that shimmed-out classes stay an on-stack concern, is the entry's own warning and not a qualification of that value.Agent guidance
Show 18 more
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.Agent guidance
ADT MCP Serverdescription, provides[0] revisedSAP's launch post for the re-invented Joule for Developers points to the ADT MCP Server's available MCP tools in ADT for Eclipse and says the server drives the developer's own coding agent; it does not describe how the server is enabled in Eclipse. The Help page now reads "launches" where the quote said "starts".Agent access to your code
Agent access to your codeframing by ecosystem revisedBeside Agent access to your systems, the ABAP door read as two names for one thing. This one is about the code, development objects reached through ADT; that one is about business data and operations. The atlas maintainer's decision.Agent access to your code
Agent evalscore coverage, coverage by flavor, facets, gap revisedThe note rested on "everyone" and "nobody", which nothing here sources. The replacement says what the material read on the three doors covers and what it leaves to the project, which is checkable.Agent evals
Agent guidancecoverage by ecosystem, framing by ecosystem, facets, coverage by flavor, framing by flavor revisedskillOverflowDanKromp/skillOverflowA collection of 41 agent skills, 37 for CAP, Fiori, BTP, UI5, ABAP, Integration Suite and HANA work and four for creating, reviewing and retiring skills, each with its own eval.independent, cap entered on 2026-09-18, after this flavor was assessed, serves the UI5 door and states no flavor, so by the flavor rule it answers in all of them. Its own skill list names SAPUI5 data binding, custom controls, i18n and testing and nothing about the component library, so it is reported as a fallback rather than read as a community presence here. Saying so is what keeps core-only honest beside the options the page lists.Agent guidance
ARC-1 Skillsprovides revisedcapability:agent-guidance widened installs_into to the ABAP door and declared system_reach there. The skills README read on 2026-10-15 names each client one at a time in its manual-install table, with a directory per client, which is why each value carries its own row; the plugin routes it documents beside that are for Claude Code and Agent Plugins, and the skills command line it offers states "any agent" rather than a list. system_reach rests on the prerequisite the README already states, which the entry's own warning repeats: the server is required for every skill that touches ABAP, and the reader connects it.Agent guidance
claude-abap-devprovides revisedcapability:agent-guidance widened installs_into to the ABAP door and declared system_reach there. Both answers were already quoted on this entry: the README calls it a Claude Code plugin and names no other client, and the sentence about detecting servers by tool name is the clearest statement of the third state on this door, since the reader supplies the servers and the skills do not care what they are called. Re-read on 2026-10-15 and unchanged.Agent guidance
claude-abap-skillsprovides revisedcapability:agent-guidance widened installs_into to the ABAP door and declared system_reach there. The README read on 2026-10-15 lists Claude Code as the first prerequisite and names no other client the plugins install into, so the one value is the whole answer; the
AGENTS.md template it ships is for agents that are not Claude and is not an install route the README states. system_reach rests on the sentence the entry's own warning already turned on: there is no connector here, and the reach comes from servers the reader connects.Agent guidanceDanKromp/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.Agent guidance
LLM integrationcore coverage, coverage by flavor, framing by flavor, facets revisedTwo questions the options here answer differently and the page could not show. Which models an option reaches is the first fact a reader needs, because all but one of the CAP options are clients of SAP AI Core; whether the response can be streamed decides whether a chat surface is possible at all. Both are scoped to cap: the ABAP, UI5 and BTP options were not read for them in this pass.LLM integration
rap-skillsprovides revisedcapability:agent-guidance widened installs_into to the ABAP door and declared system_reach there. The skills are cloned into a Claude Code skills directory and the README names no other client, so the one value is the whole answer. system_reach rests on the README's own sentence about VSP, which the reader downloads and configures with their own SAP credentials: the bridge is named and not supplied.Agent guidance
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.Agent guidance
sap-basis-opsprovides revisedcapability:agent-guidance widened installs_into to the ABAP door and declared system_reach there. The README read on 2026-10-15 says the repository is a Claude Code plugin marketplace and names no other client. system_reach rests on the sentence the entry's own description already paraphrased, and it is the clearest statement of that state on this door: the shell server is the reader's to supply, and the skills carry no credentials of their own.Agent guidance
sap-mcp-serverentry revisedHanded over in a chat as one address and written from the repository's own README, read raw. Placed on the ABAP door and on agent access to your systems, the concern split out of MCP servers on 2026-10-09: it reaches into a system you run from outside, as the door's two existing providers of that capability do. The README never says ABAP, so the placement rests on the system it reaches and the protocols it names — Gateway OData services, RFC/BAPI, RFC_READ_TABLE and DDIF_FIELDINFO_GET — rather than on a development model it states. Not umbrella: it names ECC and S/4HANA and reaches them through one stack's own protocols, so a door holds it. No tool_count: the README lists its tools in a table and states no count. No flavors: nothing read states standard ABAP or ABAP Cloud. No compat.runtimes: the server is Python with an optional Node bridge, which that enum cannot say.Agent access to your systems
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.Agent guidance
SuperClaude for SAPprovides revisedcapability:agent-guidance widened installs_into to the ABAP door and declared system_reach there. The README read on 2026-10-15 calls it a Claude Code plugin in its own subtitle and names no other client; the installation steps are documented in a separate file that was not read, which does not change the client. system_reach is the state this entry defines: the server it depends on is installed, configured and connection-tested by its own setup command, which is the fact the entry's own warning about being a stack rather than a component already rests on.Agent guidance
Telemetrycore coverage, coverage by flavor, framing by flavor, framing by ecosystem, facets revisedThree questions the sources answer differently for the CAP options and that change which one a reader reaches for: which signals it produces, where it can send them, and whether the application has to write code for a signal of its own. Scoped to the CAP door; the ABAP and BTP options were not assessed in this pass.Telemetry
Werkbankecosystem revisedThe project homepage describes "A small, curated shelf of MCP servers and SAP development skills." Its own catalog spans ABAP (ARC-1 and ABAP Cloud), CAP (CAP Upgrade), and UI5 skills; the workspace is not specific to one stack. This intake follows the maintainer’s explicit request after the September source sweep passed it over for lacking a workspace capability; that concern now exists as Agent workspaces. The served views describe which users the project-owned install catalog addresses. Werkbank provides the workspace; each selected connector or skill supplies the stack-specific behavior. No SAP implementation capability is attributed to Werkbank itself.Agent guidance
Wed 14
Agent access to your codenormative relevance revisedThe policy's agentic provision reaches every server that calls ADT for an agent; it was stated on arc-1 alone and as unsourced prose in several boundaries.Agent access to your code
aibap.mcpdescription revisedThe README's own constraint is now its explicit SAP API Policy relation, quoted.Agent access to your code
arc-1description revisedThe licensing side is its explicit SAP API Policy relation, sourced to its README; the rest restated what any server in front of ADT is. Removed at the atlas maintainer's request on 2026-10-14.Agent access to your code
LLM integrationcoverage by flavor revisedThe PromptInput page no longer carries the sentence this rested on. Read again on 2026-10-14 it states "The @ui5/webcomponents-ai package is under development and considered experimental - components' APIs are subject to change. Furthermore, the package supports Horizon themes only", with no version marker in it. The since-2.0 claim had no second source, so it goes rather than stand unsourced; the experimental state and the Horizon-only limit stay, in the words the page now uses, which are the words coverage_by_ecosystem.ui5 already quoted. The flavor's own assessment of who provides it was not redone, so assessed_at stands.LLM integration
Show 2 more
midasol/sap-mcp-serverdescription revisedThe whole paragraph was the policy, which Agent access to your systems carries as a condition sourced to the policy.Agent access to your systems
vibing-steampunkdescription revisedThe policy is now a condition of Agent access to your code for ABAP, sourced to the policy itself.Agent access to your code
Mon 12
pam-mcp-serveradded to the atlasLocal MCP server on support status from an SAP PAM exportKnowing the maintenance status of a release
SAP Support Radaradded to the atlasBrowser app checking SAP product support status from a PAM exportKnowing the maintenance status of a release
Agent access to your systemscore coverage, coverage by ecosystem, description revisedMaintainer requested complementary boundaries so a CAP bridge can connect system access and application MCP exposure, while implementation restrictions remain explicit. Domains, providers and task classifications are unchanged.Agent access to your systems
Knowing the maintenance status of a releaseentry revisedDrafted with sap-support-radar and pam-mcp-server, the first umbrella artifacts (ADR-0063), which had no concern to attach to: mcp-servers is serving an application one built, agent-systems-access reaches into a running SAP system, and documentation is first-party docs made searchable. On the ABAP, CAP and UI5 doors because each has a published SAP answer of its own: the Product Availability Matrix, capire's release schedule and the SAPUI5 version overview. BTP is left out: its services name plans and regions rather than releases, and no page was read that states a maintenance period for one. core-only on every door because SAP publishes the answer and no door holds an option of its own; the umbrella entries count into no door's coverage by construction.Knowing the maintenance status of a release
Show 2 more
pam-mcp-serverentry revisedStaged as its own entry beside the app (ADR-0063, two entries) because an agent reaches for the server and a person opens the app. part_of rests on the README's project layout. ecosystem: umbrella and serves_ecosystems: abap for the same reasons as the app: it reads the same matrix, and its documentation's worked example queries SAP S/4HANA 2022 and SAP NetWeaver 7.5. No tool_count: the README lists three tools and states no count. Its package is private and not on npm.Knowing the maintenance status of a release
SAP Support Radarentry revisedStaged with the capability Knowing the maintenance status of a release and the external SAP Product Availability Matrix. ecosystem: umbrella (ADR-0063) because its documentation is about SAP products as such and names no single stack it serves: "Check the support/maintenance status of the SAP products and versions you actually use against the official SAP Product Availability Matrix (PAM)". OpenUI5 is what it is built with, not whom it serves. serves_ecosystems: abap because the releases its documentation checks are SAP S/4HANA and SAP NetWeaver, as in the worked example in docs/mcp-server.md ("SAP S/4HANA 2022 On-Premise", "SAP NetWeaver 7.5"). use_as: reference because it is consulted at its own address. The README names no contributors besides the maintainer. Named SAP Support Radar, the title the maker gives it in the README, by the maintainer's decision on 2026-10-12; serves_ecosystems: abap confirmed by the maintainer the same day.Knowing the maintenance status of a release
Sat 10
Clean Core Measurementadded to the atlasReports Clean Core ATC results per system as Level A to D KPIsABAP Cloud readiness
Fri 9
abap-offstack-aunitentry revisedIn the SAP AI Skills Library registry snapshot since the baseline of 2026-09-18 and never drafted; the registry record for skills/abap-offstack-aunit changed before the 2026-10-09 check, so it enters as a new entry rather than a revision. Written from the repository's own README; hard rule 7: skills are indexed, never authored here. The registry's skillspector scan is its own dated claim and is not carried as a field.Agent guidance
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.Agent guidance
Agent access to your systemsentry revisedSplit out of MCP servers at the maintainer's decision. That capability named a protocol and carried two concerns: exposing what you built to agents, which stays there under a name that says so, and giving agents a way into an SAP system you run, which is this one. Thirty providers moved with their own sentences; the Commerce and SuccessFactors slots moved with them. Named beside agent access to your code, its development-time sibling.Agent access to your systems
Agent guidanceecosystems revisedSAP Commerce opened as a product door (docs/concepts/product-doors.md, ADR-0033) and sap-commerce-skillsap-commerce-skillAn agent skill for SAP Commerce Cloud 2211-jdk21.1 and later: 21 reference guides, 58 code templates and three shell scripts, installed through the skills CLI.independent, commerce entered behind it with no tile to sit under. Packaged knowledge for the Commerce type system, service layer, ImpEx and OCC API is the same concern the node already holds on four doors, so the key was added rather than the capability forked.Agent guidance
Show 8 more
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
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.Agent access to your systems
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.Agent access to your systems
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.Agent access to your systems
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.Agent access to your systems
pyrfc-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.Agent access to your systems
sap-security-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.Agent access to your systems
sapskillsentry revisedIn the SAP AI Skills Library registry snapshot since the baseline of 2026-09-18 and never drafted; the registry record for skills/clean-abap changed before the 2026-10-09 check, so it enters as a new entry rather than a revision. Represented once at repository level, as skillOverflowDanKromp/skillOverflowA collection of 41 agent skills, 37 for CAP, Fiori, BTP, UI5, ABAP, Integration Suite and HANA work and four for creating, reviewing and retiring skills, each with its own eval.independent, cap is: the registry registers one skill, clean-abap, while the repository documents and installs three, so the repository's count is used for the entry and both remain in the crawl record. Written from the repository's own README; hard rule 7: skills are indexed, never authored here.Agent guidance
Tue 6
claude-abap-devadded to the atlasFive ABAP workflows for Claude Code on existing MCP serversAgent guidance
claude-abap-deventry revisedHanded over as a URL in a chat session and written from the repository's own README. Hard rule 7: skills are indexed, never authored here, and the guardrails are reported as the maintainer states them rather than as anything the atlas has run. when_not_to_use and to_build_on_it are left for an editor.Agent guidance
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.Agent access to your codeSun 4
arc-1-bopf-enhadded to the atlasarc-1 extension for reading and maintaining BOPF enhancementsAgent access to your code
arc-1-extension-sampleadded to the atlasSample arc-1 extension in TypeScript with ten custom tools
ZARC1_EXTENSION_FORMSadded to the atlasarc-1 extension for SAPscript and Smart Forms objectsAgent access to your code
arc-1description revisedRe-read against the README, the npm registry record, the extensions page and the release notes on 2026-10-04, with arc-1 at 1.5.0 published 2026-10-02. Every claim the entry already carried still holds word for word, so the checked dates move and the text does not, except where the documentation says something the entry did not. Two such things:
Custom_* tools an operator registers without forking, which the corpus already recorded on claude-sap-kitclaude-sap-kitA Claude Code plugin of three skills that extends arc-1 with five Custom_* tools for an on-premise ABAP system: running a report and reading its ALV as JSON, previewing a NAST message as PDF, and reading, writing and replacing SmartForms as XML.independent, abap and not on the server those tools run in, and one agent plugin that installs the server together with ARC-1 SkillsARC-1 SkillsTwenty-two SKILL.md files shipped in arc-1's own skills/ directory for RAP scaffolding, unit test generation, clean-core audits and migration paths, loaded on demand by description and namespaced /arc-1:<skill> when installed through the Claude Code plugin.independent, abap. The seven guardrails added were stated when the entry was written and left out of it; they are quoted, not counted. The run_code facet stays absent: the extensions page gates class and report execution behind two flags and a plugin the operator writes, which is not the server stating that it runs code.Agent access to your codeShow 3 more
arc-1-bopf-enhentry revisedEntered by intake from the repository README after the admin had routed the URL to a refresh of arc-1, which reported it as a candidate of its own. Written from the README and the repository description.Agent access to your code
arc-1-extension-sampleentry revisedEntered by intake from the README, found through ARC-1's extensions page, which links it as the worked sample.
ZARC1_EXTENSION_FORMSentry revisedEntered by intake from the repository README and description.Agent access to your code
Sat 3
Maherd18/sap-mcp-serveradded to the atlasPolicy-checked MCP server for ABAP development over ADTAgent access to your code
Maherd18/sap-mcp-serverentry revisedHanded over as a URL. Behind the ABAP door because the objects it reads and changes are ABAP ones in a system reached over ADT. Two edges: agent access to your codeAgent access to your codeLetting a coding agent read the project or the system you actually have, reach its model, its objects and its checks, and act on it. In file-based environments that works out of the box; complex systems need dedicated access capabilities. Whatever the environment, the agent also needs project- and framework-specific context, so it understands the thing in front of it rather than guessing from what it remembers of its training data. The transport is incidental: an MCP server, a language server or a CLI answer the same question, and what differs between them is how much of the real thing the agent can see. Distinct from MCP servers, which is a protocol adapter on your own running service, and from agent guidance, which is knowledge handed over as files rather than read from the thing itself.SAP and community, unassessed for the eight tools over ADT, with
create_objects entered as false because the README states that choice rather than leaving it out, and tool governanceTool governanceControlling what an agent may call, with which authorisations, and leaving an audit trail of what it did. The authorisation question that MCP exposure raises but does not answer.SAP and community, unassessed for the policy file, the allow-lists, the read-only switch, the approval and separation-of-duties rules, the dry-run mode and the audit log, which the README's own opening makes the point of the server. MCP serversServe your application over MCPExposing selected application data and business operations to an AI agent through the Model Context Protocol. An application may also integrate remote services through service integration, connecting its exposed contract with agent access to your systems. Development assistance belongs to agent access to your code.SAP and community, narrow by design was considered and left off: that capability is a protocol adapter on a running application service, and this one helps somebody write code, which its own description sends here. No flavor is stated, since the README names no ABAP release or cloud edition; tool_count is left out because the README names no number, and the eight in the prose is a count of its own Tools table. The second tool governanceTool governanceControlling what an agent may call, with which authorisations, and leaving an audit trail of what it did. The authorisation question that MCP exposure raises but does not answer.SAP and community, unassessed provider on the ABAP door, where the reading was community-only with one; the coverage note is left to revisit by hand.Agent access to your codeThu 1
sap-ai-dev-toolkitadded to the atlasMCP proxy pinning an agent's ABAP tools to one SAP systemAgent access to your code
Bellasources, interfaces revisedThe entry recorded the MCP connection Bella opens to ARC-1arc-1An MCP server in front of the ADT REST API that runs locally and on Cloud Foundry with twelve tools that read, search, write, activate, lint and transport ABAP objects.independent, abap and not the one it answers: on the two subscription routes Bella starts a CLI with its built-in tools switched off and hands it the
adt_* tools over an MCP server of its own. The README states the server, the address and the token in both of those sections. An interface is a fact about the node and belongs on the thing that offers it (docs/concepts/design-roles-and-interfaces.md §3), so it is entered here rather than left to be read off the CLI's side.Agent access to your codesap-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.Agent access to your code
Wed 30
Bellaadded to the atlasEclipse plugin bringing Claude into ABAP Development ToolsAgent access to your code
Bellaentry revisedHanded over as a repository URL in an intake request. It is the first entry on the ABAP door that puts the assistant inside the ADT editor rather than in front of ADT as a separate server, and its README compares its own tools with those of ARC-1arc-1An MCP server in front of the ADT REST API that runs locally and on Cloud Foundry with twelve tools that read, search, write, activate, lint and transport ABAP objects.independent, abap, which the graph already holds.Agent access to your code
Tue 29
pyrfc-mcpadded to the atlasMCP server calling RFC-enabled function modules behind an allowlistAgent access to your systems
pyrfc-mcpentry revisedHanded over as a URL. Filed behind the ABAP door because the system it reaches is an ABAP one and the reader who points it at theirs is working on that system, which is the opposite case from open-rfcopen-rfcAn SDK-free TypeScript and JavaScript client for SAP classic synchronous RFC on Node.js, with no native addon and no runtime dependencies, that works as a drop-in under @sap/cds-rfc through an npm override.independent, cap, a client an ABAP developer would never install. Three edges: MCP serversServe your application over MCPExposing selected application data and business operations to an AI agent through the Model Context Protocol. An application may also integrate remote services through service integration, connecting its exposed contract with agent access to your systems. Development assistance belongs to agent access to your code.SAP and community, narrow by design for the tool surface over function modules, agent access to your codeAgent access to your codeLetting a coding agent read the project or the system you actually have, reach its model, its objects and its checks, and act on it. In file-based environments that works out of the box; complex systems need dedicated access capabilities. Whatever the environment, the agent also needs project- and framework-specific context, so it understands the thing in front of it rather than guessing from what it remembers of its training data. The transport is incidental: an MCP server, a language server or a CLI answer the same question, and what differs between them is how much of the real thing the agent can see. Distinct from MCP servers, which is a protocol adapter on your own running service, and from agent guidance, which is knowledge handed over as files rather than read from the thing itself.SAP and community, unassessed for
read_abap_source alone, and tool governanceTool governanceControlling what an agent may call, with which authorisations, and leaving an audit trail of what it did. The authorisation question that MCP exposure raises but does not answer.SAP and community, unassessed for the allowlists, the table guard, the result limits and the audit log, which the README states as the point of the server rather than as a footnote. RFC connectivityRFC connectivityCalling ABAP function modules from outside the system over RFC, with destinations and connection pooling handled rather than hand-wired on the calling side.SAP and community, narrow by design was considered and left off: the RFC client here is PyRFCPyRFCSAP's Python bindings over the SAP NetWeaver RFC SDK. For the things here it is what a Python program calls ABAP function modules through, and it carries the SDK's own prerequisite with it., so nobody installs this to call a function module from their own code. No flavor is stated, since the README names no ABAP release or cloud edition, and auth and tool_count are left out because the README names neither a mechanism nor a number.Agent access to your systemsMon 28
claude-sap-kitadded to the atlasClaude Code plugin adding Custom_* tools to arc-1Agent access to your code
claude-sap-kitentry revisedHanded over as a URL. Typed
skill rather than mcp-server or package: what a reader installs is a Claude Code plugin of three SKILL.md directories, and the tool surface it brings belongs to arc-1arc-1An MCP server in front of the ADT REST API that runs locally and on Cloud Foundry with twelve tools that read, search, write, activate, lint and transport ABAP objects.independent, abap, which serves MCP — one artifact_type per entry (hard rule 9), the same shape ARC-1 SkillsARC-1 SkillsTwenty-two SKILL.md files shipped in arc-1's own skills/ directory for RAP scaffolding, unit test generation, clean-core audits and migration paths, loaded on demand by description and namespaced /arc-1:<skill> when installed through the Claude Code plugin.independent, abap takes beside that server. It answers agent access to your codeAgent access to your codeLetting a coding agent read the project or the system you actually have, reach its model, its objects and its checks, and act on it. In file-based environments that works out of the box; complex systems need dedicated access capabilities. Whatever the environment, the agent also needs project- and framework-specific context, so it understands the thing in front of it rather than guessing from what it remembers of its training data. The transport is incidental: an MCP server, a language server or a CLI answer the same question, and what differs between them is how much of the real thing the agent can see. Distinct from MCP servers, which is a protocol adapter on your own running service, and from agent guidance, which is knowledge handed over as files rather than read from the thing itself.SAP and community, unassessed through the five Custom_* tools and agent guidanceAgent guidancePackaged knowledge you hand a coding agent so it gets a framework right unprompted — skills, rule files, instruction packs. Distinct from agent tooling, which is about building agentic features into your application, and from agent access to your code, where the agent reads the real project instead of being handed a file about it.SAP and community, core adopted it through the three skills, and states the standard-abap flavor by its requirements, which rule out the two public-cloud ABAP targets by name.Agent access to your codeSun 27
ADT MCP Serverpart of, description revisedThe server is a preference inside the extension, and the connection to an ABAP system is the extension's, stated on its own entry with the protocols SAP's marketplace page names (docs/concepts/design-roles-and-interfaces.md, P3); a part points up at its whole and enters the fact once.Agent access to your code
arc-1connects, requires, description revisedThe connection is what the README states the server fronts (docs/concepts/design-roles-and-interfaces.md, P1), and it attaches the system's entry. The two BTP connections are stated under the README's Cloud Foundry deployment heading, so they carry that condition; the Destination service's sentence states identity forwarding and no data flow, and the ABAP environment's sentence names no protocol. The README's credits table names abaplint as what the linter uses. Two older defects go with it: a nested link that rendered its outer bracket as text, and abap-adt-api named in the same quoted sentence as the other two inspirations and carried by no edge.Agent access to your code
Configurationcore coverage revisedcapire audit 2026-09-27, judgement pages read once more: a page this capability owns was cited nowhere.Configuration
Feature togglescore coverage revisedcapire audit 2026-09-27: the Feature Toggles guide documents toggled features as built into both runtimes, with the production toggle provider left to the project, which is exactly what the one community option supplies. The capability had no core paragraph and no source.Feature toggles
Show 5 more
fr0ster/mcp-abap-adtconnects, description, provides[0], lineage revisedThe README's acknowledgment names the project it started from; the graph holds it, and the edge is the maintainer's own sentence.Agent access to your code
Loggingcore coverage revisedcapire audit 2026-09-27: a page this capability owns was cited nowhere.Logging
Retrieval-augmented generationcore coverage revisedcapire audit 2026-09-27, link-only pages read a fourth time: vector embeddings are one of the three things SAP frames as CAP's native AI support, in the one sentence the section's index says of its own.Retrieval-augmented generation
Telemetrycore coverage revisedcapire audit 2026-09-27: a page this capability owns was cited nowhere.Telemetry
vibing-steampunkconnects revisedThe connection is what the README states the server fronts (docs/concepts/design-roles-and-interfaces.md, P3): the sentence each ABAP server carries and nobody had entered, which the tool role of the ABAP pilot reads as the arrow from the server to the system.Agent access to your code