Skip to content
MCP server

ARC-1

MCP server letting AI assistants read and edit SAP ABAP systems via ADT, with admin safety

Runs locallyStatus and history
Install
Pricing
Open source
Platforms
CLI, vscode, API
Runs
Locally
Version
1.10.1
Listing updated
today

Similar MCP servers

About ARC-1

ARC-1 is an open-source MCP server for developer tools. It runs locally on your machine and is started by your AI client.

The README describes ARC-1 as a TypeScript MCP server that turns AI tool calls into requests against SAP ABAP Development Tools REST APIs, so an assistant can browse, search and edit ABAP code on an SAP system. It is distributed as an npm package and a Docker image, and the docs say it works with Claude, GitHub Copilot, VS Code and Copilot Studio.

The server starts read-only. Writes, table preview, freestyle SQL, transport changes and Git operations each need a separate opt-in environment variable, and writes are limited to $TMP and Z packages unless an admin widens the package allowlist. Every tool call is audited against the user's identity, and per-user scopes can be applied through XSUAA, OIDC or API-key profiles.

The main audience is SAP ABAP developers and the teams that run their systems, including those deploying to SAP BTP or on-premise. The docs also flag that using table data or SQL through ADT may fall outside SAP's API policy, so organisations should check their agreements before enabling those features.

Install

Run in a terminal

claude mcp add arc-1 --env SAP_URL='<SAP_URL>' --env SAP_USER='<SAP_USER>' --env SAP_PASSWORD='<SAP_PASSWORD>' -- npx -y arc-1

Add to claude_desktop_config.json

{
  "mcpServers": {
    "arc-1": {
      "command": "npx",
      "args": [
        "-y",
        "arc-1"
      ],
      "env": {
        "SAP_URL": "<SAP_URL>",
        "SAP_USER": "<SAP_USER>",
        "SAP_PASSWORD": "<SAP_PASSWORD>"
      }
    }
  }
}

Add to ~/.cursor/mcp.json

{
  "mcpServers": {
    "arc-1": {
      "command": "npx",
      "args": [
        "-y",
        "arc-1"
      ],
      "env": {
        "SAP_URL": "<SAP_URL>",
        "SAP_USER": "<SAP_USER>",
        "SAP_PASSWORD": "<SAP_PASSWORD>"
      }
    }
  }
}

Add to .vscode/mcp.json

{
  "servers": {
    "arc-1": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "arc-1"
      ],
      "env": {
        "SAP_URL": "<SAP_URL>",
        "SAP_USER": "<SAP_USER>",
        "SAP_PASSWORD": "<SAP_PASSWORD>"
      }
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "arc-1": {
      "command": "npx",
      "args": [
        "-y",
        "arc-1"
      ],
      "env": {
        "SAP_URL": "<SAP_URL>",
        "SAP_USER": "<SAP_USER>",
        "SAP_PASSWORD": "<SAP_PASSWORD>"
      }
    }
  }
}

Add to your client's MCP settings (most use this shape)

{
  "mcpServers": {
    "arc-1": {
      "command": "npx",
      "args": [
        "-y",
        "arc-1"
      ],
      "env": {
        "SAP_URL": "<SAP_URL>",
        "SAP_USER": "<SAP_USER>",
        "SAP_PASSWORD": "<SAP_PASSWORD>"
      }
    }
  }
}

Using several servers? Build one config file with the MCP config generator.

Configuration

  • SAP_URLSAP system URL (e.g., http://host:50000)Required
  • SAP_USERSAP usernameRequired
  • SAP_PASSWORDSAP passwordRequired
  • SAP_CLIENTSAP client number
  • SAP_LANGUAGESAP logon language
  • SAP_INSECURESkip TLS certificate verification
  • SAP_ALLOW_WRITESAllow ABAP object mutations (safe default: false)
  • SAP_URLSAP system URL (e.g., http://host:50000)Required
  • SAP_USERSAP usernameRequired
  • SAP_PASSWORDSAP passwordRequired
  • SAP_CLIENTSAP client number
  • SAP_LANGUAGESAP logon language
  • SAP_INSECURESkip TLS certificate verification
  • SAP_ALLOW_WRITESAllow ABAP object mutations (safe default: false)
  • SAP_TRANSPORTMCP transport (Docker defaults to http-streamable, set to stdio for local MCP clients)

Tools this server provides (12)

Taken from the project documentation; the running server may differ.

SAPRead
Reads ABAP source, table data, CDS views and other SAP objects.
SAPSearch
Searches for objects and full-text source code across the system.
SAPWrite
Creates, updates and deletes ABAP source and DDIC metadata with lock handling.
SAPActivate
Activates single or batch ABAP objects and publishes OData service bindings.
SAPNavigate
Provides go-to-definition, find references and code completion.
SAPQuery
Reads saved SAPscript texts or runs ABAP SQL, each behind its own opt-in.
SAPTransport
Manages CTS transport requests, including listing, creating and releasing.
SAPGit
Runs Git-based ABAP workflows across gCTS and abapGit.
SAPContext
Returns dependency information, where-used results and CDS impact analysis.
SAPLint
Runs local ABAP lint and ADT pretty-printing.
SAPDiagnose
Runs syntax checks, ABAP Unit, ATC, short dump and trace diagnostics.
SAPManage
Handles feature probing, cache statistics, package operations and FLP helpers.

What it does

Twelve intent-based tools
Exposes SAP operations such as reading source, searching, writing objects, activating, running ABAP Unit and transport management as twelve grouped tools.
Read-only by default
Writes, data preview, SQL, transport writes and Git writes are all off until an admin sets the matching SAP_ALLOW flag.
Package-restricted writes
Write operations can be limited to $TMP, Z* or a custom package pattern via an allowlist.
Per-user audit and scopes
Tool calls are logged with the caller's identity and can be narrowed with XSUAA roles, OIDC tokens or API-key profiles.
Object caching
Source reads are cached in memory or SQLite and revalidated with ETag conditional requests to reduce repeated SAP calls.
Startup feature detection
Probes the SAP system at startup to detect BTP versus on-premise, RAP, gCTS and abapGit availability and adjusts tool definitions.

Good for

  • Letting an AI assistant read and explain existing ABAP classes and programs on an SAP system
  • Creating or changing Z-package objects with AI help while keeping writes restricted to a package allowlist
  • Running syntax checks, ABAP Unit tests and ATC checks from an assistant during development
  • Reviewing transport requests and CTS release status from within an MCP client
  • Connecting GitHub Copilot or Copilot Studio to an SAP development landscape through HTTP streamable mode

Pricing

Open source

MIT-licensed open source, self-hosted via npm or Docker.

Prices change. Check docs.arc-1-mcp.com before you buy.

ARC-1 FAQ

How do I install ARC-1?

The README gives npx arc-1@latest as the direct run command, with a Docker image at ghcr.io/arc-mcp/arc-1 and a Claude Desktop .mcpb bundle on the releases page.

Are writes enabled by default?

No. The docs say ARC-1 is read-only by default, and writes, table previews, freestyle SQL and transport mutations each require an explicit opt-in flag.

Which license does ARC-1 use?

The website and README both state the MIT license.

Does ARC-1 work with BTP ABAP Environment?

Yes. The docs describe a service-key OAuth flow for local BTP ABAP development and a BTP Destination setup for deployed servers.

Is ARC-1 free?

Yes. ARC-1 is open source, so you can use and self-host it for free.

How do I add ARC-1 to Claude Code?

Run this command in your terminal: claude mcp add arc-1 --env SAP_URL='<SAP_URL>' --env SAP_USER='<SAP_USER>' --env SAP_PASSWORD='<SAP_PASSWORD>' -- npx -y arc-1

What are the best alternatives to ARC-1?

The closest alternatives to ARC-1 are SAP ABAP MCP, Copado Agentia, ArborNote MCP by usefulapi, AnythingMCP and mcpcut.

Where this comes from

  • Description: written from the project's README, the project's website and its MCP Registry entry.
  • Install steps: from the official MCP Registry entry.

How AIPoweredBot checks servers