Connecting a client

Wiring Claude Desktop, Claude Code or any other MCP client to the app.

File > Settings > Connections. Each client has a Connect button and reports its own status.

Claude Desktop

Connect registers the app with Claude Desktop. Once connected it auto-reconnects on launch, so it is a one-time setup.

If the page says Claude Desktop is not installed, install it first; there is nothing to register against otherwise.

Claude Code (CLI)

Connect registers the connector at user scope, so it is available in every project you open in Claude Code.

If the page reports that the claude CLI is not on PATH, either install Claude Code or use the registration command the page shows, which does the same thing by hand.

Other clients

The two Claude clients above are the ones the page registers for you. Any other MCP-capable client connects the same way underneath: point it at the broker with the registration details the page gives you to paste in.

MCP is an open protocol, so this is the path for whatever you run rather than a fallback - the connector does not care which assistant is on the other end of it.

Checking it works

• Test connection runs a round trip and reports back.
• The status line tells you what is missing when something is: Ready. Open a project so Claude can read it. means the connector is fine and there is simply nothing open yet.

The connector reads the project you have open. Open the job first, then ask - a connected client with no open project can see nothing.

Performance

The page lists per-tool latency from the day's connector calls, slowest first, with median, 95th percentile and worst handler time. It is there for diagnosing a slow tool rather than for daily use.