Routific

Route optimization for agents, free up to 8 addresses.

Given a list of addresses, Routific will optimize a route connecting all addresses. Optionally add start and end locations & departure times — we'll return the optimized sequence with ETAs and distances.

MCP connector

Server URL: https://mcp.routific.com/mcp
Login: None
Protocol: MCP 2025-11-25
Instructions: Optimize routes with Routific (https://routific.com) — answered in chat, or set up on a map in the user's Routific account.
STEP 1 — before optimizing, ask once where they want the result, unless their request already says: "Do you want the plan here in chat, or set up in your Routific account so you can see it on a map and dispatch it to your drivers? The map needs a Routific account (free plan: 100 orders a month, sign up at https://plan.routific.com/signup?utm_source=mcp), and the stops are added as orders to your account." If they mention a map, Routific, the app, drivers' phones or dispatching, that's the map. If they say "just tell me" or similar, that's chat. Then run exactly ONE optimization for that choice — never plan in chat first and then again on the map.
STEP 2 — chat:
: one driver, up to 8 stops. No sign-in, nothing saved.
: more stops, several drivers/vehicles, time windows, or capacity. Requires signing in; nothing is saved. It waits and returns the plan; only very large runs need a follow-up with and . Never split a long stop list into several calls: separately optimized chunks aren't an optimized route — use instead. If they later ask for the chat plan on a map, use and say Routific plans it again, so the result can differ slightly.
STEP 3 — map: call ONCE with every stop, one driver per vehicle, and the date (the day they mentioned, otherwise today). Pass the depot as { address } in each driver's startLocation (and endLocation if they return), or coordinates the user gave; never invent coordinates. Service time (duration) is in seconds — 300 is 5 minutes. adds the orders, creates the routes, optimizes only those, waits, and returns view_in_app with a short summary. The user chose to see the plan in Routific, so the link IS the answer: start your reply with it on its own line, bold — 🗺️ [Open in Routific →](view_in_app) — then one or two short lines (date, stops and routes, anything unscheduled, where the depot was placed). Don't list the stops or ETAs. From Routific they can adjust the plan and dispatch it to their drivers' phones (or ask you to publish it).
To change orders afterwards, use the ids from , or with include_orders to find a day's orders. Use for the same change on many orders (one call, not one per order); addTags keeps existing tags. Tags are routing requirements (an order tagged X needs a route tagged X), so for a plain label prefer customFields or instructions. Other tools: , , , .
Drivers: puts a driver on a route (by name — it matches the organization's drivers — or uuid); takes them off; shows who's available. Route uuids come from or . On a published route the change reaches the driver's app straight away, so confirm first. Publishing: sends EVERY route on a date to the drivers' Routific app and starts customer notifications. Before calling, say which routes and drivers will go out and wait for an explicit yes. Unchanged published routes and empty routes are skipped; unpublishing is done in the Routific app. Confirm before deleting orders. Tools that take workspaceUuid can omit it when the account has one workspace.

Tools

Reads data13

Changes data5

Deletes or can't be undone7

Skills

None in the store listings or on the server

MCP connector

Server URL

https://mcp.routific.com/mcp

None

Protocol

MCP 2025-11-25

Instructions

Optimize routes with Routific (https://routific.com) — answered in chat, or set up on a map in the user's Routific account.

STEP 1 — before optimizing, ask once where they want the result, unless their request already says: "Do you want the plan here in chat, or set up in your Routific account so you can see it on a map and dispatch it to your drivers? The map needs a Routific account (free plan: 100 orders a month, sign up at https://plan.routific.com/signup?utm_source=mcp), and the stops are added as orders to your account." If they mention a map, Routific, the app, drivers' phones or dispatching, that's the map. If they say "just tell me" or similar, that's chat. Then run exactly ONE optimization for that choice — never plan in chat first and then again on the map.

STEP 2 — chat:

: one driver, up to 8 stops. No sign-in, nothing saved.

: more stops, several drivers/vehicles, time windows, or capacity. Requires signing in; nothing is saved. It waits and returns the plan; only very large runs need a follow-up with and . Never split a long stop list into several calls: separately optimized chunks aren't an optimized route — use instead. If they later ask for the chat plan on a map, use and say Routific plans it again, so the result can differ slightly.

STEP 3 — map: call ONCE with every stop, one driver per vehicle, and the date (the day they mentioned, otherwise today). Pass the depot as { address } in each driver's startLocation (and endLocation if they return), or coordinates the user gave; never invent coordinates. Service time (duration) is in seconds — 300 is 5 minutes. adds the orders, creates the routes, optimizes only those, waits, and returns view_in_app with a short summary. The user chose to see the plan in Routific, so the link IS the answer: start your reply with it on its own line, bold — 🗺️ [Open in Routific →](view_in_app) — then one or two short lines (date, stops and routes, anything unscheduled, where the depot was placed). Don't list the stops or ETAs. From Routific they can adjust the plan and dispatch it to their drivers' phones (or ask you to publish it).

To change orders afterwards, use the ids from , or with include_orders to find a day's orders. Use for the same change on many orders (one call, not one per order); addTags keeps existing tags. Tags are routing requirements (an order tagged X needs a route tagged X), so for a plain label prefer customFields or instructions. Other tools: , , , .

Drivers: puts a driver on a route (by name — it matches the organization's drivers — or uuid); takes them off; shows who's available. Route uuids come from or . On a published route the change reaches the driver's app straight away, so confirm first. Publishing: sends EVERY route on a date to the drivers' Routific app and starts customer notifications. Before calling, say which routes and drivers will go out and wait for an explicit yes. Unchanged published routes and empty routes are skipped; unpublishing is done in the Routific app. Confirm before deleting orders. Tools that take workspaceUuid can omit it when the account has one workspace.

Tools