Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
Optimoroute is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
15
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Check OptimoRoute routes, orders and driver events, and create orders or start route planning.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http optimoroute-mcp https://optimoroute.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# optimoroute_get_routes, optimoroute_get_orders, optimoroute_search_orders and 12 more
Optimoroute costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
USAll 334 servers
usefulapi334 servers
24 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http optimoroute-mcp https://optimoroute.usefulapi.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
15 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Get the planned routes for one date: per driver/vehicle the duration, distance, loads and the ordered list of stops with scheduled times. Optionally filter to one driver or vehicle and include the encoded polyline, start/end locations and dispatch status. OptimoRoute: GET /get_routes.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| date | string | yes | Date in YYYY-MM-DD format, e.g. 2026-09-30. |
| driverSerial | string | no | Only this driver's route (serial number). |
| driverExternalId | string | no | Only this driver's route (external id). |
| vehicleRegistration | string | no | Only this vehicle's route. |
| includeRoutePolyline | boolean | no | Include the encoded route polyline (large). |
| includeRouteStartEnd | boolean | no | Include each route's start and end locations. |
| includeDispatchStatus | boolean | no | Include whether each route was sent to its driver, and changed since. |
Fetch full order data (location, time windows, assignment, loads, skills, contact) for up to 500 orders by orderNo or id. Each result has its own success flag; missing orders come back with ERR_ORD_NOT_FOUND rather than failing the call. Read-only despite using POST. OptimoRoute: POST /get_orders.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| orders | array | yes | Orders to target, each {"orderNo": "..."} or {"id": "..."}. At most 500. |
Find orders in a date range (at most 35 days) or by a list of orderNo/id, optionally filtered by status (e.g. failed, rejected, unscheduled), with order data and/or scheduling info. Up to 500 per page; pass the returned after_tag with the SAME other parameters to get the next page. Read-only despite using POST. OptimoRoute: POST /search_orders.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| dateRange | object | no | A date range, e.g. {"from": "2026-09-28", "to": "2026-10-02"}. |
| orders | array | no | Orders to target, each {"orderNo": "..."} or {"id": "..."}. At most 500. |
| orderStatus | array | no | Only orders in these statuses. |
| includeOrderData | boolean | no | Include each order's full data. |
| includeScheduleInformation | boolean | no | Include each order's driver, stop number and scheduled time. |
| after_tag | string | no | Cursor from the previous page's after_tag. |
Is this order scheduled, and if so on which driver/vehicle, at which stop number and time, plus the live ETA from the routes sent to drivers. Give orderNo or id. OptimoRoute: GET /get_scheduling_info.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| orderNo | string | no | The user-specified order number. |
| id | string | no | OptimoRoute's unique order id. |
Get the completion status of up to 500 orders (unscheduled, scheduled, on_route, servicing, success, failed, rejected, cancelled) with service start/end times and positions, proof-of-delivery form data (notes, signature and photo URLs, barcodes), the tracking URL and optionally customer feedback. Read-only despite using POST. OptimoRoute: POST /get_completion_details.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| orders | array | yes | Orders to target, each {"orderNo": "..."} or {"id": "..."}. At most 500. |
| includeCustomerFeedback | boolean | no | Include the customer's rating and comment, if customer feedback is configured. |
Read driver-app events for the live routes — on_duty, off_duty, start_route, end_route, start_service, success, failed, rejected, start_time_changed — up to 500 per call. Pass the returned tag as after_tag next time to get only newer events; remainingEvents says whether more are waiting. Events can arrive out of order when devices were offline. OptimoRoute: GET /get_events.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| after_tag | string | no | The tag from a previous call; omit to read from the start. |
Check a planning (route optimization) run started with optimoroute_start_planning: status N new, R running, C cancelled, F finished, E error, plus percentageComplete. OptimoRoute: GET /get_planning_status.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| planningId | integer | yes | The planningId returned by optimoroute_start_planning. |
Have the routes (and customer notifications) for a date been sent to drivers, when, and are they the live routes? Optionally counts routes added, modified or removed since sending. Omit date for the currently live date. OptimoRoute: GET /get_dispatch_status.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| date | string | no | Date to check, YYYY-MM-DD. Omit for the live routes' date. |
| includeRouteChanges | boolean | no | Include counts of routes changed since sending. |
Create one order, or update an existing one, with address geocoding. operation: CREATE (new; errors if orderNo exists), UPDATE (existing only), MERGE (create or update only the fields you send — safest for edits), SYNC (create or REPLACE all fields with what you send). CREATE/SYNC/MERGE of a new order need date, type, location and orderNo or id. A location is either an existing locationNo alone, a
| Parameter | Type | Required | Notes |
|---|---|---|---|
| operation | string | yes | How to apply the order (see description). |
| orderNo | string | no | Your order number, shown in the web app. Used to match existing orders. |
| id | string | no | OptimoRoute's order id. Takes priority over orderNo when matching. |
| date | string | no | Order date, YYYY-MM-DD. |
| type | string | no | D = delivery, P = pickup, T = task. |
| duration | number | no | Service time at the location, in minutes. |
| priority | string | no | L low, M medium (default), H high, C critical. |
| timeWindows | array | no | When the order can be serviced, e.g. [{"twFrom": "10:00", "twTo": "14:00"}]. |
| allowedWeekdays | array | no | Weekdays the order may be scheduled on. Default: all. |
| allowedDates | object | no | Restrict the dates the order may be scheduled, e.g. {"from": "2026-10-01", "to": "2026-10-07"}. |
| allowedDateTimes | array | no | Datetime windows in which the service may begin. |
| assignedTo | no | Force the order onto one driver, e.g. {"serial": "102"} or {"externalId": "444"}. null clears it. | |
| load1 | number | no | Load units #1 (boxes, kg, ...) per your capacity setup. |
| load2 | number | no | Load units #2. |
| load3 | number | no | Load units #3. |
| load4 | number | no | Load units #4. |
| vehicleFeatures | array | no | Required vehicle feature codes. |
| skills | array | no | Required driver skill codes. |
| notes | string | no | Notes for the driver's instructions. |
| string | no | Customer email for notifications. |
Create, update or replace up to 500 orders in one call. No geocoding here: each location must be an existing locationNo or carry latitude+longitude (+ locationNo, address or locationName). Per order, operation MERGE/SYNC/CREATE/UPDATE works as in optimoroute_create_order; by default an order matched by id or orderNo is updated with only the fields sent, otherwise created. Returns a per-order succe
| Parameter | Type | Required | Notes |
|---|---|---|---|
| orders | array | yes | The orders, at most 500. |
Start OptimoRoute's route optimization for a date (or a dateRange for weekly planning, if the plan allows). With the default startWith EMPTY, existing routes for that date are REPLACED; use startWith CURRENT (+ lockType) to keep them. Returns a planningId — poll it with optimoroute_get_planning_status, then read the result with optimoroute_get_routes. Can be cancelled with optimoroute_stop_plannin
| Parameter | Type | Required | Notes |
|---|---|---|---|
| date | string | no | Date to plan, YYYY-MM-DD. Ignored if dateRange is set. |
| dateRange | object | no | Plan several days at once (weekly planning). |
| balancing | string | no | OFF best routes; ON balance workload; ON_FORCE balance and use every driver. |
| balanceBy | string | no | Balance by WT working time or NUM order count. |
| balancingFactor | number | no | 0.0-1.0, how much balancing outweighs route cost (ON_FORCE only). |
| startWith | string | no | EMPTY (default) plans from scratch; CURRENT starts from existing routes. |
| lockType | string | no | With CURRENT: NONE allow changes; ROUTES keep planned routes; RESOURCES keep driver per order. |
| midRouteDepotVisits | string | no | Allow mid-route depot visits (needs Dynamic Mid-Route Depots on the account). |
| depotTrips | boolean | no | Let drivers return to the depot to reload. |
| depotVisitDuration | integer | no | Minutes spent at a depot visit. |
| clustering | boolean | no | Minimize overlap between drivers' routes. |
| useDrivers | array | no | Only plan with these drivers. Default: all available drivers. |
| useOrderObjects | array | no | Only plan these orders. Default: all valid orders on the date. |
| includeScheduledOrders | boolean | no | When planning a subset, keep other orders already scheduled on those drivers (default true). |
Stop a running planning (optimization) process by its planningId. OptimoRoute: POST /stop_planning.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| planningId | integer | yes | The planningId returned by optimoroute_start_planning. |
Change one driver's setup for one date: enable/disable, work hours, assigned vehicle, vehicle capacities, start/end location. WARNING: any existing route for that driver on that date is UNSCHEDULED; re-run planning afterwards. Start/end locations also apply to future optimizations. OptimoRoute: POST /update_driver_parameters.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| externalId | string | yes | The driver's external id from driver administration. |
| date | string | yes | Date in YYYY-MM-DD format, e.g. 2026-09-30. |
| enabled | boolean | no | Enable or disable the driver for this date. |
| workTimeFrom | string | no | Work start, 24-hour HH:MM. |
| workTimeTo | string | no | Work end, 24-hour HH:MM. |
| assignedVehicle | string | no | External id of the vehicle to assign for this date. |
| vehicleCapacity1 | integer | no | Vehicle load capacity #1 for this date. |
| vehicleCapacity2 | integer | no | Vehicle load capacity #2. |
| vehicleCapacity3 | integer | no | Vehicle load capacity #3. |
| vehicleCapacity4 | integer | no | Vehicle load capacity #4. |
| startLatitude | number | no | Start location latitude (needs startLongitude). |
| startLongitude | number | no | Start location longitude (needs startLatitude). |
| startAddress | string | no | Start address shown on reports (needs start coordinates). |
| endLatitude | number | no | End location latitude (needs endLongitude). |
| endLongitude | number | no | End location longitude (needs endLatitude). |
| endAddress | string | no | End address shown on reports (needs end coordinates). |
Set the completion status of up to 500 orders (e.g. mark success, failed or cancelled from an external system), optionally with service start/end times. Each time takes unixTimestamp, utcTime or localTime. Reversible by setting the status again. Returns a per-order success list. OptimoRoute: POST /update_completion_details.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| updates | array | yes | The status updates, at most 500. |
Dispatch the routes for a date to the drivers' mobile app (the web app's Send Routes). This makes that date the live routes and CANNOT be unsent. sendNotifications defaults to FALSE here (OptimoRoute's own default is true); set it true only when you mean to email/SMS customers per the account's Order Tracking settings. Returns ERR_NOTHING_TO_SEND if nothing changed since the last send. Confirm wit
| Parameter | Type | Required | Notes |
|---|---|---|---|
| date | string | yes | Date in YYYY-MM-DD format, e.g. 2026-09-30. |
| sendNotifications | boolean | no | Also send customer notifications. Default false in this tool. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Optimoroute or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.11.1.
1.11.1
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Optimoroute can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.