← Back to directory
A

ARC-1

Community
An enterprise MCP server for SAP ABAP systems.
Category
Dev Tools #26 of 438
Stars
★ 215 Very popular
Transport
stdio (local process)
Runtime
Node.js · Docker
Credentials
API key / credential required
License
MIT
Last commit
Tools
12
67FMRS · C

ARC-1 is an MIT-licensed SAP ABAP ADT MCP server with 12 intent-based tools and npm and Docker distributions. The source describes conservative security defaults, but production deployment still requires review of SAP API Policy, authorization, credential protection, and data governance.

Strongest · Security and permissions 16/20 Weakest · Reliability 10/20

Reliability
10/20
Security and permissions
16/20
Maintenance
13/20
Documentation
15/20
Setup experience
13/20
Why each score
Reliability 10/20
The manifest specifies npm and OCI stdio installation paths, versions, and required environment variables. The README claims extensive unit, integration, and E2E coverage and describes startup probing, auth preflight, and rate limiting. However, the actual tests and CI workflows are not included in the supplied source, so tool-list behavior, initialization, error handling, and dependency control cannot be statically verified; the score is reduced under the static calibration.
Security and permissions 16/20
The declared default posture is read-only, with writes, free SQL, table previews, Git, and transport mutations requiring explicit opt-in. The password is marked secret, and the README describes package restrictions, deny lists, authentication modes, audit logging, and rate limiting. Deductions apply because these controls are README claims without implementation or test evidence; SAP_INSECURE permits TLS verification bypass, and per-operation confirmation, data-flow boundaries, and secret-rotation details are not verifiable.
Maintenance 13/20
The project is not archived, uses the MIT license, and identifies a repository, versioning policy, changelog, security policy, and dependency/CodeQL maintenance practices. Points are deducted because commit history, release cadence, issue-response behavior, maintainer identity, and the actual security-response process are not supplied. Stars are not counted, and open-issue count does not establish maintenance quality.
Documentation 15/20
The README covers installation, authentication, deployment topologies, configuration, tool purposes, security defaults, limitations, versioning, and documentation entry points, giving it relatively strong layered coverage. Points are deducted because complete tool parameters, troubleshooting, compatibility boundaries, costs, and practical configuration examples are mainly in external documents not supplied here; the README's feature and test-count claims also cannot be independently verified.
Setup experience 13/20
The manifest offers npm/npx and Docker image paths, stdio transport, SAP connection variables, and security defaults. The README provides entry points for Claude, manual npx use, and team deployment, with reasonable mainstream-client coverage. Points are deducted because no client configuration files, runtime requirements, network or certificate prerequisites, or end-to-end success evidence are provided, and SAP credentials and connectivity still require manual preparation.

Static review · not runListed 2026-08-14

Read the FMRS scoring method →

Fit and risk

What it can accessRuns commands or codeUses the networkConnects to a database

Best for

  • Organizations seeking governed AI-assisted SAP ABAP development
  • Local or BTP deployments using the SAP ADT REST API
  • Teams that want read-only defaults with explicitly controlled write capabilities

Not for

  • General-purpose business-data extraction
  • Production use without SAP authorization, credential, and security review
  • Users who require free SQL, table previews, or write operations to be enabled by default

Required permissions

  • Requires SAP_URL, SAP_USER, and SAP_PASSWORD
  • SAP_CLIENT and SAP_LANGUAGE are optional and have defaults
  • Writing ABAP objects requires explicit SAP_ALLOW_WRITES enablement
  • Table data preview and free SQL require separate explicit environment variables
  • SAP-native authorization still governs relevant SAP operations

Risks and side effects

  • SAP_PASSWORD is a secret credential and must be protected
  • Enabling writes can create, update, or delete ABAP objects
  • Enabling table previews can expose application data
  • Enabling free SQL can execute ad-hoc ABAP SQL
  • SAP_INSECURE skips TLS certificate verification
  • SAP API Policy, SAP agreements, and organizational data-governance requirements should be reviewed before production use

Setup

Before you start

Runtime:Node.js · Docker

SAP_URL required SAP system ADT URL (e.g., http://host:50000); required.
SAP_USER required SAP username; required.
SAP_PASSWORD requiredsecret SAP password; required and secret.
Other optional settings (11)
SAP_CLIENT optional SAP client number, defaults to 100.
SAP_LANGUAGE optional SAP logon language, defaults to EN.
SAP_INSECURE optional Skip TLS certificate verification, defaults to false.
SAP_ALLOW_WRITES optional Allow ABAP object mutations, safe default false.
SAP_TRANSPORT optional MCP transport; Docker defaults to http-streamable, set stdio for local clients.
SAP_ALLOW_DATA_PREVIEW optional Enables SAPRead(type=TABLE_CONTENTS) table preview; off by default.
SAP_ALLOW_FREE_SQL optional Enables freestyle ABAP SQL via SAPQuery; off by default.
SAP_ALLOW_GIT_WRITES optional Enables abapGit/gCTS write operations; off by default.
ARC1_ALLOWED_ORIGINS optional Comma-separated exact-match origins for browser MCP clients; off by default.
ARC1_MCP_HTTP_RATE_LIMIT optional Overrides the MCP HTTP edge rate limit.
ARC1_RATE_LIMIT optional Per-user MCP quota (e.g., 60); off by default, opt-in for multi-user deployments.

Run it with npm: npx arc-1@latest --url https://your-sap-host:44300 --user YOUR_USER. You can also install the latest .mcpb in Claude Desktop or install the arc-1 plugin in Claude Code. The npm setup requires SAP_URL, SAP_USER, and SAP_PASSWORD. SAP_CLIENT defaults to 100, SAP_LANGUAGE defaults to EN, and SAP_ALLOW_WRITES defaults to false. A Docker image is also available; Docker additionally supports SAP_TRANSPORT.

Check that it works

After connecting, check that the 12 SAP* tools (SAPRead, SAPContext, SAPWrite, etc.) appear in the client's tool list, then ask something like "list Z* objects in this SAP system" to prove the ADT connection works.

Troubleshooting

  1. Verify SAP_URL, SAP_USER, SAP_PASSWORD, and SAP_CLIENT
  2. Check that the SAP user has the required ADT and object permissions
  3. Confirm that the target system supports the requested feature; ARC-1 probes and adapts to system capabilities
  4. For failed write, table-preview, free-SQL, Git, or transport operations, check the corresponding explicit enablement flags
  5. For TLS problems, inspect certificate configuration and consider SAP_INSECURE only after understanding the risk
  6. In shared technical-user mode, inspect startup authorization-preflight errors, including 401 or 403 responses

Things to try

Once connected, you can ask your AI assistant things like:

  • Use SAPContext to explain what class ZCL_ORDER does and list its dependencies
  • Use SAPSearch to find ABAP objects with ORDER in their name
  • Use SAPRead to fetch the source of ZCL_ORDER and grep only lines matching get_data
  • Use SAPDiagnose to run a syntax check and ABAP Unit tests on ZCL_ORDER

Tools 12

SAPRead read-only
Reads ABAP source, methods, metadata, table contents, CDS views, service bindings, knowledge-transfer documents, versions, and other supported SAP objects.
SAPSearch read-only
Searches SAP objects and source code across the system.
SAPWrite writes
Creates, updates, or deletes ABAP source and supported DDIC metadata.
SAPActivate writes
Activates individual or batched ABAP objects and publishes or unpublishes OData service bindings.
SAPNavigate read-only
Provides go-to-definition, find-references, and code completion capabilities.
SAPQuery read-only
Executes ABAP SQL and automatically chunks some long literal IN lists.
SAPTransport writes
Manages CTS transports, including listing, creation, release, deletion, reassignment, and recursive release.
SAPGit writes
Supports Git workflows across gCTS and abapGit, including repository, commit, branch, and push operations.
Show 4 more tools
SAPContext read-only
Provides dependency, reverse-usage, and CDS impact analysis, and includes knowledge-transfer documentation and dependency contracts when available.
SAPLint read-only
Runs local ABAP linting, autofix, and pre-write validation, with server-side PrettyPrint support.
SAPDiagnose read-only
Runs syntax checks, ABAP Unit, ATC, diagnostics, active/inactive comparisons, quick fixes, short-dump analysis, and profiler traces.
SAPManage read-only
Provides feature probing, cache statistics, package lifecycle operations, and FLP catalog, group, and tile helpers.

Use cases

AI-assisted ABAP source understanding and development
SAP object and source-code search
ABAP linting, activation, testing, and diagnostics
CTS transport and gCTS or abapGit workflows
Dependency, usage, and CDS impact analysis

Supported clients

Claude Desktop
Claude Code
GitHub CopilotPartial support
Copilot StudioPartial support
Joule StudioPartial support

Listed from the project's documentation, not tested by this site.

Overview

ARC-1 connects AI assistants and MCP clients to SAP ABAP systems through the SAP ADT REST API. It supports ABAP source reading, search, editing, activation, navigation, diagnostics, testing, transport management, Git workflows, context analysis, and linting. It can run locally, on SAP BTP, or in on-premise environments. The default posture is read-only; writes, data preview, and free SQL require explicit enablement.

Similar servers

Context7 80 · B

Upstash's official server providing up-to-date third-party library docs for AI coding assistants

★ 62.9k · Tools 2 Compare with this →

Source revision 150dc8b994ed Data synced 2026-10-12 Read the FMRS scoring method