Spoke Dispatch
Manage delivery routes, drivers, stops and optimize plans for your Spoke Dispatch account.
Connect to Spoke Dispatch to view and manage delivery plans, routes, drivers and stops. Create new plans, add stops, optimize routes and send them to drivers. Requires a Spoke Dispatch account and API access.
Try asking Muse: "Create a delivery plan for tomorrow, add customer stops, optimize the routes and send them to my drivers."
See the most upvoted connectors
Source: Found in the official MCP Registry (io.usefulapi/spoke-dispatch) · First listed October 29, 2026
Last 24 hours
Each bar is one check, every 15 minutes. Green means it answered. Last checked 1 h ago.
Is it safe to connect?
What Muse can see: It does not ask you to sign in, so it cannot see your accounts. It only sees what Muse sends it from your request.
Before it acts: Read what Muse plans to do before you approve it, and remove the app from Muse when you stop using it.
musedirectory.ai is not part of Meta. More about how Muse handles your information
How to add it to Muse
Not in Muse's Connectors list yet, but Muse can still use it. Copy the request below and paste it into Muse. Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.
https://spoke-dispatch.usefulapi.io/mcpNot in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
Also use it in ChatGPT or Claude
Spoke Dispatch is a remote MCP server, so any assistant that can add a custom connector by link can use it. Same link, same tools.
Add it to ChatGPT
- 1
Open ChatGPT settings
In ChatGPT, open Settings, then Connectors (called Apps & Connectors on some accounts).
- 2
Turn on developer mode
Under Advanced settings, switch on Developer mode. That is what lets you add a connector by link.
- 3
Create the connector
Choose Create, give it a name, paste the link as the MCP server URL, and save. If it needs a sign-in, ChatGPT asks for it here.
- 4
Use it in a chat
Start a chat, open the tools menu, pick the connector, and ask. ChatGPT asks before it runs a tool the first time.
Custom connectors need a paid ChatGPT plan, and on Team, Enterprise and Edu accounts only an admin can add them. Our "Working" label means the server answered us; it cannot tell whether your plan lets you add it. All connectors that work in ChatGPT
Add it to Claude
- 1
Open Claude settings
In Claude, open Settings, then Connectors.
- 2
Add a custom connector
Choose Add custom connector, give it a name, and paste the link.
- 3
Connect and use it
If it needs a sign-in, Claude sends you to it. Then turn the connector on in a chat from the tools menu and ask.
Custom connectors are available on paid Claude plans; on Team and Enterprise accounts an admin may need to add them. Our "Working" label means the server answered us; it cannot tell whether your plan lets you add it. All connectors that work in Claude
https://spoke-dispatch.usefulapi.io/mcpWhat people ask Muse to do
Technical details: safety screening, tools, response time and recent checks
Response time at the last check: 40ms. Worked in 100% of checks over 30 days.
Screening · October 29, 2026
Screened, no issues found
Screening looks for known threats and hidden instructions at the time of the check, and runs again weekly and whenever the tool list changes. It cannot see the server's code, so only connect what you need and review what Muse asks to do. How screening works.
Tools · 23
spoke_list_plansList 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_get_planOne plan: title, start date, depot, driver ids, route ids, whether it is distributed/writable, optimization state and route overrides. GET /plans/{planId}.spoke_list_plan_stopsList 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_get_stopOne 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_search_stopsSearch 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, recipienspoke_list_unassigned_stopsList 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_get_unassigned_stopOne unassigned stop by id. Contains personal data. GET /unassignedStops/{id}.spoke_list_driversList the team's drivers (name, e-mail/phone, active flag, depots, route overrides), up to 50 per page. Contains personal data. GET /drivers.spoke_get_driverOne driver by id. Contains personal data. GET /drivers/{driverId}.spoke_list_depotsList depots (start/end addresses, working hours, vehicle type, max stops), up to 20 per page. Use the ids when creating plans. GET /depots.spoke_get_depotOne depot by id. GET /depots/{depotId}.spoke_list_routesList routes (one driver's run of a plan: stop count, driver, distributed/started/completed state), up to 20 per page. GET /routes.spoke_get_routeOne route: title, driver, stop count and state (distributed, started, completed, recipients notified). GET /routes/{routeId}.spoke_list_route_stopsList 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_operationsList long-running operations (plan optimizations): type, done flag, who started it, result (optimized and skipped stops), up to 20 per page. GET /operations.spoke_get_operationOne operation, e.g. the optimization started by spoke_optimize_plan: poll until done is true. GET /operations/{operationId}.spoke_list_custom_stop_propertiesThe 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_create_planWRITE: 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_update_planWRITE: 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}.spoke_create_stopWRITE: 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_impspoke_import_stopsWRITE: 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 nospoke_optimize_planWRITE: 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: pospoke_distribute_planWRITE (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 explRecent checks
Link
https://spoke-dispatch.usefulapi.io/mcpQuestions about Spoke Dispatch in Muse
How do I connect Spoke Dispatch to Muse?
Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use Spoke Dispatch to help me. It is a free service with an MCP server at https://spoke-dispatch.usefulapi.io/mcp. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.
Is Spoke Dispatch working right now?
At the last check (October 29, 2026, 10:45 UTC) the endpoint was working, answering in 40ms. Over the last 7 days it answered 100% of health checks. It is checked every 15 minutes.
Is Spoke Dispatch safe to connect to Muse?
It was screened on October 29, 2026 with the result "screened, no issues found". Screening checks the domain against threat feeds and reads the tools for hidden instructions and requests for passwords or card numbers. It cannot see the server's code, so grant only the access you need.
What can Spoke Dispatch do in Muse?
It exposes 23 tools, including spoke_list_plans, spoke_get_plan, spoke_list_plan_stops, spoke_get_stop. For example, you could ask Muse: "Create a delivery plan for tomorrow, add customer stops, optimize the routes and send them to my drivers."
Follow Spoke Dispatch
Made this app? Claim it or get a status badge
Is this yours?
This listing was added from public sources (Found in the official MCP Registry (io.usefulapi/spoke-dispatch)). If you build Spoke Dispatch, claim it to correct the details and get your badge.
Paste this on your site or README. It always shows the latest check.
<a href="https://musedirectory.ai/connector/spoke-dispatch"><img src="https://musedirectory.ai/badge/spoke-dispatch.svg" alt="Spoke Dispatch on musedirectory.ai" width="236" height="40"></a>