# Why can't my coding agent see Brilliant's tools?

*How-to · by The Brilliant team · updated Nov 20, 2026 (2026-11-20)*

> **Short answer.** Most often the agent was not restarted after you connected it, or nothing is serving Brilliant: the desktop app is closed, or the helper has no browser canvas to pair with. Restart the agent, keep Brilliant open in the desktop app or in a Chrome, Edge or Firefox tab, and look for brilliant in the agent's server list, which is /mcp in Claude Code.

## How to get your agent to see Brilliant

### 1. Restart the agent

Most tools load MCP servers at startup, so a server you added in the middle of a session does not appear. Quit the agent and open it again, or start a new session.

### 2. Look for brilliant in the server list

In Claude Code, run /mcp in the new session. In VS Code, run MCP: List Servers from the Command Palette.

```text title="Claude Code"
/mcp
```

### 3. Make sure something is serving Brilliant

With the desktop app, the local server runs only while the app is open, so open it. With the npx helper, the first tool call opens brilliant.design in Chrome, Edge or Firefox and pairs with it. Safari cannot run the browser canvas.

### 4. Connect again if the entry is missing

The desktop app removes its entry when it quits and adds it back at its next start, unless you unchecked the row in Settings, MCP connections. To add the helper for Claude Code, run the line below. Other clients have their own line on the Supported clients page.

```text title="Terminal"
claude mcp add --scope user brilliant -- npx -y @brilliant-hq/mcp
```

### 5. Name Brilliant in the prompt

Ask for a design in Brilliant by name, then check that the tool call came from brilliant.

```text title="Prompt"
Design a three-tier pricing section in Brilliant.
```

## Common problems

| Problem | Fix |
|---|---|
| The row reads Another Brilliant instance owns this config | Check the row in the copy of Brilliant you are using, then restart the tool. |
| The row is unchecked, but the config file has a brilliant entry | Check the row. It rewrites the address. |
| Calls fail or the connection is refused | Open Brilliant. Its local server runs only while the app is open. |
| The npx command fails to start | The helper needs Node 20 or later. Run node --version, update Node if it is older, then restart the agent. |

## Questions

### Do I have to keep Brilliant open while the agent works?

Yes. Keep the desktop app open, or keep open the brilliant.design tab the helper paired with. The agent has nothing to call when both are closed.

### Does the helper need an API key?

No. It needs Node 20 or later and no API key.

### Which browsers work with the helper?

Chrome, Edge and Firefox. Safari cannot run the browser canvas the helper pairs with.

### How do I check the connection in Claude Code?

Run /mcp in a session, or claude mcp list from a shell, and look for brilliant.

### Where is the connect line for my client?

On the Supported clients page, with the config file each line writes. Add --dry-run to any install line to preview the change, or --remove to take it out.

## Related

- [Supported clients, with each connect line](https://brilliant.design/docs/agents/clients)
- [Claude Code setup](https://brilliant.design/docs/agents/claude-code)
- [Troubleshooting](https://brilliant.design/docs/workspace/troubleshooting)
- [What port does the Brilliant MCP server use?](https://brilliant.design/learn/brilliant-mcp-port)
- [Why does my browser ask for local network access?](https://brilliant.design/learn/local-network-access-for-brilliant)

[Open the editor](https://brilliant.design/playground)
