Connect an AI assistant to Routy

To connect an AI assistant to Routy, open your account menu, at the top right of any page. Then choose MCP and Access Tokens.

It lets an AI assistant read your Routy reports, so you can ask questions in plain language. Every user has this page. You do not need to be an account admin. An assistant connects as you, with only the permissions you give it, and it can never change anything. For Claude and ChatGPT, use the connector. There is nothing to paste. Copy this connector URL. Then open Claude or ChatGPT, and add it as a custom connector in their settings. When you click Connect there, your browser comes back to Routy to ask for your approval.

This is the Connect an app page. Check where access will be sent. If it is not the app you started from, click Cancel. The permissions are what the app asked for. You can untick any of them, but never add more. Choose the affiliates it may work on, or leave it empty for all of them. That includes affiliates you were added to as a collaborator, not only your own. Then click Allow, and you are sent back to the app, connected.

The connection appears in your list, named after the app and the day you connected it. Created shows the app instead of Manual. To disconnect the app later, revoke this row. Claude Desktop, Claude Code and Cursor are set up with a config file or a command instead. For those, click Create token for MCP.

The name is filled in, and reports read is ticked. That is all an assistant needs. Pick when it expires. Then the affiliates. Here are your own affiliate, and one you were added to as a collaborator. Pick some to limit the token to them, or leave it empty for all of them. Then click Create.

Here is your token. It is shown once, so copy what you need before you close this. Pick your assistant, and copy its config, or for Claude Code, the command. Paste it where your assistant expects it, and restart the assistant.

Every token you make is listed here, with what it can do and when it was last used. A token never gains permissions on its own. When new ones are available, this badge says so. A token unused for ninety days switches itself off, and a revoked one stops working within about thirty seconds.

Settings, API tokens is still here, for account admins. Its keys belong to the affiliate, not to a person. That makes them the right choice for long-running services, like a nightly export. Settings used to have an MCP tab too. That tab is gone, but any key it made still works, and is listed here. If a person uses that assistant, connect it again from MCP and Access Tokens. Then delete the old key here. That's it. The help panel on MCP and Access Tokens has the steps for each assistant.