ARC-1 - self-hosted SAP AI gateway

Governed SAP access for enterprise AI

Let teams use AI on SAP systems without turning every laptop into an ungoverned door into production. ARC-1 is a gateway you operate, with SAP identity, authorization, and audit still in control.

MCP is the open protocol for connecting AI assistants to enterprise systems. ARC-1 is the governed SAP implementation for BTP ABAP environment, SAP S/4HANA Cloud Public and Private Edition, and on-prem ABAP from 7.40.

See the executive case Open live demo View GitHub repo

Landscape-ready BTP ABAP, S/4HANA Cloud Public or Private Edition, and on-prem ABAP 7.40+.

Read-only first Writes, SQL, data preview, transports, and Git are explicit opt-ins.

SAP stays in charge Existing SAP identity, authorization, and audit remain the control plane.

Inspectable OSS Public TypeScript code, docs, npm package, Docker image, and CI.

Supported SAP landscapes

One governed MCP layer for modern and classic ABAP systems.

ARC-1 is not tied to one SAP runtime. The same intent tools and safety model cover cloud-first ABAP, public and private S/4HANA Cloud landscapes, and established on-premise systems, with authentication and deployment configured for each environment.

BTP-native

SAP BTP ABAP environment

Connect cloud ABAP development systems with BTP-aware authentication, service-key setup paths, and the same read/write gates used everywhere else.

Public cloud

SAP S/4HANA Cloud Public Edition

Support S/4HANA Public Cloud access through SAP-supported identity and ADT paths while respecting public-cloud boundaries and SAP authorization.

Private cloud

SAP S/4HANA Cloud Private Edition

Use ARC-1 with managed private-cloud systems through central endpoints, network routing, Cloud Connector, and per-user identity where available.

On-prem

ABAP systems from 7.40

Keep classic NetWeaver and S/4HANA on-premise systems in scope, from local smoke tests to shared Docker or BTP-hosted team deployments.

Live demo

Experience ARC-1 workflows without setting up a demo SAP landscape.

The hosted live demo lets teams explore realistic ARC-1 scenarios across VS Code, Claude, Teams, Outlook, Copilot, SharePoint, and GitHub-style workflows. It shows the assistant flow, ARC-1 tool calls, supporting MCP calls, and the evidence history behind each answer before you connect your own SAP system.

Launch live demo Open SharePoint demo Demo source

live-arc-1.arc-1-mcp.com Hosted demo

Teams + SharePoint Business memo to SAP impact chain SharePoint request, ARC-1 dependency evidence, collapsed history.

VS Code SEGW to RAP and UI5 modernization RAP object plan, tool calls, branchable UI target decisions.

Claude SAP dependency graph exploration Graph-first evidence with where-used overlays and validation gates.

Executive case

AI access to SAP without a new shadow integration layer.

ARC-1 gives AI assistants useful SAP context through a controlled gateway instead of unmanaged local scripts, copied credentials, and client-specific integrations. Start read-only, prove the model, then open higher-risk actions only where the operating model supports them.

Own the runtime

ARC-1 is not a hosted black box. Run it where your SAP and AI security posture already belongs: local, Docker, or BTP.

Keep model choice open

Use Claude, Copilot, Joule, Cursor, VS Code, or future MCP clients without inventing a separate SAP access model for each.

Roll out by risk

Keep production read-only, allow sandbox writes selectively, and treat SQL, data preview, transport, and Git actions as separate approvals.

No license lock-in

Free and open source does not mean zero operating cost. It means no per-seat license and an inspectable control plane your team can run.

Why ARC-1

SAP AI needs governed context, not another prompt trick.

SAP development context lives in source objects, packages, transports, dumps, checks, dependencies, release state, and authorizations. ARC-1 gives assistants that context through a small set of intent-based tools with safety gates in front.

Standards-based MCP is the client protocol; SAP ADT remains the system interface.

SAP-native security Server ceiling, user permission, and SAP authorization all have to pass.

Enterprise deployment BTP, XSUAA, Destination Service, Cloud Connector, and audit logging are first-class paths.

Public maintenance Open TypeScript source, public docs, npm release, Docker image, and GitHub Actions.

What ARC-1 is good for

Use cases that matter beyond a developer demo

The first value is read access: current system state, source, metadata, checks, dependencies, dumps, and transport context. Write access can come later, in restricted systems and packages, after the organization is comfortable with the control model.

ABAP development assistance

Read source, search objects, edit methods, activate, run syntax checks, run ABAP Unit, inspect ATC, and keep the AI grounded in the actual SAP system.

Clean Core and modernization

Analyze custom code against release state and SAP guidance, identify direct table usage, build modernization backlogs, and guide SEGW-to-RAP moves.

Architecture and impact analysis

Turn change requests into technical risk views: dependencies, activation order, table impact, transport requirements, and affected objects.

Support and diagnostics

Connect weak tickets to ST22 dumps, source code, gateway messages, traces, package contents, and likely root causes before a developer opens the IDE.

Microsoft 365 and Joule agents

Reuse the same BTP-deployed ARC-1 endpoint from Copilot Studio, Teams, Microsoft 365 Copilot, and Joule Studio without creating a separate SAP access model.

GitHub workflow automation

Give PR checks and AI reviewers live SAP context for ABAP Unit, ATC, activated-source drift checks, and read-only code review.

Evidence, not theater

Real workflows ARC-1 was built around

These examples come from the ARC-1 blog series and demo repositories: impact analysis in Copilot Studio, Clean Core checks, RAP and Fiori elements modernization, and modern UI5 consumption of a generated RAP service.

Copilot Studio impact analysis for an ABAP domain change request — Impact analysis from a SharePoint change request

Copilot Studio clean core readiness analysis with ARC-1 context — Clean Core readiness with system evidence

Fiori elements list report generated from a RAP OData V4 service — SEGW to RAP to Fiori elements modernization

Modern UI5 TypeScript app consuming the new RAP OData V4 service — Modern UI5 TypeScript on top of RAP V4

Security architecture

One controlled SAP access layer. Three gates before action.

ARC-1 can run locally, in Docker, or as a BTP Cloud Foundry app, then connect to BTP ABAP environment, S/4HANA Cloud Public or Private Edition, and on-prem ABAP. The enterprise pattern is central: one endpoint, one safety ceiling, one audit path, and SAP authorizations still deciding what the backend user may do.

ARC-1 on SAP BTP architecture with MCP clients, BTP services, Cloud Connector, and SAP ABAP systems — Recommended operating model: ARC-1 on SAP BTP with XSUAA, Destination Service, Cloud Connector, and per-user SAP identity where possible.

Gate 1

Server ceiling

Admin-controlled flags define what this ARC-1 instance can ever do.

Gate 2

User permission

Scopes, role collections, OIDC claims, or API-key profiles restrict the user.

Gate 3

SAP authorization

SAP still enforces S_DEVELOP, package, transport, table, and system permissions.

Effective permission = server ceiling AND user permission AND SAP authorization

Quickstart

Quickstart first. npx is a smoke test.

SAP URL, client, auth, TLS, and client wiring vary by landscape. The docs cover the read-only first run, Claude install, local development, Docker, BTP deployment, and cloud-specific SAP auth paths.

Quickstart docs Install in Claude Deployment docs

connectivity smoke test

npx arc-1@latest \
  --url https://your-sap-host:44300 \
  --user YOUR_USER \
  --password YOUR_PASS \
  --client 100

ARC-MCP ecosystem

ARC-1 is the flagship. The org is becoming a SAP AI toolkit.

The GitHub organization contains the core server, adjacent runtime pieces, samples, and workflow demos. Labels make maturity explicit so the flagship product stays clearly separated from labs and proofs of concept.

Core product - Stable

The product story is already written in public

ARC-1 grew out of a clear argument: AI in SAP succeeds when context, governance, identity, and workflow quality are treated as architecture. These posts are the best path through that argument.

Context first How I Use AI for Development and Why Context Matters The ABAP gap ABAP and Agentic AI: The Hidden Problem in Real Projects Product thesis Introducing ARC-1: A Secure ADT MCP Server for Enterprise SAP Development Enterprise deployment ARC-1 on SAP BTP: Secure ABAP Agentic Development Beyond the Laptop Business users ARC-1 with Copilot Studio: SAP System Context Beyond Developers SAP-native agents ARC-1 with Joule Studio: Bringing Real ABAP System Context into Joule Modernization From SEGW and Legacy UI5 to RAP with ARC-1 GitHub workflows ABAP Development Automation with ARC-1 and GitHub Workflows Governance A Clearer View of Your SAP Integrations Under the New API Policy

Free, open source, inspectable

Give SAP AI a controlled path to the system it needs to understand.

Start with the repo Install guide