RouteSavvy MCP Server

ClaudeCommunityby OnTerra Systems

RouteSavvy MCP Server connects Claude directly to RouteSavvy's route-optimization engine, turning a list of customer visit locations into driver-ready, turn-by-turn itineraries — all from a single conversation, no routing console or API programming required. It fits any operation that sends people to multiple stops a day: last-mile and courier delivery, field service and repair, route sales and merchandising, home healthcare, utility servicing, property inspections, and door-to-door sales. Share your stop locations (CSV, Excel, PDF or any file type, or a plain list typed into chat) with your driver roster, and Claude builds the optimized run: up to 1,000 stops and 50 vehicles per request, each vehicle starting and ending at its own depot or a shared one, optimized by drive time or distance. Built for real dispatch operations: give any stop an arrival time window and priority level, so if everything can't fit, lower-priority stops are left for the next run — never a hard failure. Set each driver's shift hours and a break window, and RouteSavvy factors it in, skipping the break if the route ends before it's due. Every itinerary includes leg-by-leg directions, a route path ready to plot on a map, and a plain-language report on any unreachable stop. It can also minimize the number of vehicles needed to cover all stops, so you do more with fewer drivers. No dashboard to learn — just tell Claude what you need in plain English: "assign 3 drivers to the customer visits in my CSV," "only route the restaurant work orders," "give the loading-dock stops top priority." Claude reads the file and returns a dispatcher-ready itinerary per driver. Default limits: 1,000 stops and 50 vehicles per run (higher on request); trial connections are capped at 100 stops and 5 vehicles for 14 days. Stop and driver locations must be latitude/longitude coordinates — geocode street addresses first.