Connecting an Assistant

The desktop client writes the configuration for you. You do not need to hand- edit a JSON file unless you want to.

tcc mcp configure

With no argument it lists the AI apps it knows and asks which one. Name the app to skip the question:

tcc mcp configure claude-desktop
tcc mcp configure claude-code
tcc mcp configure cursor

Restart the app afterwards. The tools do not appear until it reconnects.

What It Writes

configure adds an entry called trusted-codes to the app’s mcpServers object, pointing at the running tcc binary by absolute path:

{
  "mcpServers": {
    "trusted-codes": {
      "command": "/path/to/tcc",
      "args": ["mcp"]
    }
  }
}

The files it edits are the canonical ones for each app: Claude Desktop’s claude_desktop_config.json under Application Support, ~/.claude/settings.json for Claude Code, and ~/.cursor/mcp.json for Cursor. Existing content is kept — only the trusted-codes entry is added or replaced.

If you run against a non-production environment, configure forwards that choice into the entry as --env local or --env dev, so the assistant talks to the same environment you configured from. Production is the binary’s default and adds no flag.

Checking and Removing

tcc mcp status
tcc mcp remove cursor

status reports, for each of the three apps, whether a trusted-codes entry is present in its config. remove takes the entry back out; restart the app to deactivate it.

Two Transports

The server speaks MCP over two paths, and which one you get depends on how the assistant reaches it.

Standard input and output. tcc mcp is what configure wires up. The AI app launches the binary as a child process and talks JSON-RPC over the pipe. It is the local path, and it is the only path on which the provider-stamp tool is available — that tool signs with the key on that machine.

Local HTTP. The daemon serves the same tools at POST /mcp on its loopback port, for assistants that want a URL rather than a process. This path carries a bearer token, and the token’s scope decides which tools the assistant is even shown. In hybrid mode the desktop client can mint one for you from loopback and hand back a ready-made snippet with the URL and the Authorization header already filled in.

Startup on the stdio path is deliberately instant — no keychain prompt, no network call, no browser. Nothing is checked until the assistant calls its first tool. If you are not signed in, that call comes back as AUTH_REQUIRED, the assistant calls the login tool, a browser opens, and it retries. On a new device login can answer recovery_required instead, and the assistant will ask you for the three recovery words from the mobile app.

If Your Plan Does Not Include It

tcc mcp configure checks your account before it writes anything, and tells you if the MCP server is not part of your plan. The check is a courtesy, made where a person is waiting for an answer — it is not a lock. The server runs on your machine against a key you already hold and computes codes offline, so no server is in a position to refuse it.