sap-abap-mcp

The headless, client-neutral, governance-first MCP server for SAP ABAP development across multiple systems.

SAP ABAP MCP lets Codex, Claude, and other local MCP hosts work with SAP ABAP through ABAP Development Tools (ADT) HTTP services. It can inspect and edit source, run quality checks, manage transports, use abapGit and the RAP generator, inspect runtime data, compare systems, and perform guarded refactorings without an IDE runtime, SAP GUI, or an ABAP FS virtual workspace.

Why this server

SAP now provides an official ADT MCP Server inside its ADT clients. This project serves a different operating model: headless automation from any supported local MCP host.

This is a deployment-model comparison, not a capability benchmark or a claim of SAP endorsement. Official behavior varies by ADT and SAP backend release.

90-second workflow

The animation contains synthetic object and transport names and no live SAP data. See the accessible transcript and exact workflow.

Quick start

Detailed references: profiles and authentication, HTTP deployment, and CLI commands.

You need Node.js 20 or later, network or VPN access to SAP, and an SAP HTTPS URL, three-digit client number, username, and ADT Basic Auth permission.

Recommended: guided onboarding

Run one command and follow the local browser wizard. It checks npm, Claude Code, Codex, existing .claude and .codex settings, and saved SAP profiles. It then verifies the SAP login before saving it and registers the MCP server through the installed client's official CLI. Existing steps are detected and skipped.

Windows:

npx.cmd -y @coaspe/sap-abap-mcp@latest onboard

macOS:

npx -y @coaspe/sap-abap-mcp@latest onboard

The wizard runs only on 127.0.0.1; SAP credentials do not pass through a publisher-operated service. Passwords are protected with Windows DPAPI or macOS Keychain. Linux users should use the manual setup because the browser wizard does not store Linux credentials.

Manual setup

1. Configure SAP

Windows:

npx.cmd @coaspe/sap-abap-mcp@latest setup

macOS or Linux:

npx @coaspe/sap-abap-mcp@latest setup

The wizard calls the local connection alias Server name and the endpoint SAP URL. Windows and macOS validate SAP before saving and protect the password with DPAPI or Keychain. Linux saves only non-secret settings and prints the password environment-variable commands to run before starting the MCP client.

2. Register the MCP server

After setup, run only the command for your client. On Windows, use npx.cmd.

Codex CLI:

codex mcp add sap-abap -- npx.cmd -y @coaspe/sap-abap-mcp@latest serve

Claude Code:

claude mcp add --transport stdio --scope user sap-abap -- npx.cmd -y @coaspe/sap-abap-mcp@latest serve

On macOS or Linux, use npx.

Codex CLI:

codex mcp add sap-abap -- npx -y @coaspe/sap-abap-mcp@latest serve

Claude Code:

claude mcp add --transport stdio --scope user sap-abap -- npx -y @coaspe/sap-abap-mcp@latest serve

This registration exposes all saved SAP profiles; every SAP-facing tool still requires an explicit connectionId. Restart the client, then use codex mcp list, claude mcp get sap-abap, or /mcp to confirm that the process starts. The completed wizard already performs live SAP verification; /mcp alone does not prove that SAP authentication succeeded.

Prefer a plugin install? Follow Claude Code and Codex plugin marketplaces; the included setup skill guides the same local wizard without putting the SAP password in chat. See the detailed Windows, macOS, and Linux sections for platform-specific behavior and server management.

Community and adoption

• Read the public roadmap.
• Run or implement the open SAP ABAP MCP compatibility profile.
• Add an opt-in, sanitized entry to ADOPTERS.md.
• Use GitHub Discussions for implementation questions, compatibility evidence, and RFCs.

Need a transport-specific release decision and CI evidence from existing ATC and ABAP Unit checks? Review the fixed-scope paid diagnostic and three-day pilot. If your current workflow already preserves the check results, release decision, and evidence together, the service is not a fit. Never include SAP credentials, source code, hosts, transport numbers, logs, tokens, or other confidential information in a public issue or discussion.

Current v1 surface

The v1 catalog contains 120 action-specific tools and seven Resources. Unreleased local CLI builds default to the minimal preset: five discovery/invocation tools. Other capabilities are loaded on demand. Use --toolsets all to advertise the complete catalog directly. Use --api-version v0 only for legacy client compatibility, or select toolsets explicitly when a host should advertise fewer schemas. Normal clients should omit both --api-version and --toolsets.

See the v1 migration guide for contracts, Resources, and the separate live-SAP verification boundary.

Built-in workflow prompts (unreleased)

MCP hosts supporting prompts/list and prompts/get can select these workflows:

Each prompt accepts systemId, target, and optional goal in your preferred language. Prompts appear only when their required tools are enabled; viewer sessions never expose the source-change workflow. The legacy v0 API is unchanged. Fetching a prompt performs no SAP calls. These are agent instructions, not an automatic transaction or an additional authorization grant.

For local usage and verification, see workflow prompts. The September 2026 competitive assessment separates implemented improvements from remaining live-SAP and release gaps.

Live SAP evidence

Capabilities are reported as unverified until they succeed against a live connection. docs/live-sap-evidence.md records the current sanitized results — no credentials, no customer source, no host names.

200 live checks in total: 180 tool-surface checks across two systems, plus 20 transport and CI checks on one. The tool-surface count counts each capability once per system, because release coverage is the claim; it is not 180 distinct capabilities.