NewABAP, RAP and ABAP Cloud
In the last 30 days
168 changes
B-Tocs ABAP SDKadded to the atlasWeb service client and connector layer for calling out of ABAP
cross-http-clientadded to the atlasHTTP client for classic on-premise ABAP and ABAP Cloud
launchpad-kpiadded to the atlasPuts a number from an abap2UI5 app on a Fiori launchpad tile
open-abap-odataadded to the atlasOData and Gateway shims serving SEGW-style services on Node.js
ZASISadded to the atlasRegex RuleSets that read barcode strings into named fields
ABAP Architectadded to the atlasEclipse plug-in turning JSON or XML into ABAP types and DDIC objects
abap-ai/mcp2added to the atlasStateless ABAP MCP server SDK for the 2026-07-28 protocol draft
CDS Field Mappingdescription revisedSAP's Cloudification Repository is in the graph, so the README's source is named by its entry rather than by a URL none of this entry's sources gave. The README's sentence is "Source will be the Cloudification Repository, where the mapping old table to new Core Data Services is listed.", so the prose reports it as what the README names and not as how the mapping file is produced today: the file in the repository comes from an extractor class you copy and run in your own system. The CAST, CASE and ABS gap is attributed to the tool's page, which is where that sentence stands, rather than to the README.
ERPLadded to the atlasDuckDB extension reading SAP ERP tables, CDS views and BW queries
open-table-maintenanceadded to the atlasTable maintenance over HTTP for a table fixed in code
ABAP Statistical Toolsadded to the atlasABAP class for descriptive statistics over an internal table
open-abap-pdfadded to the atlasStandalone PDF generator written in ABAP
erpl-node-rfcadded to the atlasRFC client for Node.js and TypeScript without the NW RFC SDK
rfc-connectoradded to the atlasForwards abap2UI5 roundtrips to another system over RFC
Consume ABAP RFC Function Modules in 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).
EPOD ADT MCP Serveradded to the atlasMCP server for ABAP on the ADT session, in Eclipse or standalone
Klystronadded to the atlasMCP server in ABAP inside the application server, with agent skills
@mcp-abap-adt/corereleased 20.0.0ABAP ADT MCP server published as an npm scope and plugin
@mcp-abap-adt/corereleased 19.0.0ABAP ADT MCP server published as an npm scope and plugin
Show 33 more
abapsmithadded to the atlasABAP MCP server over ADT with a local journal that can undo writes
Modernization Agents for SAP on AWSadded to the atlasAWS agents for ABAP, PI/PO and BW modernisation work
@abap2ui5/mcp-serveradded to the atlasMCP server for the abap2UI5 check, deploy and run loop
aibap.mcpdescription revisedThe README's own constraint is now its explicit SAP API Policy relation, quoted.
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.
vibing-steampunkdescription revisedThe policy is now a condition of Agent access to your code for ABAP, sourced to the policy itself.
@mcp-abap-adt/corereleased 18.0.0ABAP ADT MCP server published as an npm scope and plugin
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-abap-adt/corereleased 17.0.0ABAP ADT MCP server published as an npm scope and plugin
fr0ster/mcp-abap-adtreleased 17.0.0Setups against a system with a self-signed or company-CA certificate that worked without any TLS setting.
arc-1-bopf-enhadded to the atlasarc-1 extension for reading and maintaining BOPF enhancements
ZARC1_EXTENSION_FORMSadded to the atlasarc-1 extension for SAPscript and Smart Forms objects
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.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.
ZARC1_EXTENSION_FORMSentry revisedEntered by intake from the repository README and description.
Maherd18/sap-mcp-serveradded to the atlasPolicy-checked MCP server for ABAP development over ADT
@mcp-abap-adt/corereleased 16.0.0ABAP ADT MCP server published as an npm scope and plugin
fr0ster/mcp-abap-adtreleased 16.0.0Descriptions of five authentication methods including client certificates and Kerberos, and setups that rely on a
.env in the directory the server starts in.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.sap-ai-dev-toolkitadded to the atlasMCP proxy pinning an agent's ABAP tools to one SAP system
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.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.
Bellaadded to the atlasEclipse plugin bringing Claude into ABAP Development Tools
@mcp-abap-adt/corereleased 15.0.0ABAP ADT MCP server published as an npm scope and plugin
fr0ster/mcp-abap-adtreleased 15.0.0Instructions that start a test run with
CreateUnitTest and poll GetUnitTestStatus.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.
claude-sap-kitadded to the atlasClaude Code plugin adding Custom_* tools to arc-1
@mcp-abap-adt/corereleased 13.0.0ABAP ADT MCP server published as an npm scope and plugin
@mcp-abap-adt/corereleased 14.0.0ABAP ADT MCP server published as an npm scope and plugin
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.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.
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.
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.
Skybuffer AI MCP serveradded to the atlasABAP add-on serving business data and transactions as MCP tools
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.
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.
midasol/sap-mcp-serverdescription revisedThe whole paragraph was the policy, which Agent access to your systems carries as a condition sourced to the policy.
Show 8 more
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.
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.
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.
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.
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.
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.
pyrfc-mcpadded to the atlasMCP server calling RFC-enabled function modules behind an allowlist
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.agentic-abap-evalsadded to the atlasABAP navigation tasks and a grader for coding agents
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.
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.
Werkbankadded to the atlasLocal desktop workspace for AI conversations with SAP connectors
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.
Show 16 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.
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.
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.
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.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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
claude-abap-devadded to the atlasFive ABAP workflows for Claude Code on existing MCP servers
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.
Building Code-Based AI Agents on the BAIPpublishedA Devtoberfest 2026 session on writing the agent yourself rather than configuring one, which is the agent toolingAgent toolingBuilding an agent into your own application — the tools it may call, the state it keeps between turns, and the framework it runs in. Distinct from MCP servers, which expose an application to somebody else's agent, and from agent guidance, which is knowledge handed to a coding agent.SAP and community, unassessed 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 CoreSAP AI CoreSAP's AI service on BTP: the runtime for AI assets, and through the Generative AI Hub inside it the access to foundation models, the orchestration service with its templating, masking, filtering and grounding modules, the Prompt Registry and Document Grounding.sap official, btp 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-webuicap-agent-ui5-webuiGives a CAP agent a UI5 web interface out of the box, so an agent built in the service has somewhere to be talked to without a separate frontend project.independent, cap 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.
abap-agent-runtimeadded to the atlasABAP-native MCP endpoint that drives opted-in abap2UI5 apps
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.
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.
Clean-Core.ioadded to the atlasHosted workspace redrawing custom ABAP as BPMN and grading it
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.
Show 1 more
Clean Core Measurementadded to the atlasReports Clean Core ATC results per system as Level A to D KPIs
config-managementadded to the atlasTheme, CSS and CSP settings of abap2UI5 pages kept in tables
pam-mcp-serveradded to the atlasLocal MCP server on support status from an SAP PAM export
SAP Support Radaradded to the atlasBrowser app checking SAP product support status from a PAM export
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.
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.
open-abap-baladded to the atlasApplication logging for ABAP transpiled to JavaScript on Node.js
admin-cockpitadded to the atlasUsage, error and response-time monitor for abap2UI5
abap-transport-reviewadded to the atlasTransport release check gated by GitHub pull request approval
abap-transport-reviewentry revisedEntered by intake from the repository README and the repository's own facts. Placed on the ABAP door in the standard-abap flavor only, because the README states the tools are classic ABAP using the CTS_REQUEST_CHECK BAdI, background jobs and the cluster table INDX, "none of which is part of ABAP Cloud".
kts982/mcp-sap-guidescription revisedThe policy is now a condition of GUI automation, sourced to the policy itself.
mcp-sap-guidescription revisedThe policy is now a condition of GUI automation, sourced to the policy itself.
sapgui.mcpdescription revisedThe policy is now a condition of GUI automation, sourced to the policy itself.
Cloud ALM Link for ADTadded to the atlasEclipse plugin linking ABAP transports to SAP Cloud ALM features
ABAP Syntax Highlightingadded to the atlasVS Code syntax highlighting for .abap files
ABAP Call Hierarchyadded to the atlasEclipse plugin showing the call hierarchy of ABAP members
ABAP Tagsadded to the atlasEclipse plugin for tagging ABAP repository objects
Show 4 more
abap2UI5 for VS Codeadded to the atlasVS Code extension to preview, activate and lint abap2UI5 apps
abap-adt-apireleased 9.0.01 content item in the atlas was written against an earlier version. Nothing is recorded about what changed.
abapthemesadded to the atlasThree colour themes for ABAP source in ADT for Eclipse
Hammeradded to the atlasNative macOS code editor for ABAP and CDS
SAP TCode Runneradded to the atlasVS Code sidebar that opens SAP transactions through WebGUI
ui5-tcode-finderadded to the atlasBrowser page searching SAP transaction codes
ui5-tcode-finderentry revisedStaged with the capability Finding a transaction code, drafted in the same batch because the corpus held no concern for it. ecosystem: abap is a placement rather than a stated fact: the repository is an OpenUI5 and TypeScript application, but its subject is the transaction codes of a classic SAP system and the only stack its features name is SAP GUI for HTML. serves_ecosystems: ui5 rests on the overview sentence naming the T-Codes a UI5 or Fiori project needs. use_as: reference because it is consulted at its own address rather than installed into a project.
abap2UI5 Layout Editoradded to the atlasDrag-and-drop UI5 view editor that writes an abap2UI5 app class
eclipsADT-o-matadded to the atlasPowerShell wizard installing Eclipse with ADT and plugins
eclipsADT-o-matentry revisedEntered by intake from the repository README and description.
abap2UI5 Playgroundadded to the atlasIn-browser ABAP editor beside the abap2UI5 app it builds
web-abap2UI5added to the atlasabap2UI5 transpiled to JavaScript and run in a browser tab
open-steamgateadded to the atlasLocal ABAP server serving /IWBEP/ OData v2 without an SAP system
ABAP Code Searchadded to the atlasEclipse plugin searching ABAP sources from the search dialog
ABAP Search and Analysis Toolsadded to the atlasEclipse plugin for ABAP object search and CDS view analysis
abapwuluadded to the atlasRefreshes the where-used list for objects in one package
Tools for abapGitadded to the atlasHelper programs around abapGit
@abap2ui5/linteradded to the atlasCommand-line checker for abap2UI5 app classes and their views
abap2UI5 headless frontendadded to the atlasDrives abap2UI5 app classes from ABAP Unit tests
@abaplint/transpileradded to the atlasTranspiles ABAP to JavaScript to run on Node.js
express-icf-shimadded to the atlasShim running an ABAP ICF handler behind an Express 4.x server
open-abap-coreadded to the atlasCore ABAP artifacts for code transpiled by @abaplint/transpiler
rap-extadded to the atlasFloorplans rendered from CDS UI annotations as abap2UI5 apps
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).
XLF Translatorflavors, type properties revisedThe flavor rests on the page's "The tool is mainly used to translate ABAP Cloud Content, which is generated using the 'Maintain Translation' app (XLIFF Version 1.2)." The web-tool block's uploads key carries the one sentence the page gives about the file leaving the machine, "After uploading, all fields that have a translation element are available for translation.", verbatim; access is left out because neither the page nor the site's FAQ says what it takes to use the tool. The prose no longer says the file is opened in the browser, which the word "uploading" does not support, no longer treats XLIFF 1.2 as what the tool accepts (the page states the version of the ABAP Cloud content it is mainly used for), and attributes "without installing an additional tool" to the maker. when_not_to_use was "One file per session, translated by hand, field by field", none of which the page states.
LISAadded to the atlasMCP server for reading and writing ABAP object translations
LISAentry revisedEntered by intake from the README, found through ARC-1's extensions page, which names it in its example of driving a custom ABAP HTTP service.
abap-cloud-guiadded to the atlasReport-style programming model for abap2UI5 on ABAP Cloud
abap2UI5 for Exceladded to the atlasOffice add-in running an abap2UI5 app in Excel's task pane
abap2UI5 frontendadded to the atlasabap2UI5 frontend as ABAP artefacts installed with abapGit
abap2UI5 frontend-webcomponentadded to the atlasabap2UI5 frontend rendering with UI5 Web Components
Show 7 more
abap2UI5 protocoladded to the atlasVersioned specification of the abap2UI5 roundtrip protocol
abap2UI5-addons/popupsadded to the atlasReady-made dialogs for abap2UI5 apps
abap2UI5-localadded to the atlasabap2UI5 folded into the local classes of one HTTP handler
custom-controlsadded to the atlasThirteen custom UI5 controls for abap2UI5 apps
http-connectoradded to the atlasForwards abap2UI5 roundtrips to another system over HTTP
layout-managementadded to the atlasTable and form layouts with saved variants for abap2UI5
selection-screenadded to the atlasSelect-options with saved variants for abap2UI5 apps
Under no capability
pyapi4abapadded to the atlasTemplate pairing a FastAPI service with ABAP reports that call it
Supply Chain Rescueadded to the atlasCAP and SAPUI5 demo of recovery from a supply disruption
@abap2ui5/embed-controladded to the atlasUI5 custom control that runs an abap2UI5 app inside a host app
abap2UI5 mobile shelladded to the atlasNative iOS and Android shell for one abap2UI5 endpoint
Show 14 more
abap2UI5 samplesadded to the atlas129 abap2UI5 sample apps, one ABAP class each
abap2UI5-addons/open-source-libsadded to the atlasEleven abap2UI5 apps, one per open-source ABAP library
abap2UI5/samples-controlsadded to the atlasUI5 Demo Kit samples rebuilt as abap2UI5 apps
abap2UI5/samples-stackadded to the atlasabap2UI5 apps in front of OData, RAP, events and other technology
app-templateadded to the atlasStarter repository for an abap2UI5 app with CI and agent setup
custom-controls-customeradded to the atlasTemplate repository for own UI5 artefacts served to abap2UI5
lock-manageradded to the atlasHolds SAP locks across stateless abap2UI5 roundtrips
Hammer Core Servicesadded to the atlasABAP-side component for the Hammer editor
open-abap-guiadded to the atlasGUI controls for ABAP transpiled to JavaScript
open-abap-lockadded to the atlasConcurrent and cross-session locking for open-abap on PostgreSQL
arc-1-extension-sampleadded to the atlasSample arc-1 extension in TypeScript with ten custom tools
arc-1-extension-sampleentry revisedEntered by intake from the README, found through ARC-1's extensions page, which links it as the worked sample.
abaprapunmanagedadded to the atlasPractice repository for the unmanaged RAP scenario
abaprapunmanagedsaveadded to the atlasPractice repository for managed RAP with unmanaged save