ABAPilot MCP Server

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add abapilot-mcp -e 'ABAPILOT_URL=<ABAPILOT_URL>' -- npx -y abapilot

{
  "mcpServers": {
    "abapilot-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "abapilot"
      ],
      "env": {
        "ABAPILOT_URL": "<ABAPILOT_URL>"
      }
    }
  }
}

[mcp_servers.abapilot-mcp]
command = "npx"
args = ["-y", "abapilot"]
env = { ABAPILOT_URL = "<ABAPILOT_URL>" }

{
  "mcpServers": {
    "abapilot-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "abapilot"
      ],
      "env": {
        "ABAPILOT_URL": "<ABAPILOT_URL>"
      }
    }
  }
}

{
  "servers": {
    "abapilot-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "abapilot"
      ],
      "env": {
        "ABAPILOT_URL": "<ABAPILOT_URL>"
      }
    }
  }
}

Put your own value in place of <ABAPILOT_URL> (URL of the ABAPilot SICF endpoint in your SAP system, e.g. https://sap-host:8443/sap/bc/abapilot). The author’s registry entry marks it as required.

Optional settings from the registry entry, left out of the block above: ABAPILOT_USER (SAP user for basic authentication), ABAPILOT_PASSWORD (SAP password for basic authentication), ABAPILOT_TOKEN (Bearer token, alternative to basic authentication), ABAPILOT_CLIENT (SAP client number, e.g. 100), ABAPILOT_TOOLS (Comma-separated allowlist of tool names to expose to the client. Optional; default is the full catalog), ABAPILOT_TLS_INSECURE (Set to 1 to skip TLS certificate verification (development systems only)).