fr0ster/mcp-abap-adt

Package (npm 23.1.0)

npx -y @mcp-abap-adt/[email protected]

Or add to your MCP client config:

{
  "mcpServers": {
    "mcp-abap-adt": {
      "command": "npx",
      "args": [
        "-y",
        "@mcp-abap-adt/[email protected]"
      ],
      "env": {
        "SAP_SYSTEM_TYPE": "<YOUR_VALUE>"
      }
    }
  }
}

• MCP_ENV_PATH — Path to the .env file that states the destination (the same as the --env-path argument). The file states SAP_URL and SAP_AUTH_TYPE (basic, snc or jwt); a jwt file also states SAP_GRANT_TYPE (authorization_code or none). Without this or --mcp, the server starts in tool-inspection-only mode: nothing is read from the working directory, and SAP_* variables in the process environment alone form no destination.
• AUTH_BROKER_PATH — Base directory of service-keys/ and sessions/ for a named destination chosen with the --mcp argument (one directory; a list is not split). Default: ~/.config/mcp-abap-adt (Documents\mcp-abap-adt on Windows).
• MCP_BROWSER — Browser for a JWT login: chrome, edge, firefox, system, headless or none.
• MCP_BROWSER_AUTH_PORT — Callback port of the JWT browser login, 1-65535.
• MCP_UNSAFE — Write a named destination's session to disk (sessions/<name>.env) instead of keeping it in memory.
• SAP_CONNECTION_TYPE — Connection type: http or rfc. SNC needs rfc (and the SAP NW RFC SDK).
• SAP_SYSTEM_TYPE required — System type, required (here or as --system-type; no default, never guessed): the tools offered (e.g. Programs are onprem-only), the connector, and how the system's answers are read. Without it a destination does not start.
• SAP_LANGUAGE — Logon language (ISO code, e.g. 'en', 'de').
• SAP_MASTER_SYSTEM — System context for on-prem create/update operations (system id).
• SAP_RESPONSIBLE — Responsible user for on-prem create/update operations.

This server takes extra arguments — see its repository.