irfanardi/mcpabapaccelerator repository overview

⁠ABAP Accelerator MCP Server

MCP (Model Context Protocol) server that connects AI coding assistants — Kiro, Claude Desktop, VS Code, Amazon Q Developer, and other MCP-compatible clients — directly to your SAP system (ECC or S/4HANA) over the SAP ADT (ABAP Development Tools) REST API.

It lets an AI assistant read, write, check, and activate ABAP objects, browse the DDIC data model, inspect enhancements/BAdIs, and run read-only data previews — all through natural conversation instead of manually switching between SAP GUI, Eclipse ADT, and your editor.

⁠How it works

+------------------------+
|  MCP Client            |
|  (Kiro / Claude /      |
|   VS Code / Q Dev)     |
+-----------+------------+
            |  MCP protocol (HTTP, streamable)
            v
+------------------------+
|  ABAP Accelerator      |
|  MCP Server (Docker)   |
+-----------+------------+
            |  SAP ADT REST API (HTTPS)
            v
+------------------------+
|  SAP ECC / S/4HANA     |
+------------------------+

The server runs as a single Docker container exposing an HTTP MCP endpoint (default http://localhost:8000/mcp). It authenticates to SAP using Basic Auth (username/password) over the ADT REST API — no RFC/SAPGUI connectivity is required, only HTTPS access to the SAP host's ICM port (typically 443<instance>, e.g. 44300 for instance 00).

⁠Quick Start (Docker)

⁠1. Pull the image

docker pull irfanardi/mcpabapaccelerator:latest

The image is multi-arch (linux/amd64 and linux/arm64), so it runs natively on both Intel/AMD machines and Apple Silicon / ARM.

⁠2. Run the container

docker run -d \
  --name abap-mcp \
  --restart unless-stopped \
  -p 8000:8000 \
  -e CREDENTIAL_PROVIDER=env \
  -e SAP_HOST=your-sap-host.example.com \
  -e SAP_INSTANCE_NUMBER=00 \
  -e SAP_CLIENT=100 \
  -e SAP_USERNAME=YOUR_SAP_USER \
  -e SAP_PASSWORD='YOUR_SAP_PASSWORD' \
  -e SAP_SYSTEM_ID=YOUR_SID \
  -e SAP_LANGUAGE=EN \
  -e SSL_VERIFY=false \
  -e MCP_ROLE=dev \
  irfanardi/mcpabapaccelerator:latest

MCP_ROLE controls which tools the container exposes — set it to match how you intend to use the server:

Run the same command as above but with -e MCP_ROLE=prod for a read-only instance:

docker run -d \
  --name abap-mcp-readonly \
  --restart unless-stopped \
  -p 8000:8000 \
  -e CREDENTIAL_PROVIDER=env \
  -e SAP_HOST=your-sap-host.example.com \
  -e SAP_INSTANCE_NUMBER=00 \
  -e SAP_CLIENT=100 \
  -e SAP_USERNAME=YOUR_SAP_USER \
  -e SAP_PASSWORD='YOUR_SAP_PASSWORD' \
  -e SAP_SYSTEM_ID=YOUR_SID \
  -e SAP_LANGUAGE=EN \
  -e SSL_VERIFY=false \
  -e MCP_ROLE=prod \
  irfanardi/mcpabapaccelerator:latest

You can run both a dev and a prod container side by side (different names, different host ports) if you want separate connections for exploration-only vs. active development.

Wait a few seconds, then confirm it's healthy:

docker ps --filter name=abap-mcp
# STATUS should show "healthy"

docker logs abap-mcp --tail 20

⁠3. Point your MCP client at it

The config file location and JSON shape differ per client. Both connect to the same running container — only the config format changes.

⁠Kiro

File: .kiro/settings/mcp.json (workspace-level) or ~/.kiro/settings/mcp.json (user-level, applies to all workspaces).

{
  "mcpServers": {
    "abap-accelerator": {
      "url": "http://localhost:8000/mcp",
      "disabled": false,
      "autoApprove": [
        "abap_cb_get_source",
        "abap_cb_connection_status",
        "abap_cb_search_object",
        "abap_cb_data_preview"
      ]
    }
  }
}

Create the file (and .kiro/settings/ folder) if it doesn't exist yet. After saving, open the MCP Servers panel in Kiro and enable/reconnect abap-accelerator — Kiro watches this file, but a manual reconnect is the most reliable way to pick up a newly added or edited server, especially after the container itself was restarted.

autoApprove is optional — it lists tool names Kiro can call without prompting for confirmation each time. Leave it as [] (or omit it) if you want to approve every call manually.

⁠VS Code (MCP extension / Copilot Chat MCP support)

File: .vscode/mcp.json in the workspace, or your global MCP settings depending on the extension you use. The key difference from Kiro is the top-level key (servers instead of mcpServers) and the explicit "type": "http":

{
  "servers": {
    "abap-accelerator": {
      "type": "http",
      "url": "http://localhost:8000/mcp"
    }
  }
}

Reload the window (or use the extension's "Restart/Reconnect MCP Server" command) after adding or changing this file.

⁠Claude Desktop

Claude Desktop's config only supports stdio-launched MCP servers out of the box (command/args), not a raw HTTP URL like this server exposes. To use it there, run the container as above and bridge it with an HTTP-to-stdio proxy such as mcp-remote:

{
  "mcpServers": {
    "abap-accelerator": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "http://localhost:8000/mcp"]
    }
  }
}

Config file location: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows).

⁠Verifying the connection

Whichever client you use, once it's connected, ask it to check the SAP connection — it should call abap_cb_connection_status and report Connected.

⁠Alternative: interactive helper script

If you're running from this repository's source, run-abap-accelerator.sh walks you through the same setup interactively (prompts for host/client/user/password, starts the container, verifies the SAP connection, and prints the ready-to-paste MCP config block):

./run-abap-accelerator.sh

⁠Alternative: Docker Compose

services:
  abap-accelerator:
    image: irfanardi/mcpabapaccelerator:latest
    container_name: abap-accelerator
    restart: unless-stopped
    ports:
      - "8000:8000"
    environment:
      CREDENTIAL_PROVIDER: "env"
      SAP_HOST: "your-sap-host.example.com"
      SAP_INSTANCE_NUMBER: "00"
      SAP_CLIENT: "100"
      SAP_USERNAME: "YOUR_SAP_USER"
      SAP_PASSWORD: "YOUR_SAP_PASSWORD"
      SAP_SYSTEM_ID: "YOUR_SID"
      SAP_LANGUAGE: "EN"
      SSL_VERIFY: "false"
      MCP_ROLE: "dev"

docker compose up -d
docker compose logs -f
docker compose down

⁠Configuration Reference

⁠Required

⁠Optional

⁠Multi-system setup

Each request can target a different SAP system by passing an x-sap-system-id header (or the sap_system_id tool argument), resolved against systems configured via CREDENTIAL_PROVIDER=interactive-multi and a sap-systems.yaml file, or aws_secrets in production/ECS deployments.

⁠Security Notes

• Never bake SAP_PASSWORD into the Docker image. Pass it at runtime via -e / Compose / a secrets manager.
• Prefer a dedicated SAP service user scoped to what the assistant needs (development client, S_DEVELOP and ADT-related authorizations), not a personal or administrator account.
• Run with MCP_ROLE=prod on any system where you want the assistant to browse/read but never write, activate, or create transports.
• Set SSL_VERIFY=true and use a valid certificate for anything beyond local testing.
• The MCP endpoint itself has no built-in authentication — anyone who can reach http://localhost:8000/mcp can invoke tools with the container's configured SAP credentials. Bind it to localhost only, or place it behind your own reverse proxy/auth layer, before exposing it on a shared network.

⁠What can this MCP do?

The server exposes 43 tools, all prefixed abap_cb_, covering the full loop of exploring, understanding, writing, and validating ABAP code plus its surrounding metadata. In MCP_ROLE=prod (read-only) mode, only the tools marked ✅ below are available; tools marked 🔒 are disabled.

⁠Connection & discovery

⁠Reading & editing ABAP source

⁠Code navigation

⁠Testing & quality

⁠Interfaces, function groups & modules (RFC/BAPI signatures)

⁠Enhancements, exits & BAdIs

⁠Service bindings (OData/REST)

⁠Data dictionary (DDIC) exploration

⁠Data preview (read-only SQL)

⁠Packages & transports

⁠Typical workflows

Understand and extend an existing program

1. abap_cb_search_object → find the program/class.
2. abap_cb_get_source (+ abap_cb_get_program_includes if it has includes) → read it.
3. abap_cb_where_used → check impact before changing anything.
4. abap_cb_check_object_lock → confirm nobody else has it locked.
5. abap_cb_update_source → apply the change.
6. abap_cb_check_syntax / abap_cb_activate_object → validate and activate.
7. abap_cb_run_unit_tests / abap_cb_run_atc_check → verify quality.

Design a new report/query

1. abap_cb_search_object / abap_cb_get_tables → find the relevant tables or CDS views.
2. abap_cb_get_table_info → understand fields, types, and keys.
3. abap_cb_get_data_element_info / abap_cb_get_domain_info → understand field semantics and valid values.
4. abap_cb_data_preview → validate the proposed query against real data, read-only.

Investigate a custom field or enhancement

1. abap_cb_find_field → locate a custom field (e.g. ZBRTU) and its data element/domain, even if it lives in an append structure.
2. abap_cb_get_enhancements / abap_cb_get_enhancement_info / abap_cb_get_enhancement_source → find and read the BAdI/exit logic that populates or uses it.

⁠Troubleshooting

"Failed to connect to SAP system ..."

• Verify SAP_HOST, SAP_INSTANCE_NUMBER (or SAP_PORT), SAP_CLIENT, SAP_USERNAME, SAP_PASSWORD.
• Confirm the host is reachable from wherever the container runs (curl -k https://<host>:<port>/sap/bc/adt/discovery).
• If the SAP server uses a self-signed/expired certificate, set SSL_VERIFY=false (testing only).

MCP client shows the server as connected but tools return "Session not found" or similar

• This happens if the container was restarted after the MCP client already opened a session. Reconnect/re-enable the server in your MCP client so it re-initializes a fresh session.

Syntax check reports a generic error for a program that is clearly valid

• Make sure you're running the latest image — an earlier version had a bug where the syntax-check call always requested the object's "inactive" version, which fails for objects with no pending changes. This is fixed by trying the "active" version first.

Container exited unexpectedly

• docker logs abap-mcp for the stack trace. Common causes: wrong/missing required env var, or SAP host unreachable at startup depending on credential provider mode.

⁠License

MIT License. See LICENSE for details.