Connect an AI assistant
Found at Settings → MCP.
This is where you connect your own AI assistant — Claude, Cursor, or any assistant that supports MCP — to your Routy data, so you can ask questions in plain language instead of building a report by hand.
Once it's connected you can ask things like "which accounts made me the most money last month?" and the assistant reads the answer straight out of your reports.
What your assistant can and can't do
This is the part worth reading before you connect anything.
The key we generate for you is read-only. You don't choose what it can access and there's no advanced setting to widen it — that's deliberate, so a key can't end up with more access than it needs.
Connect an assistant
- Go to Settings → MCP.
- Click Connect assistant.
- Pick the assistant you use — Claude Desktop, Claude Code, Cursor, or Other.
- Click Connect. We create the key and show you a config block.
- Click Copy config.
- Paste it into your assistant's MCP configuration, save, and restart the assistant.
- Ask it a question about your data.
The key is shown once. After you close that screen it cannot be shown again — not by us, not by support. If you lose it, disconnect the connection and create a new one. Copy it before you navigate away.
If your assistant isn't in the list, choose Other. You'll get the three things every MCP client asks for: the server address, the transport (Streamable HTTP), and the authorization header to send.
Where to paste the config
Every assistant keeps its MCP configuration in a slightly different place, and
it moves between versions — check your assistant's own documentation if the
option isn't where you expect. As a starting point, look for a Developer,
MCP, or Connectors section in its settings, or an mcp.json /
claude_desktop_config.json file.
If your assistant already has other MCP servers configured, add Routy alongside them rather than replacing the file — the config we give you shows only the Routy entry.
Reading the connections list
Once you have at least one connection, the screen lists them:
"Not yet connected" almost always means the assistant wasn't restarted. Pasting the config isn't enough — most assistants only read their MCP configuration at startup. Restart it and check the row again.
Last used is the one to keep an eye on. If you see a connection you don't recognise, or one from a laptop you no longer use, disconnect it.
Having several connections is normal — one per device, or one per assistant.
Disconnect an assistant
Click Disconnect on the row and confirm.
The key stops working within about a minute and cannot be restored. To use that assistant again you'll need to connect it fresh and paste a new config.
Disconnecting affects only that one connection. Your other assistants keep working.
Common problems
"My assistant says it can't connect." Restart the assistant first — it needs to re-read its configuration. If it still fails, the key may have been mistyped or truncated when pasting: disconnect, connect again, and use the Copy config button rather than selecting the text by hand.
"It connected, but it says it can't find any reports." Your assistant can only see reports that you can see in Report Builder. If a report is missing there, it will be missing here too.
"I closed the window before copying the key." The key can't be recovered. Disconnect that connection and create a new one.
"I can't see the MCP tab / the Connect button does nothing." Only an account admin can connect an assistant. If you're not one, ask your account owner to set it up. If you are an account admin and the screen shows an upgrade message instead, this capability isn't in your current plan — your account owner or billing contact can upgrade.
When to escalate to engineering
- The connection shows Connected with a recent Last used, but the assistant returns data the customer says is wrong.
- Disconnect was clicked and confirmed, but the key still works several minutes later.
- The customer is an account admin on a plan that includes the feature, and the screen still refuses to create a connection.
Include the connection name and its created date — that's enough for us to find the key without ever needing the secret itself. Never ask a customer to send you their key.