ARC 1
Expose SAP ABAP system operations to Claude Code or Cursor so agents can read and optionally mutate ABAP objects with guardrailed credentials.
Overview
io.github.marianfoo/arc-1 is a MCP server for the Build phase that connects coding agents to SAP ABAP systems with configurable read and optional write access.
What is this MCP server?
- ARC-1 npm package arc-1 version 0.9.8 with npx runtime hint and stdio MCP transport
- Connects via SAP_URL, SAP_USER, SAP_PASSWORD, SAP_CLIENT (default 100), SAP_LANGUAGE (default EN)
- SAP_INSECURE toggle for TLS verification skip in lab systems; SAP_ALLOW_WRITES defaults false for safe read-first ABAP a
- Enterprise SAP ABAP focus for agent-assisted inspection and controlled object changes
- Environment-driven configuration suitable for solo consultants bridging AI editors and customer landscapes
- Package arc-1 version 0.9.8 on npm with npx runtimeHint
- Six documented SAP environment variables including required URL, user, and password
- SAP_ALLOW_WRITES defaults to false for mutation safety
What problem does it solve?
Working on SAP ABAP means constantly exporting metadata and code into chats because your agent cannot reach the system directly.
Who is it for?
SAP developers, freelancers, and small teams who use Claude Code or Cursor and need governed agent access to a specific ABAP landscape.
Skip if: Solo web-only builders with no SAP estate, or teams that forbid agent connections to ERP credentials regardless of write locks.
What do I get? / Deliverables
After you configure SAP credentials and add ARC-1 to MCP, your agent can query and work with ABAP objects under your SAP_ALLOW_WRITES safety policy.
- MCP tools backed by live SAP ABAP connectivity
- Configurable read-first access with optional writes via SAP_ALLOW_WRITES
- Documented environment contract for SAP_CLIENT, language, and TLS behavior
Recommended MCP Servers
Journey fit
SAP ABAP connectivity is a Build concern because it wires your agent into enterprise ERP backends during implementation and maintenance. integrations is the right shelf for MCP servers that authenticate to SAP_URL and orchestrate ABAP-level work rather than generic UI coding.
How it compares
SAP ABAP systems MCP bridge, not SAP documentation search or generic SQL database tooling.
Common Questions / FAQ
Who is io.github.marianfoo/arc-1 for?
It is for SAP ABAP practitioners who want MCP-enabled agents to interact with their SAP system using explicit URL and logon environment variables.
When should I use io.github.marianfoo/arc-1?
Use it during build or integration tasks when repeated ABAP lookups or controlled changes are faster through agent tools than GUI copy-paste.
How do I add io.github.marianfoo/arc-1 to my agent?
Set SAP_URL, SAP_USER, SAP_PASSWORD, and optional SAP_CLIENT, SAP_LANGUAGE, SAP_INSECURE, and SAP_ALLOW_WRITES, then add npx arc-1 (0.9.8) as an stdio MCP server.