Skip to Content
Help centreMy agent isn’t connecting

Troubleshooting

My agent isn’t connecting

The things that cause this, in the order they're worth checking.

Check the URL

It is https://mcp.breaknorm.co/mcp — with /mcp at the end. https://mcp.breaknorm.co on its own is not the server.

Finish the sign-in (Claude, ChatGPT)

After adding the connector, the client opens app.breaknorm.co. Sign in, pick the organization and click Allow. If you closed that window, remove the connector and add it again, or use the client’s Connect button next to it.

Restart the client (config-file clients)

Claude Desktop, Cursor and most editors read their MCP config at startup. Quit the client properly (⌘Q on macOS — closing the window is not quitting) and reopen. A trailing comma in the JSON silently disables the whole file in most clients.

ClientWhere the config lives
Claude Codeclaude mcp list shows what is registered; /mcp shows its status
Cursor~/.cursor/mcp.json, or .cursor/mcp.json in the project
VS Code.vscode/mcp.json

Test the key (key-based clients)

curl -s https://api.breaknorm.co/v1/usage -H "Authorization: Bearer bnk_live_…"

200 — the key works; the problem is in the client config. 401 — the key was revoked or mistyped; create a new one under API keys in the dashboard. 402 — the key is fine but the plan is not active; see Billing.

It connects, but the agent doesn’t use it

The agent sees the tools and decides not to call them — usually because the question sounds answerable from memory. Be explicit: “Use Breaknorm to find…”. Once it sees real data come back it keeps using it.

Clients with many servers connected sometimes drop tools past a limit — disconnect a server you are not using.

Still stuck? Email [email protected] with your client and version and, if you have one, the request_id from an error message.