Connect XTester to an AI agent (MCP)
Connecting — the built-in XTester screen
XTester knows the real install path and the current workspace rules, so you connect through the GUI rather than by hand-editing configs:
- Download XTester only from the official GitHub Release.
- Install or unpack the program.
- Launch XTester.
- Open the built-in "Connect to an AI agent (MCP)" item.
- Pick your MCP client — XTester prepares a configuration with the correct path for your installation.
- Apply it from the connection screen and add it to your client.
- Restart the agent session.
- Verify the connection with a safe read-only call.
The built-in screen always matches the installed version and the real component locations. That is why concrete install paths and launch arguments are not reproduced on the website — the application itself shows their current values.
How it works, conceptually
XTester runs a local MCP server over the stdio transport: the AI client talks to it directly on your computer, and no separate MCP network port is opened. See Security for more on transport and data.
Clients
Per-client instructions for Claude Code, Claude Desktop, Codex CLI, Cursor, Windsurf and VS Code are being prepared and verified. Exact config snippets and step-by-step checks will be published after they are reconciled with a verified release. Until then, use the built-in connection screen in XTester — it always matches the installed version.
What not to do
- do not disable antivirus or SmartScreen;
- do not run as administrator without a proven need;
- do not use debug paths like
bin\Debug\...; - an agent must not silently download and run the application — the user confirms install and launch.