SAP ABAP MCP

MIT

sapabapadtdeveloper-toolsenterprise

Summary

Headless MCP server exposing SAP ABAP Development Tools so agents can browse, edit, refactor, and test ABAP without SAP GUI.

Features

115 tools across repository browsing, semantics, editing, and refactoring
ABAP Unit test execution and ATC static analysis with CI-friendly reports
Transport request listing, assessment, and release
Production-safe defaults: read-only profiles, confirm-required writes

Installation

Set up this MCP server in your favorite AI agent — copy a ready-made configuration below.

Any MCP-compatible agent

Most agents (Claude, Cursor, Windsurf, VS Code, and more) read a standard mcpServers configuration.

Open your agent's MCP configuration file.
Merge the snippet below into it.
Restart the agent — the "SAP ABAP MCP" tools will be available.

{
  "mcpServers": {
    "sap-abap-mcp": {
      "command": "npx",
      "args": [
        "--yes",
        "@coaspe/sap-abap-mcp@latest",
        "serve",
        "--profile",
        "DEV100"
      ]
    }
  }
}

Claude Code

Add the server with a single CLI command.

claude mcp add sap-abap-mcp -- npx --yes @coaspe/sap-abap-mcp@latest serve --profile DEV100

Claude Desktop

Add the server to claude_desktop_config.json (Settings → Developer → Edit Config).

{
  "mcpServers": {
    "sap-abap-mcp": {
      "command": "npx",
      "args": [
        "--yes",
        "@coaspe/sap-abap-mcp@latest",
        "serve",
        "--profile",
        "DEV100"
      ]
    }
  }
}

Description

This server lets Claude, Codex, and other MCP clients act on a real SAP system through ABAP Development Tools APIs, without needing Eclipse/ADT installed or an SAP GUI session. It exposes around 115 tools grouped into repository browsing, such as searching objects and reading metadata and source; semantic services like code completion, go-to-definition, and type hierarchy; source editing including exact-range replacement, BDEF creation, syntax checks, and activation; refactoring such as rename, package moves, and method extraction; quality gates covering ABAP Unit tests and ATC static analysis with CI-friendly JSON, SARIF, or JUnit output; transport management for listing, assessing, and releasing transports; plus abapGit integration, RAP object generation, and runtime debugging.

Governance is built in on purpose: production-connected profiles default to read-only, writes require an explicit transport request and confirmation, preview plans expire after ten minutes, and no ABAP source or credentials are sent anywhere outside the connection you configure. This is squarely a developer-tools play for SAP shops that want AI pair-programming or automated refactors and tests against ABAP codebases with the same guardrails a human developer would face, rather than a generic file-editing tool retargeted at SAP.