onedevatlasBeta
Browse the atlas
AllABAPCAPUI5BTP
SampleSampletypeA worked example you read or clone. Evidence: it demonstrates, it never provides.See every one →What this type is →independently maintainedindependently maintainedoriginPublished by one person or a small company outside SAP. Says nothing about quality; the readings say that.See every one →

arc-1-extension-sample

A sample arc-1 extension in TypeScript, with no ABAP, whose ten Custom_* tools each show one way the plugin API reaches SAP: ADT and OData reads, an OData write, class and report execution, a custom ICF service and classic RFC.

It is the smoke test for the extension framework of arc-1 (FEAT-61), reported verified live against a real S/4HANA system, and the repository ARC-1's extensions page tells a reader to clone and adapt. Reads go through the gated ctx.http, Custom_RunClass and Custom_RunReport use ARC-1's gated ADT run operations, Custom_CreateSalesOrder writes to OData behind SAP_ALLOW_PLUGIN_RAW_WRITES, and Custom_ReadProgram is a read declared as a JSON manifest in place of code. Three tools drive the translation service of LISA through its custom ICF endpoint. Custom_RfcSystemInfo calls RFC_SYSTEM_INFO over classic RFC with open-rfc, outside ctx.http, and the README lists the eight controls that tool brings itself because ARC-1's write ceiling and package restrictions do not reach the call.

GitHub1 ★

Facts

Last push

Where it sits

Lives in
ABAP
Demonstrates
Agent access to your codeABAPAgent access to your codecapabilityLetting 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.
Requires
arc-1arc-1artifactthe server whose arc-1/public extension API the sample consumes and which loads it with ARC1_PLUGINS
Optional
open-rfcopen-rfcartifactthe SDK-free RFC client the RFC tool dials classic RFC with, pinned to 0.2.3LISALISAartifactthe ABAP ICF service ZCL_I18N_SERVICE the three translation tools post to, imported from LISASAP Connectivity serviceSAP Connectivity serviceartifactthe bound service whose short-lived OAuth token and SOCKS5 proxy carry the RFC call to the on-premise system

Who is behind it

ARC MCPARC MCPOrganisationMaintains this
In the atlas: maintains 9@arc-mcpmaintainerMarian ZeisPersonContributes to this
In the atlas: maintains 35, contributes to 86, wrote 25@marianfoo1 contributor

Before choosing this

Signals

LicenceNo licenseNeither the package manifest nor the repository tree declares a licence

Without a licence the default is all rights reserved. Ask the maintainer, or check for terms stated elsewhere, before depending on it.

Conditions

PracticalFunctional boundary

It consumes the @experimental public API, which the README says may break in any release. The RFC tool dials as one shared technical user with its own credentials, so SAP's log records that user and not the person behind the agent.

What it declares

Every artifact

Type
Sample
Origin
Independently maintained

As a sample

Form
Code snippets

Connections5

Download
arc-1-extension-sample connectionsarc-1-extension-samplePROVIDES→ demonstrates1demonstrates authoredAgent access to your codeNEEDS→ needs1needs stated the server whose `arc-1/public` extension API the sample consumes and which loads it with `ARC1_PLUGINS` arc-mcp/arc-1-extension-sample — README: https://raw.githubusercontent.com/arc-mcp/arc-1-extension-sample/main/README.mdarc-1→ optionally needs3optionally needs stated If: the three translation tools are used the ABAP ICF service `ZCL_I18N_SERVICE` the three translation tools post to, imported from LISA arc-mcp/arc-1-extension-sample — README, Integrating LISA: https://raw.githubusercontent.com/arc-mcp/arc-1-extension-sample/main/README.mdLISAifoptionally needs stated If: `Custom_RfcSystemInfo` is used the SDK-free RFC client the RFC tool dials classic RFC with, pinned to 0.2.3 arc-mcp/arc-1-extension-sample — README, RFC: https://raw.githubusercontent.com/arc-mcp/arc-1-extension-sample/main/README.mdopen-rfcifoptionally needs stated If: the RFC tool runs on Cloud Foundry the bound service whose short-lived OAuth token and SOCKS5 proxy carry the RFC call to the on-premise system arc-mcp/arc-1-extension-sample — README, RFC: https://raw.githubusercontent.com/arc-mcp/arc-1-extension-sample/main/README.mdSAP Connectivity serviceif

README

quoted from arc-mcp/arc-1-extension-sample, read
arc-mcp/arc-1-extension-sample/README.mdOn GitHub

arc-1-extension-sample

A sample ARC-1 extension — the playground for FEAT-61. The default plugin is TypeScript only. The separate forms sample includes an optional ABAP companion.

Consumes the @experimental arc-1/public API. It is the smoke test for the FEAT-61 extension framework (arc-1 docs/research/extension-framework-spec.md). Verified live against a real S/4HANA system — both tiers return real SAP source. The API may break in any release (it declares apiVersion).

excerpt, no licence read, read the rest, on GitHub

Details

Sources3
Added by handdiscovered herechecked
github.com/arc-mcp/arc-1-extension-sampletree, pushes, contributors, CIchecked
README.mdquoted, and what the entry declareschecked

Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.

Compatibility and provenance
discovered viaAdded by hand
first seen in the atlas
ecosystem and domainabap, ai-and-agents
Contributors1
Marian Zeis

From the repository’s contributor list, .

History in the atlas2
  1. Entered by intake from the README, found through ARC-1's extensions page, which links it as the worked sample.
  2. First seen.
For your agent
Ref
artifact:arc-mcp-arc-1-extension-sample
JSON
/artifacts/arc-mcp-arc-1-extension-sample.json
MCP
Connecting an agent