Agent access to ABAP code
There is no filesystem to read: the source lives in a system reachable by default through ADT resourcesADT resourcesThe HTTP endpoint an ABAP system exposes as the adt ICF service under /sap/bc/adt, so a client outside the system can reach development objects, delivered with the platform rather than installed.sap official, abap, so this is a landscape and licensing question before it is a tooling one. Many MCP servers build towards ADT resourcesADT resourcesThe HTTP endpoint an ABAP system exposes as the adt ICF service under /sap/bc/adt, so a client outside the system can reach development objects, delivered with the platform rather than installed.sap official, abap, but differ in where they run, how they connect and how they authenticate. SAP ships its own servers here, meant to be the default way in. The community ones are further along in features.
Showing artifacts, examples and content with confirmed Standard ABAP applicability. View All ABAP
Overview
No SAP artifact is confirmed here for Standard ABAP.
A Standard ABAP coverage assessment has not been written. View all flavors
Reaches what ADT does not on an on-premise system: an agent connected 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 reads, creates, changes, checks and deletes classic BOPF enhancements of SAP standard business objects and their entities, without BOBX.
Gives the same ADT operations to a person at a shell and to an agent over MCP from one binary, and extends them to BW/4HANA modelling objects that ABAP-only servers do not reach.
Reaches the classic form objects ADT does not list: an agent connected 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 reads and writes SAPscript window texts and Smart Styles, and checks any TADIR object for its existence, package and author.
Executes the ABAP it just wrote through ADT's classrun and returns the console output, so an agent can check a change rather than assert it.
Answers what is in the system with tools shaped for reading, against a sibling server that exposes the lower-level ADT API for editing it.
Supplies source and dictionary context from ECC and on-premise S/4HANA through a vendor backend installed in the system, rather than by speaking ADT from outside.
Adds the parts of a system a developer needs during a post-mortem and ADT does not surface — cluster tables decoded, the application log, spool and job output, variants, test data and the IMG — on top of the usual read, write, test and deploy loop.
Adds five tools to what an agent can reach on a classic ABAP system beyond ADT: submitting a report and reading its ALV as JSON, running a NAST message's print program and fetching the spool PDF, and reading, writing and replacing SmartForms as XML.
Gives a coding assistant object metadata, source code and ST22 short dumps from the system through the same MCP tools, under the developer's own authorizations.
Exposes the system's own objects, checks and transports to an MCP client as typed tools from inside the application server, so an agent reads, writes and activates ABAP under the signed-in user's authorizations and gets each object back as a file in SAP's format.
Runs an LLM's tool calls as ABAP inside the system, reading classes, single methods, programs and pattern matches from the live repository.
A Standard ABAP coverage assessment has not been written. View all flavors
Policy
PolicySAP API Policy 4.2026a§ 1.1, 1.2, 2.2.2AlwaysAn MCP server calls ADT or another SAP API of a running system for an agent.
- § 1.1 Published APIs. Published APIs are made available for the documented purposes identified by SAP, including integration, extensions and data exchange.
- § 1.2 Non-Published APIs. Customer and third-party applications must not access non-published APIs except where documentation permits it or SAP otherwise authorizes it.
- § 2.2.2 AI call sequences and data extraction. Outside SAP-endorsed architectures, data services or expressly identified pathways, the policy prohibits specified agentic API use and systematic or large-scale extraction.
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.
SAP API Policy 4.2026a →Artifacts
Tasks
Let an agent change ABAP in an on-premise system
An agent reads and changes ABAP in a system the customer runs themselves, on the classic development model, and the change is activated there.
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.
arc-1Reaches 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.
fr0ster/mcp-abap-adtNames 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.
vibing-steampunkStates 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.
Content
Details
Coverage
Comparison properties
These are the questions used to compare what the artifacts do. Values come from their documentation and may apply to a particular ecosystem or runtime. Each recorded value in the comparison opens its statement and sources.
For your agent
- Ref
capability:agent-code-access- JSON
- /capabilities/agent-code-access.json
- MCP
- Connecting an agent