Optimize routes right in your chat or connect your Routific account to see the routes on Routific.
https://mcp.routific.com/mcp
Want the plan here in chat, or set up in your Routific account so you can see it on a map and dispatch it?
Tomorrow’s route is ready: 5 stops on 1 route, starting and ending at 455 Granville St — about 101 min on the road.
Your agent asks where you want the plan: right here in chat, or set up in your Routific account with a link to the map. Either way it optimizes once.
optimize_route · create_optimization, or straight into Routific with show_on_map.Pick your client. Quick routes work right away; when you ask for a bigger plan or a map, you’ll be asked to sign in with Routific — sign up free if you don’t have an account.
https://mcp.routific.com/mcp
https://mcp.routific.com/mcp
claude mcp add --transport http routific https://mcp.routific.com/mcp
401 that points
your client to Routific sign-in (standard MCP OAuth).{
"mcpServers": {
"routific": {
"type": "http",
"url": "https://mcp.routific.com/mcp"
}
}
}
optimize_route toolOne tool, four parameters. Routific solves the underlying traveling-salesman problem and returns a schedule with machine-learned ETAs — not just a stop order.
| Name | Type | Description |
|---|---|---|
stops required | string[] · 2–8 | Addresses to visit, e.g. “800 Robson St, Vancouver, BC”. Include city + region for reliable geocoding. |
start_address optional | string | Where the driver starts. Defaults to the first entry in stops. |
return_to_start optional | boolean | End the route back at the start. Default false. |
departure_time optional | string | 24h hh:mm departure used to compute ETAs. Default 09:00. |
| Field | Description |
|---|---|
route[] | Stops in optimal order: address, eta, departure, and distance_from_previous_m. |
total_travel_time_minutes | Driving + service time for the whole route. |
total_distance_km | Total driving distance. |
unserved | Stops that couldn’t be routed, with the reason (e.g. address not found). |
optimize_route is for quick answers, capped at 8 stops. Splitting a longer
list into chunks and optimizing them separately does not produce an optimized
route — the chunks are only locally optimal. For more stops, multiple drivers, or time
windows, your agent uses create_optimization instead (sign in with Routific),
which has no stop limit.
Sign in with Routific and your agent gets these tools on top of optimize_route.
It works in your workspace as you, and checks with you before deleting anything.
Plan whole fleets in chat — nothing is saved until you ask for the map.
create_optimizationget_optimization · get_schedule_solutionTurn the plan into real routes in Routific, and get a link to them.
create_orderscreate_routesschedule_orders · get_schedule_actionKeep the day’s orders up to date from chat.
get_order · search_ordersupdate_orderdelete_order · delete_orders Asks firstCheck how the day’s routes are shaping up.
get_route · get_route_timelinesearch_routes · list_scheduleslist_workspacesMissing something you’d want your agent to do? Tell us — your ideas shape what ships next.
The Routific MCP server is in beta. A quick note from you goes straight to the team building it, and it’s the fastest way to make your assistant better at routing. Good or bad, we’d love to hear how it went.
Everything on this page works today, and we’re actively improving it — expect answers, tools, and features to change as we learn from real use. Orders and routes your agent adds to Routific are kept like anything else in your account. If something doesn’t behave, let us know.
Yes. Quick routes in chat (one driver, up to 8 stops) are free and need no account. Bigger plans and seeing routes on a map need a Routific account — the free plan includes 100 orders a month.
You sign in to Routific and approve what your assistant may do. When you ask to see a plan on a map, it adds the orders and routes to your Routific account and sends you a link — dispatching to drivers stays with you, in the Routific app. It asks before deleting orders. You can disconnect at any time from your assistant’s connector settings.
Your assistant will let you know. Log in to your Routific account and upgrade your plan to keep going.
Quick routes send only the addresses you provide to the Routific Engine API
(api.routific.com) to geocode and optimize them — nothing is saved. Orders
and routes your agent creates are stored in your Routific account, like anything else
you create in Routific. A depot given as an address is looked up on OpenStreetMap to find
its coordinates. This server stores nothing. See the
Routific privacy policy.
They’re powered by machine learning. The Routific Engine learns from millions of real-world deliveries every month, so its travel-time predictions keep getting more accurate — the same blazing-fast engine behind our route optimization API. Each ETA combines your chosen departure time (default 09:00), ML-predicted driving times between stops, and 5 minutes of service time at each stop.
Plain addresses work — they’re geocoded automatically. For best results include the city and region (e.g. “800 Robson St, Vancouver, BC, Canada”).
Any client that supports remote MCP servers with sign-in: Claude (web, desktop, mobile), ChatGPT, Claude Code, Cursor, VS Code, and most other MCP-capable tools.
Routific plans routes for entire fleets — multiple drivers, time windows, live tracking, and proof of delivery. Start free with 100 orders a month and plan it from your AI agent. Trusted by 1,000+ delivery businesses.