Connect Claude Code

Drive Brilliant from the Claude Code CLI: ask it to design in plain English and watch native, editable elements land on your canvas. This is the smoothest of all the integrations, because Brilliant can register itself with Claude Code for you.

Prerequisites

• Claude Code installed and signed in.

• Brilliant open. The MCP server only runs while the app is running.

Setup

You have two paths. The first needs nothing at all.

Automatic (recommended)

Open the built-in AI chat in Brilliant once (press / on the canvas). Brilliant registers its endpoint with claude for you, including the per-project trust it needs, so the brilliant tools are available the next time you start Claude Code from anywhere.

Manual toggle

If you would rather not open the chat, add the connection from settings:

1. Open Settings (Cmd+,) and pick MCP Connections.

2. Flip the Claude Code row on.

The MCP Connections list with the Claude Code row toggled on (screenshot coming soon)

Either way, Brilliant writes a brilliant server entry into ~/.claude.json. Restart Claude Code (or start a fresh session) so it picks the server up.

By hand

If you manage ~/.claude.json yourself, add Brilliant under mcpServers:

{
  "mcpServers": {
    "brilliant": {
      "type": "http",
      "url": "http://127.0.0.1:3333/mcp"
    }
  }
}

Use 3334 or 3335 if Brilliant reported a fallback port on startup.

Try it

In a Claude Code session with Brilliant open, describe the outcome:

• Design a three-tier pricing section in Brilliant.

• Read the Dashboard canvas in Brilliant and add a stats row that matches its style.

• Turn the button in my selection into a reusable component with hover and disabled variants.

Claude Code shines on multi-step work, so lean into it: point it at a real design brief or an existing canvas and let it build, inspect its own result, and refine.

Troubleshooting

• Claude Code doesn't see the brilliant tools. Restart the session; MCP servers load at startup. Run /mcp inside Claude Code to confirm brilliant is listed and connected.

• "Connection refused" or nothing happens. Brilliant has to be open for the endpoint to answer. Launch it, then retry.

• Port mismatch. If 3333 was busy, Brilliant is on 3334 or 3335. Re-toggle the Claude Code row in Settings to rewrite the current address, then restart.

• The Settings row shows unchecked even though ~/.claude.json has an entry. The entry points somewhere other than the local Brilliant address (usually a hand edit). Toggle it on to rewrite it to the correct URL.