Spoke Dispatch MCP by usefulapi is answering right now. Last checked 4 min ago. It exposes 23 tools. Last commit 12 Oct 2026.
Read Spoke Dispatch plans, stops, routes and drivers; create and optimize plans; send routes.
Uptime history
4 hours of history
4 hours agonow
100.0%
Uptime 24h
12 of 12 checks
23
Tools
read from the server
121 ms
Response time
average over 24h
0
Stars
last commit 12 Oct 2026
Nothing serious here today
Today is the operative word: we check Spoke Dispatch MCP by usefulapi every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 4 min ago.
run in your terminal
claude mcp add spoke-dispatch --transport http https://spoke-dispatch.usefulapi.io/mcp~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"spoke-dispatch": {
"url": "https://spoke-dispatch.usefulapi.io/mcp"
}
}
}~/.codex/config.toml
[mcp_servers.spoke-dispatch]
url = "https://spoke-dispatch.usefulapi.io/mcp".cursor/mcp.json
{
"mcpServers": {
"spoke-dispatch": {
"url": "https://spoke-dispatch.usefulapi.io/mcp"
}
}
}.vscode/mcp.json
{
"mcpServers": {
"spoke-dispatch": {
"url": "https://spoke-dispatch.usefulapi.io/mcp"
}
}
}Available tools 23
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
spoke
spoke_create_plan
WRITE: create a new route plan for a date (no stops yet, nothing is sent to drivers). Optionally assign drivers (up to 50, they must be active and share the plan's depot) and a depot (default: the team's main depot). Does not optimize or distribute. POST /plans.
spoke_create_stop
WRITE: add one stop to a writable (not yet distributed) plan. Needs an address (text fields or latitude+longitude). The recipient's phone/e-mail are stored on the stop and Spoke may contact the recipient later when the route runs; nothing is sent now. For many stops use spoke_import_stops. POST /plans/{planId}/stops.
spoke_distribute_plan
WRITE (SENDS TO REAL PEOPLE): distribute an optimized plan, which immediately sends each driver of the plan their route on their phone (push notification / message) and locks the plan for edits. Cannot be undone. Only for a plan with 1-10 drivers, and only after the user has explicitly said to send the routes: set confirm_send_to_drivers to true. POST /plans/{planId}:distribute.
spoke_get_depot
One depot by id. GET /depots/{depotId}.
spoke_get_driver
One driver by id. Contains personal data. GET /drivers/{driverId}.
spoke_get_operation
One operation, e.g. the optimization started by spoke_optimize_plan: poll until done is true. GET /operations/{operationId}.
spoke_get_plan
One plan: title, start date, depot, driver ids, route ids, whether it is distributed/writable, optimization state and route overrides. GET /plans/{planId}.
spoke_get_route
One route: title, driver, stop count and state (distributed, started, completed, recipients notified). GET /routes/{routeId}.
spoke_get_stop
One stop of a plan with address, recipient, timing, ETA, route and delivery outcome (attempted, succeeded, notes, photo/signature links). Contains personal data. GET /plans/{planId}/stops/{stopId}.
spoke_get_unassigned_stop
One unassigned stop by id. Contains personal data. GET /unassignedStops/{id}.
spoke_import_stops
WRITE: add up to 100 stops to a writable (not yet distributed) plan in one request (better geocoding than one at a time; Spoke limits imports to 30 requests a minute). Returns the created stop ids and any failures. Recipient contact data is stored on the stops; nothing is sent now. POST /plans/{planId}/stops:import.
spoke_list_custom_stop_properties
The team's custom stop property definitions (ids and names). Their ids are the keys of customProperties on stops. Needs a subscription that includes custom properties (HTTP 403 otherwise). GET /team/customStopProperties.
spoke_list_depots
List depots (start/end addresses, working hours, vehicle type, max stops), up to 20 per page. Use the ids when creating plans. GET /depots.
spoke_list_drivers
List the team's drivers (name, e-mail/phone, active flag, depots, route overrides), up to 50 per page. Contains personal data. GET /drivers.
spoke_list_operations
List long-running operations (plan optimizations): type, done flag, who started it, result (optimized and skipped stops), up to 20 per page. GET /operations.
spoke_list_plan_stops
List the stops of a plan, in pages of up to 10. Stops include recipient names, phones, e-mails and addresses (personal data): page only as far as needed. GET /plans/{planId}/stops.
spoke_list_plans
List route plans (a plan = one day's delivery job: date, depot, drivers, routes), newest first, in pages of up to 20. Filter with e.g. {"title":"Monday run"} or {"startsGte":"2026-10-01"}. GET /plans.
spoke_list_route_stops
List the stops of one route in driving order, in pages of up to 10. Contains personal data: page only as far as needed. GET /routes/{routeId}/stops.
spoke_list_routes
List routes (one driver's run of a plan: stop count, driver, distributed/started/completed state), up to 20 per page. GET /routes.
spoke_list_unassigned_stops
List stops that are not on any plan yet (the inbox of imported orders), in pages of up to 20 (default 20). Contains personal data. GET /unassignedStops.
spoke_optimize_plan
WRITE: start the route optimization of a plan (orders and assigns its stops to its drivers). Rewrites the plan's routes if it was optimized before, and uses Spoke's optimization quota (30 per minute, 100 per 10 minutes). Does NOT send anything to drivers. Returns an operation: poll spoke_get_operation until done. Needs at least one driver and one stop. POST /plans/{planId}:optimize.
spoke_search_stops
Search all stops of the team (planned, unassigned, past) by keyword and/or Spoke's filter language, up to 20 per page. Example filter: address.countryCode = "DE" and deliveryInfo.attempted = false. Filterable: planId, routeId, type, activity, notes, address.*, createdAt, recipient.name/email/phone/externalId, deliveryInfo.state/attempted/succeeded, orderInfo.*. Results include personal data. The search index lags real time by a short while. GET /stops:search.
spoke_update_plan
WRITE: change a plan's title, date, drivers and/or depot. Only the fields you pass change, but driver_ids REPLACES the plan's whole driver list. Fails if the plan is not writable (already distributed). Nothing is sent to drivers. PATCH /plans/{planId}.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://spoke-dispatch.usefulapi.io/mcp | streamable-http | answering | 247 ms | 4 min ago |
Alternatives to Spoke Dispatch MCP by usefulapi
same job, measured the same wayOptimoRoute MCP by usefulapi
by usefulapi
Check OptimoRoute routes, orders and driver events, and create orders or start route planning.
Track-POD MCP by usefulapi
by usefulapi
Read Track-POD orders, routes, drivers, vehicles and proof of delivery; create orders.
Shipday MCP by usefulapi
by usefulapi
Read Shipday orders, carriers and delivery status; create orders and assign drivers.
Pipedrive MCP by usefulapi
by usefulapi
Read deals, persons, organizations, activities and pipelines; create and update CRM records.
OpenF1 MCP by UnClick
by malamutemayhem
Formula 1 sessions, drivers, positions, laps, pit stops, car data, radio, and weather. By UnClick.
Dropbox Sign MCP by usefulapi
by usefulapi
Hosted MCP server for Dropbox Sign — signature requests, templates, and account for AI agents.
UpCloud MCP by usefulapi
by usefulapi
Inspect servers, storage, networks, databases and billing, and start, stop or back up servers.
bunny.net MCP by usefulapi
by usefulapi
Inspect pull zones, storage, DNS and video libraries on bunny.net, and purge caches.
Spoke Dispatch MCP by usefulapi — questions
Answers built from our own checks of this server.
What can Spoke Dispatch MCP by usefulapi do?
It exposes 23 tools, read directly from the server on our last check. Among them: spoke_create_plan, spoke_create_stop, spoke_distribute_plan, spoke_get_depot, spoke_get_driver, spoke_get_operation and 17 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README.
How MCP servers expose tools in the first place →
Is Spoke Dispatch MCP by usefulapi working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 12 of 12 checks got a reply (100.0%), average response time 121 ms. The bar chart above shows every period we have measured.
How do I connect Spoke Dispatch MCP by usefulapi?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Spoke Dispatch MCP by usefulapi need an API key?
No. Spoke Dispatch MCP by usefulapi completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 23 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Spoke Dispatch MCP by usefulapi?
It answers our handshake in 121 ms on average, which is faster than 78% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Spoke Dispatch MCP by usefulapi open source?
Yes — it is published under the MIT licence, written in JavaScript, 0 stars on GitHub and 1 open issue. The source link is on this page, so you can read exactly what it does with your data before you connect it.