Connect Claude and ChatGPTCopy link
Claude and ChatGPT reach Routing24 as a custom connector. You paste one URL, approve the connection once on a Routing24 screen, and keep an app tab open while the assistant works. This page covers the connection in each client, the first run, the failures the assistant reports, and how to disconnect.
The mechanics behind the connection, and the 45 tools it exposes, are in Routing24 as an MCP server.
Two domains appear on this page. The connector URL is on routing24.ai. The
app you sign in to stays on routing24.com.
PrerequisitesCopy link
Open routing24.com/app and sign in. Leave the tab open. Every call the assistant makes runs inside that tab, so a closed tab means a failed call.
Connect ClaudeCopy link
- In Claude, open Settings > Connectors and press Add custom connector.
- Enter
https://routing24.ai/mcpas the URL. Set Authentication to Always required, and the OAuth client to Use Anthropic's hosted client metadata. - Press Connect on the connector. Claude sends you to the Routing24 consent screen, described below.
- Press Allow. Claude returns to its own settings and lists the Routing24 tools.
The consent screenCopy link
The screen is headed Connect an agent and names the client asking: "Claude wants to access your Routing24 account: read and edit your plans through MCP tools, acting as you."
Below the client name, one line reports what Routing24 knows about it.
Verified client: claude.ai means the client published its identity at a
domain Routing24 could check. Unverified client means it registered itself
and named no domain. Approve an unverified client only when you started the
connection yourself and recognize the name.
Two more lines state what happens next. The first reads "Keep Routing24 open in a browser tab: your assistant works through it". The second names where the approval sends you: the client's website, or "an app running on this computer" for a client that runs on your own machine.
When you are signed out, the screen shows Sign in to continue and the login form in place of the buttons. Sign in there and the buttons appear.
Allow grants the connection and reads Connecting… while it works. Cancel refuses it and returns to the client with nothing granted.
Approving sends you to the assistant and leaves no Routing24 tab behind. Open routing24.com/app again and keep it open. Otherwise the assistant's first call comes back "No Routing24 browser tab is connected for this account."
Connect ChatGPTCopy link
ChatGPT reaches custom MCP connectors in developer mode. Enable it,
then add https://routing24.ai/mcp as the connector URL. ChatGPT opens the
same consent screen and lists the Routing24 tools after you press Allow.
Other clientsCopy link
Any MCP client that speaks OAuth connects the same way, with the same URL and the same consent screen. Microsoft Copilot Studio is one. A client that cannot sign in with OAuth cannot connect today.
First runCopy link
Give the assistant a small task and check the result in your own tab:
Open my Routing24 account, list the tools you have, and tell me how many
plans I have saved and which one is loaded.
On a successful run the assistant reports the tool list and your plans, and
a green badge appears in the Routing24 header reading the client's name and
(now). Press the badge to open the assistant pane and read the log of what
it called.
Then give the assistant real work:
In Routing24, add a van with a 20 pallet capacity working 8:00 to 17:00,
re-optimize, and tell me what changed.
The app locks behind an Agent controlled overlay while the edit applies. The routes redraw in your tab, and the assistant reports the result. See what you see while a connected assistant works.
What the errors meanCopy link
Each row below is the remedy. The cause of each is in Routing24 as an MCP server.
| What the assistant reports | What to do |
|---|---|
| No Routing24 browser tab is connected | Open routing24.com/app and sign in |
| No Routing24 app tab is open | The browser is attached but every app tab is closed. Open one |
| The tab closed while running a tool | Reopen the tab, then ask the assistant to re-read the plan before it retries |
| The tab did not answer within 60s | Ask the assistant to check the status rather than repeat the call. A running optimization keeps going in the tab |
| Another tab took over while this call was running | You approved the connection in a second browser. Work in that browser, or approve again in this one |
| The connector asks for consent again | The connection was revoked. Approve it again |
An assistant that reports the tools are missing is looking at the wrong account or the wrong browser. Check that the browser holding your app tab is the browser you approved the connection in.
DisconnectCopy link
Open the assistant pane in Routing24. The bar below the message box reads "Claude is connected to your account". Press Disconnect and confirm. Claude loses access to your Routing24 account and stops working right away. To use it again, approve the connection from Claude once more.
Removing the connector in Claude or ChatGPT stops that client from calling, but leaves the approval on your account. Each workspace of a client runs its own approval, and disconnecting one leaves the others.
Next stepCopy link
Convert any data and fix every address covers turning a supplier file into orders.