Agent access to ABAP code
What an agent can reach here is already narrowed by the release contract: 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 only, and only the objects SAP has released for ABAP Cloud, the same restriction any developer works under. 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 ARC-1 LSParc-1-lspAn edition of ARC-1 that hands every ADT interaction to SAP's own embedded adt-ls language server instead of a hand-rolled HTTP client.independent, abap read and write against exactly that surface — the LSP variant states it covers "Modern ABAP-Cloud types only".
Showing artifacts, examples and content with confirmed ABAP Cloud applicability. View All ABAP
Overview
SAP's own ADT MCP ServerADT MCP ServerSAP's own ADT MCP server, and not a package: a preference inside ABAP Development Tools for VS Code that starts a local HTTP MCP server on a port you choose.sap official, abap, shipped inside ABAP Development Tools for VS CodeABAP Development Tools for VS CodeSAP's ABAP tools in VS Code: editing, debugging, ABAP Unit, ATC and transports for classes, CDS and RAP objects, over RFC to an on-premise or Private Cloud system and HTTP to a cloud one, with Joule's ADT MCP server and code completion behind an AI-unit licence.sap official, abap, 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.
Not covered: 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.
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, ARC-1 LSParc-1-lspAn edition of ARC-1 that hands every ADT interaction to SAP's own embedded adt-ls language server instead of a hand-rolled HTTP client.independent, abap, fr0ster/mcp-abap-adtfr0ster/mcp-abap-adtFull CRUD across on-premise and ABAP Cloud systems, with five authentication methods and three transports: a library under Apache-2.0 and a standalone server under AGPL-3.0-only.independent, abap and @mcp-abap-adt/core@mcp-abap-adt/coreA descendant of the Andreschak and fr0ster servers rebuilt on its own architecture, published as an npm scope and a Claude Code plugin, with Korean and Japanese documentation beside the English.independent, abap state abap-cloud on their own entries; SAP's ADT MCP Server names the same systems in its own documentation.
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
Generate a RAP business object by prompting an agent
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.
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.
arc-1Creates, 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.
Seen working
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