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
A
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.
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.
Tools
SAPRead
Reads ABAP source, methods, metadata, table contents, CDS views, service bindings, knowledge-transfer documents, versions, and other supported SAP objects.
SAPSearch
Searches SAP objects and source code across the system.
SAPWrite
Creates, updates, or deletes ABAP source and supported DDIC metadata.
SAPActivate
Activates individual or batched ABAP objects and publishes or unpublishes OData service bindings.
SAPNavigate
Provides go-to-definition, find-references, and code completion capabilities.
SAPQuery
Executes ABAP SQL and automatically chunks some long literal IN lists.
SAPTransport
Manages CTS transports, including listing, creation, release, deletion, reassignment, and recursive release.
SAPGit
Supports Git workflows across gCTS and abapGit, including repository, commit, branch, and push operations.
SAPContext
Provides dependency, reverse-usage, and CDS impact analysis, and includes knowledge-transfer documentation and dependency contracts when available.
SAPLint
Runs local ABAP linting, autofix, and pre-write validation, with server-side PrettyPrint support.
SAPDiagnose
Runs syntax checks, ABAP Unit, ATC, diagnostics, active/inactive comparisons, quick fixes, short-dump analysis, and profiler traces.
SAPManage
Provides feature probing, cache statistics, package lifecycle operations, and FLP catalog, group, and tile helpers.
Setup
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.
Fit and risk
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
Troubleshooting
- Verify SAP_URL, SAP_USER, SAP_PASSWORD, and SAP_CLIENT
- Check that the SAP user has the required ADT and object permissions
- Confirm that the target system supports the requested feature; ARC-1 probes and adapts to system capabilities
- For failed write, table-preview, free-SQL, Git, or transport operations, check the corresponding explicit enablement flags
- For TLS problems, inspect certificate configuration and consider SAP_INSECURE only after understanding the risk
- In shared technical-user mode, inspect startup authorization-preflight errors, including 401 or 403 responses
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 DesktopFull support
Claude CodeFull support
GitHub CopilotPartial support
Copilot StudioPartial support
Joule StudioPartial support