{"ref":"capability:agent-code-access","page":"/capabilities/agent-code-access","json":"/capabilities/agent-code-access.json","generated":"2026-10-26","drafted_with_ai":true,"entity":{"id":"agent-code-access","name":"Agent access to your code","domain":"ai-and-agents","ecosystems":["cap","abap","ui5","btp"],"universal":true,"description":"Letting 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](capability:mcp-servers), which is a protocol adapter on your own running service, and from [agent guidance](capability:agent-guidance), which is knowledge handed over as files rather than read from the thing itself.","short":"Letting a coding agent read and act on your project or system","facets":[{"key":"read_source","label":"source","kind":"flag","group":"read","ecosystems":["abap"]},{"key":"search_objects","label":"search","kind":"flag","group":"read","ecosystems":["abap"]},{"key":"where_used","label":"where-used","kind":"flag","group":"read","ecosystems":["abap"]},{"key":"ddic_metadata","label":"DDIC","kind":"flag","group":"read","ecosystems":["abap"]},{"key":"cds","label":"CDS","kind":"flag","group":"read","ecosystems":["abap"]},{"key":"table_data","label":"table data","kind":"flag","group":"read","ecosystems":["abap"]},{"key":"write_source","label":"write","kind":"flag","group":"change","ecosystems":["abap"]},{"key":"create_objects","label":"create","kind":"flag","group":"change","ecosystems":["abap"]},{"key":"activate","label":"activate","kind":"flag","group":"change","ecosystems":["abap"]},{"key":"transports","label":"transports","kind":"flag","group":"change","ecosystems":["abap"]},{"key":"git","label":"git","kind":"flag","group":"change","ecosystems":["abap"]},{"key":"syntax_check","label":"syntax","kind":"flag","group":"check","ecosystems":["abap"]},{"key":"atc","label":"ATC","kind":"flag","group":"check","ecosystems":["abap"]},{"key":"unit_tests","label":"ABAP Unit","kind":"flag","group":"check","ecosystems":["abap"]},{"key":"run_code","label":"run code","kind":"flag","group":"run","ecosystems":["abap"]},{"key":"dumps_or_traces","label":"dumps","kind":"flag","group":"run","ecosystems":["abap"]}],"core_coverage":{"state":"core-and-community","assessed_at":"2026-09-09","relationship":"unassessed","note":"Both are present — SAP publishes cds-mcp and the community builds beside it — but how they relate has not been assessed. No capire page states what the core intends here, so what_core_does is left empty rather than inferred from a repository.","community_adds":"[capforge](artifact:automatizatodo-capforge) scaffolds CAP and CDS for an agent and then holds it to `cds compile`, so the agent does not stop until the generated project builds."},"coverage_by_ecosystem":{"abap":{"state":"core-and-community","assessed_at":"2026-10-25","what_core_does":"SAP ships the [ADT MCP Server](artifact:sap-adt-mcp-server), a setting in [ABAP Development Tools for VS Code](artifact:sap-adt-vscode) that turns the connection the IDE already holds into a local MCP endpoint on the developer's machine. [SAP Joule for Developers, ABAP AI capabilities](artifact:sap-joule-for-developers) drives coding agents through it, and [ADT resources](artifact:sap-adt) are the REST APIs underneath.","where_it_stops":"It stops where the system boundary does — an agent still needs credentials and a reachable system, which is a licensing and landscape question rather than a technical one.","sources":[{"url":"https://help.sap.com/docs/abap-cloud","title":"SAP Help — ABAP Cloud","checked":"2026-08-31"},{"url":"https://help.sap.com/docs/abap-cloud/abap-development-tools-for-visual-studio-code/enabling-adt-mcp-server","title":"Enabling ADT MCP Server — SAP Help Portal","checked":"2026-09-15","quote":"You can enable the ADT MCP Server in ADT for VS Code to perform ABAP development tasks in an agentic workflow."},{"url":"https://help.sap.com/docs/abap-cloud/abap-development-tools-for-visual-studio-code/enabling-adt-mcp-server","title":"Enabling ADT MCP Server — SAP Help Portal","checked":"2026-10-15","quote":"it launches a local HTTP server at http://localhost:<port>/mcp"}],"relationship":"unassessed","community_adds":"The community's MCP servers reach the same [ADT resources](artifact:sap-adt) from outside the IDE: as a local process or a central server, a few inside the system itself, over stdio or HTTP. Many sign in with more than a user and password, from OAuth and X.509 to principal propagation and BTP destinations, and most state that they write as well as read."},"ui5":{"state":"core-only","assessed_at":"2026-09-09","where_it_stops":"At the tooling SAP already owns: fiori-mcp drives the same generators and editors Fiori tools ship, so it reaches what those reach and no further."},"btp":{"state":"core-and-community","assessed_at":"2026-09-09","relationship":"unassessed","where_it_stops":"At what a bound landscape allows. The tools need a service metadata file, the Cloud Foundry CLI and access to the environment, so this is a provisioning question before it is a tooling one.","community_adds":"Independent and partner servers on this door reach systems beside the project: [sap-ai-dev-toolkit](artifact:grknylmz-sap-ai-dev-toolkit) pins an agent's ABAP tools to a system through the destinations of SAP Business Application Studio, [bw-modeling-mcp](artifact:dnic-dev-bw-modeling-mcp) opens BW/4HANA modelling objects to an agent and can run centrally on BTP, and [Modernization Agents for SAP on AWS](artifact:aws-modernization-agents-for-sap) converts custom ABAP and moves PI/PO and BW content onto BTP."}},"framing_by_ecosystem":{"cap":{"description":"An agent knows the framework from training data, but little about your model, your plugins or the newest `cds` version you are on. Closing that gap means handing it the project's own context, which is what [@cap-js/mcp-server](artifact:cap-js-mcp-server) does, so the advice it gives is about the service in front of it rather than about CAP in general."},"abap":{"name":"Agent access to ABAP code","description":"There is no filesystem to read: the source lives in a system reachable by default through [ADT resources](artifact:sap-adt), so this is a landscape and licensing question before it is a tooling one. Many MCP servers build towards [ADT resources](artifact:sap-adt), but differ in where they run, how they connect and how they authenticate.\nSAP ships its own servers here, meant to be the default way in. The community ones are further along in features."},"ui5":{"name":"Agent access to your Fiori app","description":"An assistant that can only describe the steps leaves the developer to perform them. [fiori-mcp](artifact:sap-ux-fiori-mcp-server) lets it create and edit the application directly, driving the generators and editors Fiori tools already ship rather than reimplementing them — which also means it reaches what those reach and stops where they stop."},"btp":{"description":"Here the project an agent works on is bound to a landscape rather than sitting in a folder. [@sap/mdk-mcp-server](artifact:sap-mdk-mcp-server) generates into an MDK project and drives its build and deploy, and reaches past the project to pull OData metadata from the Mobile Services app it is written against."}},"coverage_by_flavor":{"abap-cloud":{"state":"community-only","assessed_at":"2026-09-14","what_core_does":"SAP's own [ADT MCP Server](artifact:sap-adt-mcp-server), shipped inside [ABAP Development Tools for VS Code](artifact:sap-adt-vscode), targets this development model by name: SAP BTP ABAP environment, SAP S/4HANA Cloud Public Edition and SAP S/4HANA Cloud Private 2025 Edition are the systems it lists as currently supported, and it exposes tools to create packages and transports, generate RAP applications and activate objects.","where_it_stops":"SAP calls it \"an experimental feature that may change at any time without notice\" and \"not intended for productive use\", and, like any ABAP Cloud client, it can only reach objects released for ABAP Cloud through ADT — which is why the servers a project actually runs against a BTP ABAP environment or SAP S/4HANA Cloud system today are the independent ones.","sources":[{"url":"https://raw.githubusercontent.com/SAP-samples/abap-platform-rap130/main/README.md","title":"SAP-samples/abap-platform-rap130 — README","checked":"2026-09-14","quote":"SAP BTP ABAP environment, SAP S/4HANA Cloud Public Edition, SAP S/4HANA Cloud Private 2025 Edition are currently supported."},{"url":"https://raw.githubusercontent.com/SAP-samples/abap-platform-rap130/main/exercises/ex01/README.md","title":"SAP-samples/abap-platform-rap130 — Exercise 1: Enable the ADT MCP Server","checked":"2026-09-14","quote":"The ADT MCP Server is an experimental feature that may change at any time without notice. It is not intended for productive use."},{"url":"https://raw.githubusercontent.com/SAP-samples/abap-cheat-sheets/main/19_ABAP_for_Cloud_Development.md","title":"SAP-samples/abap-cheat-sheets: ABAP for Cloud Development","checked":"2026-09-14","quote":"Access to SAP-delivered repository objects is restricted to objects released for ABAP for Cloud Development"}],"note":"[ARC-1](artifact:arc-mcp-arc-1), [ARC-1 LSP](artifact:arc-mcp-arc-1-lsp), [fr0ster/mcp-abap-adt](artifact:fr0ster-mcp-abap-adt) and [@mcp-abap-adt/core](artifact:babamba2-abap-mcp-adt-powerup) state abap-cloud on their own entries; SAP's ADT MCP Server names the same systems in its own documentation."},"web-components":{"state":"unmapped","assessed_at":"2026-09-14","where_it_stops":"SAP does publish an MCP server for this flavor, [@ui5/webcomponents-mcp-server](artifact:ui5-webcomponents-mcp-server), but its tools fetch a named component's API, a framework's integration guide or the documentation set itself; none reads the project the agent is actually working in.","sources":[{"url":"https://github.com/UI5/webcomponents-mcp-server","title":"UI5/webcomponents-mcp-server — README","checked":"2026-09-14","quote":"get_component_api: Fetch API docs for any UI5 Web Component (properties, slots, events, methods). get_guidelines: Get integration guides for React, Angular, or native JavaScript. list_docs: List all available UI5 Web Components documentation with summaries. get_doc: Fetch full content of specific documentation files."}],"note":"Unmapped rather than not-applicable: a Web Components project has files of its own — component definitions, a package.json, a build — for an agent to read and act on, the same as a freestyle UI5 or Fiori elements one, so the concern is not structurally absent the way routing or the flexibility layer are."}},"framing_by_flavor":{"abap-cloud":{"description":"What an agent can reach here is already narrowed by the release contract: [ADT resources](artifact:sap-adt) only, and only the objects SAP has released for ABAP Cloud, the same restriction any developer works under. [ARC-1](artifact:arc-mcp-arc-1) and [ARC-1 LSP](artifact:arc-mcp-arc-1-lsp) read and write against exactly that surface — the LSP variant states it covers \"Modern ABAP-Cloud types only\"."}},"history":[{"date":"2026-09-09","field":"id","from":"abap-agent-tooling","to":"agent-code-access","reason":"The ABAP door had invented the right capability and named it after one ecosystem. The concern — an agent reading the real project instead of guessing — is the same in CAP, where cds-mcp and fiori-mcp answer it, so the node generalises and the ABAP framing keeps the local name. The ABAP reading of 2026-08-31 is carried over unchanged as this capability's ABAP coverage."},{"date":"2026-09-09","field":"ecosystems","from":"cap, abap","to":"cap, abap, ui5","reason":"fiori-mcp was typed as a CAP artifact and carried the UI5 answer inside CAP's framing. Retyping it to ui5 gave this capability a third door with a provider of its own, and the Fiori sentence moved out of the CAP framing into UI5's where it belongs."},{"date":"2026-09-09","field":"ecosystems","from":"cap, abap, ui5","to":"cap, abap, ui5, btp","reason":"An SAP-published MCP server entered from the sap-ai-mcp-servers catalogue answers this concern on the BTP door, and the door had no tile for it to sit under."},{"date":"2026-09-14","field":"coverage_by_flavor.abap-cloud","from":null,"to":"community-only","reason":"ARC-1, ARC-1 LSP, fr0ster/mcp-abap-adt and @mcp-abap-adt/core state abap-cloud on their own entries and are all independent. SAP's ADT MCP Server names the same ABAP Cloud systems in its own documentation (the SAP-samples/abap-platform-rap130 workshop) but its artifact entry carries no flavors field, so it does not count as an sap-official provider stating the flavor, and the validator rule for this state (an sap-official provider must state it, or none may) leaves community-only as the only state the graph supports."},{"date":"2026-09-14","field":"framing_by_flavor.abap-cloud","from":null,"to":"added","reason":"ABAP Cloud narrows what an agent can reach to released objects through ADT, a restriction the door-level framing (landscape and licensing) does not state, so the flavor reads as its own paragraph rather than falling back to it."},{"date":"2026-09-14","field":"coverage_by_flavor.web-components","from":null,"to":"unmapped","reason":"The UI5-door providers of this capability — [@ui5/mcp-server](artifact:ui5-mcp-server) and [fiori-mcp](artifact:sap-ux-fiori-mcp-server) — state freestyle and fiori-elements, never web-components. SAP's [@ui5/webcomponents-mcp-server](artifact:ui5-webcomponents-mcp-server) does carry the web-components flavor but provides [documentation](capability:documentation), not this capability: its four tools serve the library's own API and guides and never open the project in front of the agent. No provider states web-components for agent-code-access, and the concern itself is not structurally absent from the flavor, so unmapped reads truer than not-applicable."},{"date":"2026-09-15","field":"coverage_by_ecosystem.abap.what_core_does","from":"an ABAP MCP server","to":"named sap-adt-mcp-server and sap-adt","reason":"The official MCP server and the HTTP resources it uses now have pages."},{"date":"2026-09-15","field":"framing_by_ecosystem.abap.description","from":"reachable only through ADT","to":"named sap-adt","reason":"The HTTP resources an agent reaches the system through now have a page."},{"date":"2026-09-15","field":"coverage_by_flavor.abap-cloud.what_core_does","from":"SAP's own ADT MCP Server, shipped inside ABAP Development Tools for VS Code","to":"named sap-adt-mcp-server and sap-adt-vscode","reason":"Both now have pages."},{"date":"2026-09-15","field":"framing_by_flavor.abap-cloud.description","from":"ADT only","to":"named sap-adt","reason":"The HTTP resources the flavor is restricted to now have a page."},{"date":"2026-10-14","field":"normative_relevance","from":null,"to":"SAP API Policy, sections 1.1, 1.2, 2.2.2, for ABAP","reason":"The 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."},{"date":"2026-10-15","field":"framing_by_ecosystem.abap.name","from":"Agent access to an ABAP system","to":"Agent access to ABAP code","reason":"Beside 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."},{"date":"2026-10-25","field":"coverage_by_ecosystem.abap.what_core_does","from":"SAP ships an [ADT MCP Server](artifact:sap-adt-mcp-server), and [ADT resources](artifact:sap-adt) expose the underlying REST APIs an agent can be pointed at.","to":"SAP ships the [ADT MCP Server](artifact:sap-adt-mcp-server), a setting in [ABAP Development Tools for VS Code](artifact:sap-adt-vscode) that turns the connection the IDE already holds into a local MCP endpoint on the developer's machine. [SAP Joule for Developers, ABAP AI capabilities](artifact:sap-joule-for-developers) drives coding agents through it, and [ADT resources](artifact:sap-adt) are the REST APIs underneath.","reason":"Rewritten 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."},{"date":"2026-10-25","field":"coverage_by_ecosystem.abap.community_adds","from":"","to":"The community's MCP servers reach the same [ADT resources](artifact:sap-adt) from outside the IDE: as a local process or a central server, a few inside the system itself, over stdio or HTTP. Many sign in with more than a user and password, from OAuth and X.509 to principal propagation and BTP destinations, and most state that they write as well as read.","reason":"Rewritten 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."},{"date":"2026-10-26","field":"coverage_by_ecosystem.btp.state, coverage_by_ecosystem.btp.relationship, coverage_by_ecosystem.btp.note, coverage_by_ecosystem.btp.community_adds","from":"core-only; note: Every provider behind this door is SAP-published, so core-only is a assessment of the corpus rather than a quote from the core.","to":"core-and-community, relationship unassessed; note removed; community_adds names sap-ai-dev-toolkit, bw-modeling-mcp and Modernization Agents for SAP on AWS","reason":"Reassessed against the graph (check:capabilities): independent and partner providers (sap-ai-dev-toolkit, bw-modeling-mcp, Modernization Agents for SAP on AWS) now serve the BTP door beside SAP's @sap/mdk-mcp-server, so the stated core-only contradicted the providers. The note only explained that state."},{"date":"2026-10-26","field":"coverage_by_ecosystem.ui5.note, coverage_by_ecosystem.ui5.where_it_stops","from":"note: One provider, SAP-official, so core-only is a assessment of the corpus...; where_it_stops ended: Nothing in the corpus answers this for a freestyle UI5 application that is not a Fiori one.","to":"note removed; the last sentence of where_it_stops removed","reason":"Reassessed against the graph (check:capabilities): the note and the closing sentence counted providers and claimed an absence in the corpus, which moves with the graph."},{"date":"2026-10-26","field":"coverage_by_flavor.abap-cloud.note","from":"...; SAP's ADT MCP Server names the same systems in its own documentation but carries no flavor statement on its entry here.","to":"...; SAP's ADT MCP Server names the same systems in its own documentation.","reason":"Reassessed against the graph (check:capabilities): removed a claim about what an entry carries, which changes when the entry does."},{"date":"2026-10-26","field":"coverage_by_flavor.web-components.where_it_stops, coverage_by_flavor.web-components.note","from":"its four tools fetch ...; so nothing here answers this concern for a Web Components app yet. note ended: No provider in the corpus states this flavor for it.","to":"its tools fetch ...; none reads the project the agent is actually working in. note ends after the structural-absence comparison.","reason":"Reassessed against the graph (check:capabilities): removed the tool count and the two absence claims about who has built something."}],"drafted_with_ai":true,"normative_relevance":[{"instrument":"instrument:sap-api-policy-v4-2026a","prominence":"prominent","sections":["1.1","1.2","2.2.2"],"applies_when":"An MCP server calls ADT or another SAP API of a running system for an agent.","note":"An agent that plans and executes ADT calls is the case section 2.2.2 names. Check that the endpoints are published for the intended use, and that the design runs within a pathway SAP identifies for it.","applies_to":{"ecosystems":["abap"]},"sources":[{"url":"https://help.sap.com/doc/sap-api-policy/latest/en-US/API_Policy_latest.pdf","title":"SAP API Policy v.4.2026a","checked":"2026-10-14","quote":"SAP prohibits API use for: (a) interaction or integration with (semi-) autonomous or generative AI systems that plan, select, or execute sequences of API calls"}]}]},"sap_delivery":{"door":"cap","all":{"built_in":[],"documented_pattern":[],"announced":[],"packages":[{"ref":"artifact:cap-js-mcp-server","name":"@cap-js/mcp-server","json":"/artifacts/cap-js-mcp-server.json"}]},"by_flavor":{"node":null,"java":null}},"edges":{"use_cases":[{"id":"agent-generates-a-rap-business-object","name":"Generate a RAP business object by prompting an agent","capability":"capability:agent-code-access","ecosystem":"abap","flavors":["abap-cloud"],"outcome":"A developer describes the travel application they want and an agent creates the RAP objects in the ABAP system, instead of printing source for the developer to paste into the editor.","boundary":"Ends at objects created and activated in the system. Publishing the service binding, previewing the SAP Fiori elements app and writing the business logic that follows are separate steps, and the ABAP Flight Reference Scenario is assumed to be in the system already.","origin":"Editorial hypothesis, taken from SAP's own RAP130 hands-on session, which is built around this outcome.","requirement_dimensions":["Which system: SAP BTP ABAP environment, SAP S/4HANA Cloud Public Edition, SAP S/4HANA Cloud Private Edition, or a system that is none of these.","Whether SAP Joule for developers, ABAP AI capabilities is enabled on that system.","Whether the agent runs in a developer's editor session or headless.","Whether an experimental feature may be used on the system at all."],"contributions":[{"ref":"artifact:sap-adt-mcp-server","role":"generator surface","state":"conditional","description":"Puts SAP's own ABAP RAP generators in front of the agent as MCP tools, so the objects come out of the generator rather than out of the model. The documented set names `abap_generators-list_generators`, `abap_generators-get_schema` and `abap_generators-generate_objects`, with `abap_activate-objects` to activate the result and `abap_transport-create` to open the transport it needs.","conditions":["ADT for VS Code is running with a destination active in the workspace; the server does not start without one.","The system is one SAP names as currently supported: SAP BTP ABAP environment, SAP S/4HANA Cloud Public Edition or SAP S/4HANA Cloud Private 2025 Edition.","SAP Joule for developers, ABAP AI capabilities is enabled on that system.","SAP calls the server an experimental feature that is not intended for productive use, which is a decision about the system it is pointed at rather than about the tool."],"remaining_work":"The developer runs the agent from an editor session of their own and reviews what the generator produced. Nothing in this path runs headless or in a pipeline.","sources":[{"url":"https://raw.githubusercontent.com/SAP-samples/abap-platform-rap130/main/exercises/ex01/README.md","title":"SAP-samples/abap-platform-rap130 — Exercise 1: Enable the ADT MCP Server","checked":"2026-09-19","quote":"| `abap_generators-generate_objects` | **Runs a RAP generator** — the key tool for Exercise 2 |"},{"url":"https://raw.githubusercontent.com/SAP-samples/abap-platform-rap130/main/exercises/ex01/README.md","title":"SAP-samples/abap-platform-rap130 — Exercise 1: Enable the ADT MCP Server","checked":"2026-09-19","quote":"| `abap_activate-objects` | Activates ABAP objects in the backend system |"},{"url":"https://raw.githubusercontent.com/SAP-samples/abap-platform-rap130/main/exercises/ex01/README.md","title":"SAP-samples/abap-platform-rap130 — Exercise 1: Enable the ADT MCP Server","checked":"2026-09-19","quote":"| `abap_transport-create` | Creates a transport request |"},{"url":"https://raw.githubusercontent.com/SAP-samples/abap-platform-rap130/main/exercises/ex01/README.md","title":"SAP-samples/abap-platform-rap130 — Exercise 1: Enable the ADT MCP Server","checked":"2026-09-19","quote":"The MCP server only starts once a destination is active in the workspace."},{"url":"https://raw.githubusercontent.com/SAP-samples/abap-platform-rap130/main/exercises/ex01/README.md","title":"SAP-samples/abap-platform-rap130 — Exercise 1: Enable the ADT MCP Server","checked":"2026-09-19","quote":"The ADT MCP Server is an experimental feature that may change at any time without notice. It is not intended for productive use."},{"url":"https://raw.githubusercontent.com/SAP-samples/abap-platform-rap130/main/README.md","title":"SAP-samples/abap-platform-rap130 — README","checked":"2026-09-19","quote":"SAP BTP ABAP environment, SAP S/4HANA Cloud Public Edition, SAP S/4HANA Cloud Private 2025 Edition are currently supported."},{"url":"https://raw.githubusercontent.com/SAP-samples/abap-platform-rap130/main/README.md","title":"SAP-samples/abap-platform-rap130 — README","checked":"2026-09-19","quote":"imported and SAP Joule for developers, ABAP AI capabilities enabled."}]},{"ref":"artifact:sap-adt-vscode","role":"editor session the agent works inside","state":"conditional","description":"Holds the logged-on ABAP project the server runs against and mounts the system as a virtual workspace filesystem, which is how the agent reads and edits the ABAP files it is generating around. The MCP tools and that filesystem are two halves of one session.","conditions":["A coding agent extension that supports Visual Studio Code's virtual workspace filesystem, which is what lets it call the MCP tools and open the ABAP files at all.","SAP-samples names GitHub Copilot as the primary tested agent; what another agent does with the same filesystem is not stated there."],"remaining_work":"Adding the project, logging on and keeping the session open are the developer's, and they are the reason this answer exists on one machine rather than in a landscape.","sources":[{"url":"https://raw.githubusercontent.com/SAP-samples/abap-platform-rap130/main/exercises/ex01/README.md","title":"SAP-samples/abap-platform-rap130 — Exercise 1: Enable the ADT MCP Server","checked":"2026-09-19","quote":"Any coding agent that supports Visual Studio Code's virtual workspace filesystem is compatible — GitHub Copilot is confirmed; others are also supported."},{"url":"https://raw.githubusercontent.com/SAP-samples/abap-platform-rap130/main/README.md","title":"SAP-samples/abap-platform-rap130 — README","checked":"2026-09-19","quote":"**GitHub Copilot** is the primary tested agent and the one used and recommended for this tutorial."},{"url":"https://raw.githubusercontent.com/SAP-samples/abap-platform-rap130/main/README.md","title":"SAP-samples/abap-platform-rap130 — README","checked":"2026-09-19","quote":"ADT for Visual Studio Code includes the built-in ADT MCP Server."}]},{"ref":"artifact:arc-mcp-arc-1","role":"general ADT surface","state":"conditional","description":"Creates, updates and deletes ABAP source and DDIC metadata with automatic lock and unlock, activates objects and manages CTS transports, under the caller's own SAP user. For RAP it scaffolds the behaviour pool, auto-creating `lhc_*` skeletons before signatures and stubs are injected, so an agent reaches this outcome by writing the behaviour definition, the projection and the service binding around that shell rather than by running a generator over the whole stack.","conditions":["A reachable ABAP system and credentials for it, since this is a proxy in front of ADT rather than a system.","Writes are off by default, so the package the objects go into has to be allowed first."],"remaining_work":"The objects are written rather than generated from a schema, so their shape, their naming and their consistency with the reference scenario are the developer's to review.","sources":[{"url":"https://github.com/arc-mcp/arc-1","title":"arc-1 — README","checked":"2026-09-19","quote":"Create/update/delete ABAP source and DDIC metadata with automatic lock/unlock"},{"url":"https://github.com/arc-mcp/arc-1","title":"arc-1 — README","checked":"2026-09-19","quote":"CTS transport management (list/get/create/release/delete/reassign/release-recursive)"},{"url":"https://raw.githubusercontent.com/arc-mcp/arc-1/main/README.md","title":"arc-mcp/arc-1 — README","checked":"2026-09-19","quote":"RAP behavior-pool scaffolding can auto-create `lhc_*` skeletons before injecting signatures/stubs."},{"url":"https://github.com/arc-mcp/arc-1","title":"arc-1 — README","checked":"2026-09-19","quote":"**Safe by default** — read-only, no free SQL, no table preview, no transport writes, no Git writes."}]}],"unknowns":["Whether any independent ADT MCP server drives the ABAP RAP generators themselves. ARC-1's README names behaviour-pool scaffolding, which produces an implementation skeleton, and names no generator tool of the kind `abap_generators-generate_objects` runs; that is silence about the generators rather than a statement that it has none.","What the generator produces in practice and how much of it is reworked before activation. The workshop drives the generator through an agent and no source retrieved here reports the result.","Whether the ADT MCP Server tool list is complete. SAP-samples heads it \"Key tools available via the ADT MCP Server\", so the nine named tools are a selection rather than a count."],"assessed_at":"2026-09-19","drafted_with_ai":true,"readings":[],"omitted_contributions":0,"assessment_kind":"documented-contributions"},{"id":"agent-changes-abap-in-an-on-premise-system","name":"Let an agent change ABAP in an on-premise system","ecosystem":"abap","flavors":["standard-abap"],"capability":"capability:agent-code-access","outcome":"An agent reads and changes ABAP in a system the customer runs themselves, on the classic development model, and the change is activated there.","boundary":"Ends at the change activated in the system. The network path to it, the Cloud Connector or the RFC route, and the authorisations the agent's user carries are landscape work this task assumes is already done.","origin":"Editorial hypothesis. The ABAP door's coverage names the licensing and landscape question, and the corpus records no task that says what changes when the system is a classic one rather than an ABAP Cloud one.","requirement_dimensions":["Release of the system, since ADT resources differ between an ERP system and an SAP S/4HANA one.","Whether the agent may act under the developer's own SAP user or a technical one.","Whether the connection is a Cloud Connector, an X.509 trust, a direct HTTP route or RFC.","Whether writes are allowed at all, or the agent is read-only on this system."],"contributions":[{"ref":"artifact:arc-mcp-arc-1","role":"ADT proxy with an identity story","state":"conditional","description":"Reaches an on-premise system through the Cloud Connector and forwards the caller's identity end to end with X.509 certificates, so the system sees a real SAP user and its authorisation checks still apply. On that connection it reads, writes and activates source and DDIC metadata and runs syntax check, ABAP Unit and ATC.","conditions":["A Cloud Connector between the server and the system, or an X.509 trust for per-user destinations.","Writes are off by default: the shipped posture is read-only, with no free SQL, no table preview, no transport writes and no git writes until each is turned on with an explicit flag."],"remaining_work":"Deciding which packages the agent may write to, and which of the off-by-default reads to turn on, before any of this happens.","remaining_kinds":["configuration"],"sources":[{"url":"https://github.com/arc-mcp/arc-1","title":"arc-1 — README","checked":"2026-09-19","quote":"**Cloud Connector** — reach on-premise systems through the connectivity proxy"},{"url":"https://github.com/arc-mcp/arc-1","title":"arc-1 — README","checked":"2026-09-19","quote":"**Per-user destinations** — user identity forwarded end-to-end via X.509 certificates for on-premise SAP, or exchanged for an ABAP bearer token for BTP ABAP Environment"},{"url":"https://github.com/arc-mcp/arc-1","title":"arc-1 — README","checked":"2026-09-19","quote":"Syntax check, ABAP Unit tests, ATC code quality"},{"url":"https://github.com/arc-mcp/arc-1","title":"arc-1 — README","checked":"2026-09-19","quote":"Create/update/delete ABAP source and DDIC metadata with automatic lock/unlock"},{"url":"https://raw.githubusercontent.com/arc-mcp/arc-1/main/README.md","title":"arc-mcp/arc-1 — README","checked":"2026-09-19","quote":"**Safe by default** — read-only, no free SQL, no table preview, no transport writes, no Git writes. Enable each capability with explicit `SAP_ALLOW_*` flags"}]},{"ref":"artifact:oisee-vibing-steampunk","role":"ADT bridge on old releases and closed networks","state":"conditional","description":"States any system with ADT switched on from 7.50 upwards, which reaches an ERP system no ABAP Cloud client answers for, and carries a second route for systems where the HTTP path is not available: classic RFC through the gateway port, with `SADT_REST_RFC_ENDPOINT` taking a whole HTTP request so an ADT resource is still reachable. What a given system actually offers varies by release, and `vsp compat` reports that per system rather than assuming it.","conditions":["ADT is enabled on the system.","RAP needs SAP S/4HANA and AMDP needs SAP HANA, so part of the surface is absent on an ERP system.","The RFC route needs the gateway port open instead of ICF, which is a different network decision rather than a fallback that needs no one's approval."],"remaining_work":"Reading `vsp compat` for the system in front of you before planning what the agent is allowed to attempt on it, and deciding whether a production system is one the agent may write to at all.","sources":[{"url":"https://github.com/oisee/vibing-steampunk","title":"vibing-steampunk — README","checked":"2026-09-19","quote":"any system with ADT enabled, 7.50 upwards."},{"url":"https://github.com/oisee/vibing-steampunk","title":"vibing-steampunk — README","checked":"2026-09-19","quote":"The available surface varies by release, and `vsp compat` reports it per system: RAP needs S/4, AMDP needs HANA, and some ADT resources present on S/4 are absent on ERP."},{"url":"https://raw.githubusercontent.com/oisee/vibing-steampunk/main/README.md","title":"oisee/vibing-steampunk — README","checked":"2026-09-19","quote":"`SADT_REST_RFC_ENDPOINT` takes a whole HTTP request, so **any** ADT resource is reachable over the gateway port"},{"url":"https://raw.githubusercontent.com/oisee/vibing-steampunk/main/README.md","title":"oisee/vibing-steampunk — README","checked":"2026-09-19","quote":"a system where ICF is closed, HTTPS terminates somewhere inconvenient, or CSRF and cookies are a fight"},{"url":"https://raw.githubusercontent.com/oisee/vibing-steampunk/main/README.md","title":"oisee/vibing-steampunk — README, Transportable Packages Configuration","checked":"2026-10-18","quote":"Without these flags, operations on transportable packages will be blocked by the safety system."}]},{"ref":"artifact:fr0ster-mcp-abap-adt","role":"the entry that names the oldest systems","state":"conditional","description":"Names on-premise ECC and SAP S/4HANA in its own supported list, and goes below every other entry on this door: legacy systems on a BASIS release under 7.50, where vibing-steampunk's floor sits. It states full create, read, update and delete on ABAP artifacts rather than a read-only posture, and documents two authentication routes it marks as on-premise only, client certificates over mTLS and Kerberos through SPNEGO.","conditions":["Client certificate and Kerberos authentication are documented as on-premise HTTP only, so the route that fits a classic system is not the one that fits a BTP one.","A legacy system under BASIS 7.50 is served by a separate tool set rather than the full one, which the README lists on its own page."],"remaining_work":"Reading which tools the legacy set actually holds for the release in front of you, since the entry's reach below 7.50 is stated as a separate surface rather than the same one.","sources":[{"url":"https://raw.githubusercontent.com/fr0ster/mcp-abap-adt/main/README.md","title":"fr0ster/mcp-abap-adt — README","checked":"2026-09-19","quote":"Works with **On-Premise (ECC/S/4HANA)**, **ABAP Cloud (BTP)**, and **Legacy** systems (BASIS < 7.50)"},{"url":"https://raw.githubusercontent.com/fr0ster/mcp-abap-adt/main/README.md","title":"fr0ster/mcp-abap-adt — README","checked":"2026-09-19","quote":"**Full CRUD** (not read-only): create, read, update, and delete ABAP artifacts"},{"url":"https://raw.githubusercontent.com/fr0ster/mcp-abap-adt/main/README.md","title":"fr0ster/mcp-abap-adt — README","checked":"2026-09-19","quote":"For client certificate (mTLS) authentication — on-prem HTTP only:"},{"url":"https://raw.githubusercontent.com/fr0ster/mcp-abap-adt/main/README.md","title":"fr0ster/mcp-abap-adt — README","checked":"2026-09-19","quote":"- [Legacy System Tools](docs/user-guide/AVAILABLE_TOOLS_LEGACY.md)"}]},{"ref":"artifact:sap-adt-mcp-server","role":"SAP's own server","state":"unknown","description":"SAP names SAP BTP ABAP environment, SAP S/4HANA Cloud Public Edition and SAP S/4HANA Cloud Private 2025 Edition as currently supported. Nothing retrieved here speaks about a classic on-premise system either way, and a list of supported systems is not a statement that the rest are refused.","remaining_work":"Establishing this needs a source that addresses on-premise systems directly. Until there is one, a reader planning for such a system has the independent servers to look at and an open question about SAP's.","sources":[{"url":"https://raw.githubusercontent.com/SAP-samples/abap-platform-rap130/main/README.md","title":"SAP-samples/abap-platform-rap130 — README","checked":"2026-09-19","quote":"SAP BTP ABAP environment, SAP S/4HANA Cloud Public Edition, SAP S/4HANA Cloud Private 2025 Edition are currently supported."}]},{"ref":"artifact:freight-art-abapsmith","role":"the write path with an undo under it","state":"conditional","description":"Writes to the system over ADT with the mode ladder in front and a journal behind: `read` is the default and an absolute ceiling, `edit` allows write, activate and run, and every mutation is recorded as a before and after image before it is attempted, so it can be listed, shown and undone with the exact prior source restored, with drift against the live server detected and refused. The surface reaches the object types a classic system carries beyond source and DDIC — BOPF models, enhancement spots and BAdIs, classic dynpro screens, IMG customizing — and the ones ADT has no write endpoint for run by installing ABAP into a local `$ABAPSMITH_FLUID_API` package. Activation is check-only or armed, single or batched, with ATC and existing ABAP Unit tests runnable on the same connection.","conditions":["An ABAP system with ADT enabled and reachable over HTTP, under a user holding `S_DEVELOP`; a dedicated technical user is what the README suggests.","`ABAP_MODE=edit` or `admin` before anything is written: `read` is the default and no other variable lifts it.","A system that reports itself productive, or whose role the probe could not prove non-productive, is locked read-only with no override, so the target has to be a system whose client category answers the probe."],"remaining_work":"Deciding which packages, object names and transport requests the agent may write to, since those three allowlists pass by default and only the SAP-namespace check stands between an opted-in write and any package. Beyond that, the ladder governs the arguments the server passes, not the ABAP it executes: whatever `abap_run`, `abap_test` or an opted-in `core.eval` does runs under the connected technical user's own SAP authorisations.","remaining_kinds":["configuration"],"sources":[{"url":"https://github.com/Freight-Art/abapsmith","title":"Freight-Art/abapsmith — README, Requirements","checked":"2026-10-18","quote":"An ABAP system with ADT enabled (`/sap/bc/adt/*` reachable over HTTP)"},{"url":"https://github.com/Freight-Art/abapsmith","title":"Freight-Art/abapsmith — README, Configure","checked":"2026-10-18","quote":"`ABAP_MODE` is the single permission knob."},{"url":"https://github.com/Freight-Art/abapsmith","title":"Freight-Art/abapsmith — README, Configure","checked":"2026-10-18","quote":"`edit` allows write, activate and run."},{"url":"https://github.com/Freight-Art/abapsmith","title":"Freight-Art/abapsmith — README, Undo","checked":"2026-10-18","quote":"Local write journal: list, show, and undo a mutation, restoring the exact prior source. Drift is detected and refused."},{"url":"https://github.com/Freight-Art/abapsmith","title":"Freight-Art/abapsmith — README, Activate","checked":"2026-10-18","quote":"Check-only or activate, single object or batched."},{"url":"https://raw.githubusercontent.com/Freight-Art/abapsmith/main/doc/SAFETY/safety-gate.md","title":"abapsmith — Safety Gate","checked":"2026-10-18","quote":"`inconclusive` is treated exactly like `productive`: writes are locked out."},{"url":"https://raw.githubusercontent.com/Freight-Art/abapsmith/main/doc/SAFETY/safety-gate.md","title":"abapsmith — Safety Gate","checked":"2026-10-18","quote":"Checks 5, 6 and 7 all pass by default"},{"url":"https://raw.githubusercontent.com/Freight-Art/abapsmith/main/doc/SAFETY/safety-gate.md","title":"abapsmith — Safety Gate","checked":"2026-10-18","quote":"The ladder governs what this server does, not ABAP it executes"},{"url":"https://raw.githubusercontent.com/Freight-Art/abapsmith/main/doc/FLUID-API/README.md","title":"abapsmith — Fluid API","checked":"2026-10-18","quote":"The fluid API is the set of abapsmith functions that only work by installing custom ABAP into the SAP system: IMG customizing write, the DDIC bridge, package delete, report execution, the BOPF runtime test, and the FPM/UI runtime."}]},{"ref":"artifact:aws-modernization-agents-for-sap","role":"bulk conversion against a non-production system, behind a registration gate","state":"conditional","description":"Works on the whole custom code base rather than an object at a time: an agent prompted from Kiro converts ABAP out of an SAP ECC system into S/4HANA-compliant code in bulk, with unit tests generated and run either side of the conversion. The connection is to a development, sandbox or QA system, and converted code reaches production through transport and change management rather than from the agent. Two authentication models are documented, basic auth with one shared SAP service user and principal propagation carrying each caller's own SAP identity into SAP audit records.","conditions":["Registration with AWS: the public repository carries the README and the registration link, and the agents, deployment guides and documentation arrive only once registered.","Kiro or another agentic IDE AWS lists as supported, which is where the agents are prompted, plus an AWS account the agents are deployed into.","A supported SAP NetWeaver version and a network path between the AWS account and the SAP system."],"remaining_work":"Register first. The public repository names no tools and no object types, so what the agent reads, writes or activates in the system is not established by anything readable here, and each agent's own prerequisites are stated in its own repository.","remaining_kinds":["configuration"],"sources":[{"url":"https://github.com/aws-for-sap/Modernization-Agents-for-SAP-on-AWS","title":"aws-for-sap/Modernization-Agents-for-SAP-on-AWS — README, supported use cases","checked":"2026-10-18","quote":"**Make ABAP S/4HANA compliant:** convert ABAP code from your SAP ECC system into S/4HANA-compliant code in bulk."},{"url":"https://github.com/aws-for-sap/Modernization-Agents-for-SAP-on-AWS","title":"aws-for-sap/Modernization-Agents-for-SAP-on-AWS — README, FAQ 6","checked":"2026-10-18","quote":"Converted code and artifacts are then transported to SAP production system through transport and change management processes, ensuring full governance and control."},{"url":"https://github.com/aws-for-sap/Modernization-Agents-for-SAP-on-AWS","title":"aws-for-sap/Modernization-Agents-for-SAP-on-AWS — README, FAQ 3","checked":"2026-10-18","quote":"Access is provided through a registration page. Once registered, you will receive access to the GitHub repository containing the agents, deployment guides, and documentation."},{"url":"https://github.com/aws-for-sap/Modernization-Agents-for-SAP-on-AWS","title":"aws-for-sap/Modernization-Agents-for-SAP-on-AWS — README, FAQ 7","checked":"2026-10-18","quote":"A supported **SAP NetWeaver version** (refer to each agent's documentation for the exact version required)"}]},{"ref":"artifact:erhan-epod-adt-mcp-server","role":"the developer's own Eclipse session as the connection","state":"conditional","description":"Opens no connection of its own: the server runs inside Eclipse and reuses the ADT session of each connected ABAP project, so the agent acts under the developer's logon and the plugin stores and transmits no credentials. On that session it reads source, DDIC objects and short dumps, writes with one call that locks, writes, unlocks and activates, creates objects, opens and releases transport requests, and runs syntax check, ATC and ABAP Unit. Several projects can be connected at once and each tool call names its `systemId`, and access is per system: a connection starts in write, and Toggle Read-Only makes it refuse the 11 write tools and send no write request to SAP.","conditions":["Eclipse 2024-03 or later with SAP ADT installed on Java 21, and an ABAP project that is logged on: a tool returns `The destination with ID <name> is not registered.` when the project has no logon after an Eclipse restart.","The README states the connection as the ADT SNC/SSO session of an Eclipse ABAP project and names no release, edition or system type, so what is reachable is whatever that Eclipse is already connected to.","The server listens on 127.0.0.1 behind a bearer token and answers any request carrying an `Origin` header with HTTP 403, so the agent runs on the developer's machine."],"remaining_work":"Deciding which of the connected systems stays in write mode, since a new connection starts in write and the mode is stored per project. The session is a developer's Eclipse, so nothing on this path runs in a pipeline.","remaining_kinds":["configuration"],"sources":[{"url":"https://git.epod.dev/erhan/epod-adt-mcp-updatesite","title":"EPOD ADT MCP Server — README, Setup","checked":"2026-10-23","quote":"The plugin reuses each project's existing ADT session — no password prompt."},{"url":"https://git.epod.dev/erhan/epod-adt-mcp-updatesite","title":"EPOD ADT MCP Server — README","checked":"2026-10-23","quote":"No credentials are stored or transmitted by the plugin. Authentication is handled transparently by the Eclipse ADT communication framework."},{"url":"https://git.epod.dev/erhan/epod-adt-mcp-updatesite","title":"EPOD ADT MCP Server — README, Requirements","checked":"2026-10-23","quote":"One or more ABAP projects in your Eclipse workspace with active SNC/SSO connections to SAP"},{"url":"https://git.epod.dev/erhan/epod-adt-mcp-updatesite","title":"EPOD ADT MCP Server — README, Read & Write Source","checked":"2026-10-23","quote":"sap_push_source Write source code from context to an ABAP object in SAP — runs the full lock → write → unlock → activate pipeline in one call."},{"url":"https://git.epod.dev/erhan/epod-adt-mcp-updatesite","title":"EPOD ADT MCP Server — README","checked":"2026-10-23","quote":"Connect multiple ABAP projects simultaneously and route each tool call to the right system via a systemId parameter."},{"url":"https://git.epod.dev/erhan/epod-adt-mcp-updatesite","title":"EPOD ADT MCP Server — README, Access Mode","checked":"2026-10-23","quote":"A read-only system refuses the 11 write tools and sends no write request to SAP."},{"url":"https://git.epod.dev/erhan/epod-adt-mcp-updatesite","title":"EPOD ADT MCP Server — README, Why the token and the Origin rejection","checked":"2026-10-23","quote":"The server rejects any request that carries an Origin header with HTTP 403, because a browser always sends one and an MCP client sends none."},{"url":"https://git.epod.dev/erhan/epod-adt-mcp-updatesite/raw/branch/main/install/eclipse.md","title":"EPOD ADT MCP Server — Eclipse mode, Errors","checked":"2026-10-23","quote":"| A tool returns `The destination with ID <name> is not registered.` | The ABAP project has no logon after a restart of Eclipse. | Log on to the project in Eclipse. Call the tool again. |"},{"url":"https://git.epod.dev/erhan/epod-adt-mcp-updatesite/raw/branch/main/install/eclipse.md","title":"EPOD ADT MCP Server — Eclipse mode, Prerequisites","checked":"2026-10-23","quote":"Eclipse runs on Java 21 or later. ADT 3.63.0 needs Java 21."}]}],"unknowns":["Whether SAP's ADT MCP Server runs against a classic on-premise system. The workshop that documents it names three cloud systems as currently supported and addresses no other, and the SAP Help Portal pages for ADT for VS Code were not retrievable on the date of this assessment, so the question is open rather than answered either way.","Whether SAP Joule for developers, ABAP AI capabilities can be enabled on a system that is not one of those three, which decides the question above as much as any technical limit does.","What mario-andreschak/mcp-abap-adt offers on a classic system. Its entry states standard-abap on a quote about RAP behaviour definitions needing roughly NetWeaver 7.54 or SAP S/4HANA, which places a feature rather than the server's reach, so it is left out of the contributions here rather than entered on a claim its README does not make.","Which systems EPOD ADT MCP Server reaches. It names the ADT session of an Eclipse ABAP project over SNC/SSO and no release, edition or system type, so it is entered on the connection it describes and not on a statement about classic systems."],"assessed_at":"2026-10-23","drafted_with_ai":true,"readings":[],"omitted_contributions":0,"assessment_kind":"documented-contributions"}],"shared_tasks":[],"related_tasks":[],"options":[{"ref":"artifact:abap2ui5-mcp-server","name":"@abap2ui5/mcp-server","json":"/artifacts/abap2ui5-mcp-server.json","ecosystem":"abap","origin_ring":"community-org"},{"ref":"artifact:cap-js-mcp-server","name":"@cap-js/mcp-server","json":"/artifacts/cap-js-mcp-server.json","ecosystem":"cap","origin_ring":"sap-official"},{"ref":"artifact:babamba2-abap-mcp-adt-powerup","name":"@mcp-abap-adt/core","json":"/artifacts/babamba2-abap-mcp-adt-powerup.json","ecosystem":"abap","origin_ring":"independent"},{"ref":"artifact:sap-ux-fiori-mcp-server","name":"@sap-ux/fiori-mcp-server","json":"/artifacts/sap-ux-fiori-mcp-server.json","ecosystem":"ui5","origin_ring":"sap-official"},{"ref":"artifact:sap-mdk-mcp-server","name":"@sap/mdk-mcp-server","json":"/artifacts/sap-mdk-mcp-server.json","ecosystem":"btp","origin_ring":"sap-official"},{"ref":"artifact:ui5-mcp-server","name":"@ui5/mcp-server","json":"/artifacts/ui5-mcp-server.json","ecosystem":"ui5","origin_ring":"sap-official"},{"ref":"artifact:aws-abap-accelerator","name":"ABAP Accelerator MCP Server","json":"/artifacts/aws-abap-accelerator.json","ecosystem":"abap","origin_ring":"partner"},{"ref":"artifact:ysichov-abap-ai-code","name":"ABAP AI Code","json":"/artifacts/ysichov-abap-ai-code.json","ecosystem":"abap","origin_ring":"independent"},{"ref":"artifact:sap-adt-vscode","name":"ABAP Development Tools for VS Code","json":"/artifacts/sap-adt-vscode.json","ecosystem":"abap","origin_ring":"sap-official"},{"ref":"artifact:marcellourbani-vscode-abap-remote-fs","name":"ABAP remote filesystem","json":"/artifacts/marcellourbani-vscode-abap-remote-fs.json","ecosystem":"abap","origin_ring":"independent"},{"ref":"artifact:vaibhavgoel-github-1986-abap-adt-cli","name":"abap-adt-cli","json":"/artifacts/vaibhavgoel-github-1986-abap-adt-cli.json","ecosystem":"abap","origin_ring":"independent"},{"ref":"artifact:ysichov-abap-ai-code-tools","name":"ABAP-AI-CODE-TOOLS","json":"/artifacts/ysichov-abap-ai-code-tools.json","ecosystem":"abap","origin_ring":"independent"},{"ref":"artifact:saurabhvc-abapdocmcp","name":"ABAPDocMCP","json":"/artifacts/saurabhvc-abapdocmcp.json","ecosystem":"abap","origin_ring":"independent"},{"ref":"artifact:nicohern-abapilot-mcp","name":"ABAPilot","json":"/artifacts/nicohern-abapilot-mcp.json","ecosystem":"abap","origin_ring":"independent"},{"ref":"artifact:freight-art-abapsmith","name":"abapsmith","json":"/artifacts/freight-art-abapsmith.json","ecosystem":"abap","origin_ring":"independent"},{"ref":"artifact:sap-adt-mcp-server","name":"ADT MCP Server","json":"/artifacts/sap-adt-mcp-server.json","ecosystem":"abap","origin_ring":"sap-official"},{"ref":"artifact:hochfrequenz-aibap-mcp","name":"aibap.mcp","json":"/artifacts/hochfrequenz-aibap-mcp.json","ecosystem":"abap","origin_ring":"independent"},{"ref":"artifact:arc-mcp-arc-1","name":"arc-1","json":"/artifacts/arc-mcp-arc-1.json","ecosystem":"abap","origin_ring":"independent"},{"ref":"artifact:abat-tao-arc-1-bopf-enh","name":"arc-1-bopf-enh","json":"/artifacts/abat-tao-arc-1-bopf-enh.json","ecosystem":"abap","origin_ring":"independent"},{"ref":"artifact:arc-mcp-arc-1-lsp","name":"arc-1-lsp","json":"/artifacts/arc-mcp-arc-1-lsp.json","ecosystem":"abap","origin_ring":"independent"},{"ref":"artifact:arc-mcp-arc1-abap-bridge","name":"arc1-abap-bridge","json":"/artifacts/arc-mcp-arc1-abap-bridge.json","ecosystem":"abap","origin_ring":"independent"},{"ref":"artifact:arc-mcp-arc1-adt-ext","name":"arc1-adt-abap-mcp-ext","json":"/artifacts/arc-mcp-arc1-adt-ext.json","ecosystem":"abap","origin_ring":"independent"},{"ref":"artifact:ktaubmann-bella","name":"Bella","json":"/artifacts/ktaubmann-bella.json","ecosystem":"abap","origin_ring":"independent"},{"ref":"artifact:dnic-dev-bw-modeling-mcp","name":"bw-modeling-mcp","json":"/artifacts/dnic-dev-bw-modeling-mcp.json","ecosystem":"btp","origin_ring":"independent"},{"ref":"artifact:automatizatodo-capforge","name":"capforge","json":"/artifacts/automatizatodo-capforge.json","ecosystem":"cap","origin_ring":"independent"},{"ref":"artifact:chandrashekhar-mahajan-abap-mcp-server","name":"chandrashekhar-mahajan/abap-mcp-server","json":"/artifacts/chandrashekhar-mahajan-abap-mcp-server.json","ecosystem":"abap","origin_ring":"independent"},{"ref":"artifact:silvius1996-claude-sap-kit","name":"claude-sap-kit","json":"/artifacts/silvius1996-claude-sap-kit.json","ecosystem":"abap","origin_ring":"independent"},{"ref":"artifact:dassianinc-dassian-adt","name":"dassian-adt","json":"/artifacts/dassianinc-dassian-adt.json","ecosystem":"abap","origin_ring":"independent"},{"ref":"artifact:erhan-epod-adt-mcp-server","name":"EPOD ADT MCP Server","json":"/artifacts/erhan-epod-adt-mcp-server.json","ecosystem":"abap","origin_ring":"independent"},{"ref":"artifact:datazoode-erpl-adt","name":"erpl-adt","json":"/artifacts/datazoode-erpl-adt.json","ecosystem":"abap","origin_ring":"independent"},{"ref":"artifact:fgalastri-mcp-abap","name":"fgalastri/MCP_ABAP","json":"/artifacts/fgalastri-mcp-abap.json","ecosystem":"abap","origin_ring":"independent"},{"ref":"artifact:fr0ster-mcp-abap-adt","name":"fr0ster/mcp-abap-adt","json":"/artifacts/fr0ster-mcp-abap-adt.json","ecosystem":"abap","origin_ring":"independent"},{"ref":"artifact:andre-schaerpf-hammer","name":"Hammer","json":"/artifacts/andre-schaerpf-hammer.json","ecosystem":"abap","origin_ring":"independent"},{"ref":"artifact:yannick-thirion-klystron","name":"Klystron","json":"/artifacts/yannick-thirion-klystron.json","ecosystem":"abap","origin_ring":"independent"},{"ref":"artifact:maherd18-sap-mcp-server","name":"Maherd18/sap-mcp-server","json":"/artifacts/maherd18-sap-mcp-server.json","ecosystem":"abap","origin_ring":"independent"},{"ref":"artifact:mario-andreschak-mcp-abap-adt-api","name":"mcp-abap-abap-adt-api","json":"/artifacts/mario-andreschak-mcp-abap-adt-api.json","ecosystem":"abap","origin_ring":"independent"},{"ref":"artifact:mario-andreschak-mcp-abap-adt","name":"mcp-abap-adt","json":"/artifacts/mario-andreschak-mcp-abap-adt.json","ecosystem":"abap","origin_ring":"independent"},{"ref":"artifact:aws-modernization-agents-for-sap","name":"Modernization Agents for SAP on AWS","json":"/artifacts/aws-modernization-agents-for-sap.json","ecosystem":"abap","origin_ring":"partner"},{"ref":"artifact:yassinbahri-pyrfc-mcp","name":"pyrfc-mcp","json":"/artifacts/yassinbahri-pyrfc-mcp.json","ecosystem":"abap","origin_ring":"independent"},{"ref":"artifact:sap-joule-for-developers","name":"SAP Joule for Developers, ABAP AI capabilities","json":"/artifacts/sap-joule-for-developers.json","ecosystem":"abap","origin_ring":"sap-official"},{"ref":"artifact:muhammad-abdullah333-sap-mcp-bridge","name":"SAP MCP Connection Manager","json":"/artifacts/muhammad-abdullah333-sap-mcp-bridge.json","ecosystem":"abap","origin_ring":"independent"},{"ref":"artifact:grknylmz-sap-ai-dev-toolkit","name":"sap-ai-dev-toolkit","json":"/artifacts/grknylmz-sap-ai-dev-toolkit.json","ecosystem":"abap","origin_ring":"independent"},{"ref":"artifact:marcellourbani-sapdumpmcp","name":"sapdumpmcp","json":"/artifacts/marcellourbani-sapdumpmcp.json","ecosystem":"abap","origin_ring":"independent"},{"ref":"artifact:skybuffer-ai-mcp-server","name":"Skybuffer AI MCP server","json":"/artifacts/skybuffer-ai-mcp-server.json","ecosystem":"abap","origin_ring":"independent"},{"ref":"artifact:ysichov-vertex","name":"VERTEX","json":"/artifacts/ysichov-vertex.json","ecosystem":"abap","origin_ring":"independent"},{"ref":"artifact:oisee-vibing-steampunk","name":"vibing-steampunk","json":"/artifacts/oisee-vibing-steampunk.json","ecosystem":"abap","origin_ring":"independent"},{"ref":"artifact:workskong-mcp-abap-adt","name":"workskong/mcp-abap-adt","json":"/artifacts/workskong-mcp-abap-adt.json","ecosystem":"abap","origin_ring":"independent"},{"ref":"artifact:f-wer-zarc1-extension-forms","name":"ZARC1_EXTENSION_FORMS","json":"/artifacts/f-wer-zarc1-extension-forms.json","ecosystem":"abap","origin_ring":"independent"}],"samples":[{"ref":"artifact:arc-mcp-arc-1-extension-sample","name":"arc-1-extension-sample","json":"/artifacts/arc-mcp-arc-1-extension-sample.json"},{"ref":"artifact:marianfoo-local-llm-client-for-sap-consultants-librechat","name":"local-llm-client-for-sap-consultants-librechat","json":"/artifacts/marianfoo-local-llm-client-for-sap-consultants-librechat.json"},{"ref":"artifact:sap-samples-fiori-mcp-server-hands-on","name":"SAP-samples/fiori-mcp-server-hands-on","json":"/artifacts/sap-samples-fiori-mcp-server-hands-on.json"},{"ref":"artifact:sap-samples-teched2025-ca261","name":"SAP-samples/teched2025-CA261","json":"/artifacts/sap-samples-teched2025-ca261.json"},{"ref":"artifact:sap-samples-ui5con-2026-fiori-mcp-server","name":"SAP-samples/ui5con-2026-fiori-mcp-server","json":"/artifacts/sap-samples-ui5con-2026-fiori-mcp-server.json"},{"ref":"artifact:sap-samples-teched2025-ad162","name":"teched2025-AD162","json":"/artifacts/sap-samples-teched2025-ad162.json"},{"ref":"artifact:sap-samples-wdf2025-fiori-innov-day-mcp-server","name":"wdf2025-fiori-innov-day-mcp-server","json":"/artifacts/sap-samples-wdf2025-fiori-innov-day-mcp-server.json"}],"explained_by":[{"ref":"content:devtoberfest-2026-ai-assisted-sap-development-with-mcp","name":"AI-assisted SAP development with MCP","json":"/content/devtoberfest-2026-ai-assisted-sap-development-with-mcp.json"},{"ref":"content:abap-mcp-let-ai-do-real-development-in-your-sap-system","name":"ABAP + MCP: Let AI Do Real Development in Your SAP System","json":"/content/abap-mcp-let-ai-do-real-development-in-your-sap-system.json"},{"ref":"content:abap-development-tools-for-visual-studio-code-version-1-1-released","name":"ABAP development tools for Visual Studio Code: Version 1.1 released","json":"/content/abap-development-tools-for-visual-studio-code-version-1-1-released.json"},{"ref":"content:how-to-connect-claude-code-to-abap-with-zero-config-mcp","name":"How to Connect Claude Code to ABAP with Zero-Config MCP","json":"/content/how-to-connect-claude-code-to-abap-with-zero-config-mcp.json"},{"ref":"content:using-claude-for-sap-abap-development-on-rfc-only-saprouter-systems-even-ecc-r-3","name":"Using Claude for SAP ABAP development on RFC-only / SAProuter systems (even ECC R/3)","json":"/content/using-claude-for-sap-abap-development-on-rfc-only-saprouter-systems-even-ecc-r-3.json"},{"ref":"content:the-future-of-abap-is-here-vs-code-adt-zero-config-mcp-and-ai-co-pilots","name":"The Future of ABAP is Here: VS Code ADT, Zero-Config MCP, and AI Co-pilots","json":"/content/the-future-of-abap-is-here-vs-code-adt-zero-config-mcp-and-ai-co-pilots.json"},{"ref":"content:arc-1-with-copilot-studio-sap-system-context-beyond-developers","name":"ARC-1 with Copilot Studio: SAP System Context Beyond Developers","json":"/content/arc-1-with-copilot-studio-sap-system-context-beyond-developers.json"},{"ref":"content:introducing-arc-1-a-secure-adt-mcp-server-for-enterprise-sap-development","name":"Introducing ARC-1: A Secure ADT MCP Server for Enterprise SAP Development","json":"/content/introducing-arc-1-a-secure-adt-mcp-server-for-enterprise-sap-development.json"},{"ref":"content:abap-and-agentic-ai-the-hidden-problem-in-real-projects","name":"ABAP and Agentic AI: The Hidden Problem in Real Projects","json":"/content/abap-and-agentic-ai-the-hidden-problem-in-real-projects.json"},{"ref":"content:how-i-use-ai-for-development-and-why-context-matters","name":"How I Use AI for Development and Why Context Matters","json":"/content/how-i-use-ai-for-development-and-why-context-matters.json"},{"ref":"content:claude-ported-abap-functions-to-new-api","name":"Claude ported ABAP functions to new API","json":"/content/claude-ported-abap-functions-to-new-api.json"},{"ref":"content:claude-code-via-mcp-poor-man-s-joule-or-a-practical-tool","name":"Claude Code via MCP: Poor man's Joule, or a practical tool?","json":"/content/claude-code-via-mcp-poor-man-s-joule-or-a-practical-tool.json"},{"ref":"content:building-an-enterprise-ready-sap-ai-agent-with-open-source","name":"Building an Enterprise-Ready SAP AI Agent with Open Source","json":"/content/building-an-enterprise-ready-sap-ai-agent-with-open-source.json"},{"ref":"content:unlocking-mcp-servers-in-bas-right-now","name":"Don't Wait for SAP: Unlocking MCP Servers in BAS Right Now","json":"/content/unlocking-mcp-servers-in-bas-right-now.json"},{"ref":"content:building-a-cap-service-with-cds-mcp-and-cline","name":"Building a CAP service with cds‑mcp and Cline — HANDS‑ON SUPER BASIC GUIDE [ with screenshots ] 🍌","json":"/content/building-a-cap-service-with-cds-mcp-and-cline.json"},{"ref":"content:evaluating-saps-new-mcp-servers-ui5-cap-fiori-tools","name":"Evaluating SAP’s new MCP servers: UI5, CAP, and Fiori tools in practice","json":"/content/evaluating-saps-new-mcp-servers-ui5-cap-fiori-tools.json"},{"ref":"content:first-release-of-the-sap-fiori-mcp-server","name":"SAP Fiori Tools Update – First Release of the SAP Fiori MCP Server for Agentic AI","json":"/content/first-release-of-the-sap-fiori-mcp-server.json"},{"ref":"content:give-your-ai-agent-some-tools-introducing-the-ui5-mcp-server","name":"Give Your AI Agent Some Tools: Introducing the UI5 MCP Server","json":"/content/give-your-ai-agent-some-tools-introducing-the-ui5-mcp-server.json"},{"ref":"content:introducing-the-mcp-server-for-cap","name":"Boost your CAP Development with AI: Introducing the MCP Server for CAP","json":"/content/introducing-the-mcp-server-for-cap.json"},{"ref":"content:ac-agentic-engineering-for-sap-btp-extensions","name":"Agentic Engineering for SAP BTP Extensions","json":"/content/ac-agentic-engineering-for-sap-btp-extensions.json"},{"ref":"content:patterns-for-using-llms-in-abap-development","name":"Patterns for using LLMs in ABAP development","json":"/content/patterns-for-using-llms-in-abap-development.json"},{"ref":"content:teched-2026-ct1239","name":"AI-assisted full stack development using model context protocol servers","json":"/content/teched-2026-ct1239.json"},{"ref":"content:teched-2026-jw262","name":"OData to outcomes—Build AI-enabled SAP Fiori apps using SAP Fiori elements","json":"/content/teched-2026-jw262.json"},{"ref":"content:teched-2026-par1102","name":"Spec first: The disciplined way to develop ABAP with agents","json":"/content/teched-2026-par1102.json"}],"normative_context":[{"ref":"instrument:sap-api-policy-v4-2026a","name":"SAP API Policy","json":"/instruments/sap-api-policy-v4-2026a.json","prominence":"prominent","sections":["1.1","1.2","2.2.2"]}]}}