MCP Abap Adt Compact MCP Server

What the code does

We read the source, 3 h ago · rules 995398eba69f

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

  const dist = path.join(REPO, pkg, 'dist', file);

Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.

  const result = spawnSync(npmCmd, jestArgs, {

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

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 mcp-abap-adt-compact -e 'SAP_SYSTEM_TYPE=<SAP_SYSTEM_TYPE>' -- npx -y @mcp-abap-adt/compact

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

[mcp_servers.mcp-abap-adt-compact]
command = "npx"
args = ["-y", "@mcp-abap-adt/compact"]
env = { SAP_SYSTEM_TYPE = "<SAP_SYSTEM_TYPE>" }

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

{
  "servers": {
    "mcp-abap-adt-compact": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@mcp-abap-adt/compact"
      ],
      "env": {
        "SAP_SYSTEM_TYPE": "<SAP_SYSTEM_TYPE>"
      }
    }
  }
}

Put your own value in place of <SAP_SYSTEM_TYPE> (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). The author’s registry entry marks it as required.

Optional settings from the registry entry, left out of the block above: 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_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).