route_cancel_ shipmentCancel a shipment in Route, or take some items out of it.
Sync an order with Route, add each package as it ships, correct or cancel either one, look up a package's status, and see what protection would cost for a cart.
PopMCPRoute
Every order, shipment and quote call Route publishes for merchants, plus a lookup for the courier code each shipment needs.
12 tools in the full catalog: 4 read and 8 write. 10 load by default, and the rest are found with tool search.
route_cancel_ shipmentCancel a shipment in Route, or take some items out of it.
route_create_ shipmentAdd a package to an order once it has a carrier tracking number.
route_find_ courierFind the courier_id Route uses for a courier, before route_create_shipment or route_update_shipment.
route_get_ shipmentRead one package's tracking status from Route.
route_track_ packagesCheck up to 10 packages in one call.
route_update_ shipmentChange what is in a package, or its courier.
route_cancel_ orderTell Route an order was canceled, or that protection was removed from it.
route_create_ orderSend a store order to Route so it can be protected and claims can be filed against it.
route_update_ orderReplace an order Route already has, after the store's order changed.
route_get_ quotePrice Route protection for a cart before an order exists.
route_create_ order_ v1The older way to send an order to Route.
route_update_ order_ v1Change an order Route already has, using the older version of the call.
Credentials off one Route screen, then an endpoint your client signs into. Nothing to deploy, and nothing to install.
Paste your Secret API token, from the Admin section of the Route dashboard or the email Route sent when your account was made. The token belongs to one merchant account, so there is nothing else to choose. Use the Test-Secret token to try things first.
••••••••••••3f7amerch_...With a live token, creating an order makes a real order in Route, and canceling one changes what Route protects. Route has no read-only token, so use a read-only connection in PopMCP to limit the AI to tracking and quotes.
Drop the PopMCP URL into Claude, ChatGPT, Claude Code, Codex or any other supported client. It signs in through PopMCP with OAuth, so your Route credential never leaves the server.
app.popmcp.com/mcpAsk for something harmless before the agent changes anything. Writes run as soon as it calls them, so confirm it reads the right account first.
Where is the package with this tracking number on order 11003271211
route_get_shipmentok
Then just ask for the work
“Where is the package with this tracking number on order 11003271211”
“Price protection for this cart, send the order to Route, then add its package and tracking number”
“Two items from order 2210 moved to a second box, so update the first shipment and add the new one”
“Order 1042 was canceled, so cancel its shipment and the order in Route”
One hosted endpoint, registered once per client. The same tools and the same permissions, whichever window the request comes from.
Add the PopMCP URL under Customize → Connectors and the tools appear in every chat.
The same endpoint, registered in the browser. Nothing to install on the machine you are working from.
Register PopMCP as a custom connector, then let ChatGPT read and update the account.
Wire the endpoint into Codex or the Codex CLI when a task needs live business context, not a fixture.
Register the remote MCP server in OpenCode's config for terminal-first and scripted agent runs.
Add PopMCP as an MCP server in Z.ai's desktop app and work the account from the same window.
FAQ
What teams ask before putting Route behind an AI client.
One token. Copy the Secret API token from the Admin section of the Route dashboard, or from the email Route sent when your account was made, and paste it into PopMCP. There is no app to register and no redirect URL. The Test-Secret token, which starts with test-, works too, and Route flags the orders it creates as test orders.
10 operations, which is every order, shipment and quote call Route publishes: 8 write and 2 read. 8 load into your AI client by default, along with two helpers: one checks several packages at once, and one finds the courier code a shipment needs. The two older order calls stay searchable.
No. Route publishes no call to list orders or shipments, read an order, or read or file a claim, so no connector can offer them. The agent reads one package at a time, and it needs the tracking number and your store's order number to do it. Use the Route dashboard for claims.
It can. With a live token, create_order makes a real order in Route, protected when insurance_selected is true, and cancel_order tells Route an order was canceled or that protection was removed. To try things first, connect the Test-Secret token. To block changes entirely, use a read-only connection, which leaves tracking and quotes.
No. get_quote prices protection for a cart and creates no order. It needs your merchant ID, which starts with merch_ and is shown in the Route dashboard. You can save it under More options when you connect, so the agent does not have to ask.
Not through this connector. Route describes webhooks for refund, replacement and return events, but publishes no call to set one up, so there is nothing for the agent to subscribe to. Ask Route support about setting them up for your store.
No. PopMCP hosts it and gives you a Streamable HTTP MCP URL. There is nothing to deploy, no callback URL to register, and no infrastructure to keep running or patch.
Any client that supports a remote Streamable HTTP MCP server: Claude Desktop, Claude Web, Claude Code, ChatGPT custom connectors, Codex and the Codex CLI, OpenCode and Z.ai's ZCode, as well as editors such as Cursor, Windsurf and Zed. Your client signs in to PopMCP with OAuth; the provider credential never leaves the server.
Connect Route in PopMCP first, then run claude mcp add --transport http popmcp https://app.popmcp.com/mcp in a terminal. Inside Claude Code, run /mcp and sign in to PopMCP in the browser window it opens, ticking Route on the consent screen. The Route tools are then available in that session, and no Route credential is stored on your machine.
Loading 12 tool definitions into every conversation burns context before the work starts. PopMCP loads a curated 10-tool set covering the everyday workflows and keeps the rest searchable, so your AI pulls a specialist tool only when a task needs it. Every tool stays searchable, and on Scale the owner can load the full catalog for a teammate's connection.
A tool is something your AI calls, and there are 12 here. A trigger is an event PopMCP watches for on its own. Route has no triggers yet, so everything on this page happens when your AI calls a tool.
Launch a hosted MCP endpoint for Route, keep tool access under control, and start testing real workflow prompts right away.