← Registry tracker

Fleet Route Optimizer

Plan multi-vehicle delivery routes: splits stops across vans, orders each route, respects time windows and capacities. Free.

Category
Productivity
View in the Claude registry
Integration details

Description

Fleet Route Optimizer plans delivery or service routes for one or more vehicles leaving one depot. Give it your depot, your stops (street addresses or lat/lon) and your vehicles; it decides which vehicle serves which stop and in what order, and returns arrival times, load carried, and any stops that could not be served and why. It uses Google OR-Tools (guided local search) over real road driving times, not straight-line distance. Handles: - Time windows per stop, plus service time at each stop - Up to three capacity limits per vehicle (e.g. weight, volume, pallets) - Per-vehicle route time limits - Re-optimizing from previous routes after you add or change stops - Plain-language notes, such as why a van leaves the depot late or how short total capacity is Limits per call: 100 stops, 50 addresses to look up, 25 vehicles. One depot, deliveries only, one trip per vehicle. Results are the best routes found in the time allowed, not a proof of optimality. Free, no sign-up, no API key. Built by an operations research analyst with 20+ years in routing and scheduling. A web version with Excel upload is at https://routing.kindoflost.com

Integration type
Connector
Verification status
Community connector
Platform
Claude
Category
Productivity

The broad Category that contains the Primary Subcategory.

Primary Subcategory
Freight & Logistics Operations

The Primary Subcategory used for this profile’s headline score.

Secondary Subcategories
None listed

Other Subcategories where the Integration is listed.

Access
No account required
First tracked
2026-09-28
Tool count
4
Geography
US

Claude Discoverability Score

Claude Connector discovery is coming soon

Community Connectors only appear in Claude’s registry.Once verified, organic discovery begins and we can calculate your score.Read more about Community Connector verification.

No spam. Unsubscribe any time.

No spam. Unsubscribe any time.

What discovery looks like

Claude showing a list of relevant Connectors in a conversation

Claude can surface verified Connectors when they match a user’s Prompt.

Primary Subcategory
7 scoredVerified connectors by score · Community connectors A–Z
Primary Subcategory
1CargoAi81/100
2Shippo59/100
3Terminal4937/100
4Flexport7/100
5Kpler7/100
—Dock OptimizerPending VerificationGet notified
—DockflowPending VerificationGet notified
—FastQuotesPending VerificationGet notified
—Fleet Route OptimizerPending VerificationGet notified
—FreightPOPPending VerificationGet notified
—LetMeShip NextPending VerificationGet notified
—NoMap RouterPending VerificationGet notified
—OpenTrackPending VerificationGet notified
—OptilogicPending VerificationGet notified
—RoutalPending VerificationGet notified
—RoutificPending VerificationGet notified
—Routing24Pending VerificationGet notified
—ShipdayPending VerificationGet notified
—ShipthisPending VerificationGet notified
Recommended guideHow to get your Claude Connector organically discoveredFollow the practical steps agents use to find, shortlist, and choose your Connector.Read guide
Tools

4 tools agents can invoke

Fleet Route Optimizer FAQ
How do I improve a Community connector's discoverability?

The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.

What are Fleet Route Optimizer alternatives on Claude?

As of 2026-09-29, Fleet Route Optimizer competes with CargoAi, Shippo, Terminal49, Flexport, Kpler, Sendcloud, MyGeotab MCP, Dock Optimizer, Dockflow, FastQuotes, FreightPOP, LetMeShip Next, NoMap Router, OpenTrack, Optilogic, Routal, Routific, Routing24, Shipday, Shipthis in Claude Freight & Logistics Operations, ranked by public Discoverability Score.

Where is this profile measured?

This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.