Installing and registering the MCP server

The MCP server is DelphiDebuggerMcp.exe. Registering it means telling your agent where that executable is; the agent starts it and talks to it over stdio. Registration is per user, not per project.

During installation

The simplest path: Setup.exe offers to register the MCP server at the end of an install. Say yes and there is nothing else to do — Getting started covers the install itself.

Registering it yourself

From a source checkout, or to register a copy the installer did not, run the same script the installer uses. Build the server first if you are working from source:

cmd /c build_mcp.bat

powershell -ExecutionPolicy Bypass -File register-mcp.ps1 ^
  MCPDebugger\Win64\Debug\DelphiDebuggerMcp.exe

The script takes the path to DelphiDebuggerMcp.exe as its argument, resolves it to an absolute path, and registers it under the name delphi-win64-debugger. It is idempotent — re-running it is safe and simply refreshes the registration.

To remove it:

powershell -ExecutionPolicy Bypass -File register-mcp.ps1 -Unregister

Restart Claude Code, or reload VS Code, for either change to take effect.

What the script actually registers

Two targets, handled differently because they configure MCP differently.

Claude Code

Registered through the claude CLI at user scope, which is the equivalent of running:

claude mcp add delphi-win64-debugger -s user -- "C:\path\to\DelphiDebuggerMcp.exe"

If the claude CLI is not on PATH, the script skips this step and prints that command for you to run yourself rather than failing the whole registration.

VS Code and VS Code Insiders

No CLI needed — the script merges an entry into the user mcp.json, in the format VS Code 1.102 and later expects:

%APPDATA%\Code\User\mcp.json
%APPDATA%\Code - Insiders\User\mcp.json

{
  "servers": {
    "delphi-win64-debugger": {
      "type": "stdio",
      "command": "C:\\path\\to\\DelphiDebuggerMcp.exe",
      "args": []
    }
  }
}

It merges rather than overwrites: other servers already in the file are left alone. An editor that is not installed is skipped, and if neither is found the script says so.

Any other MCP client is configured the same way — point it at DelphiDebuggerMcp.exe as a stdio server with no arguments. The server itself has no client-specific behaviour; only the configuration file format differs.

Checking it worked

Restart the agent and ask it to list running processes — that maps to list_debuggable_processes, needs no debug session, and either answers or makes it obvious the server is not connected. From there, Example prompts has eleven things worth trying, and Tool reference lists everything the server exposes.