Spoke Dispatch MCP server

Read Spoke Dispatch plans, stops, routes and drivers; create and optimize plans; send routes. Hosted by usefulapi: connect it to Claude, ChatGPT, Cursor or any MCP client.

Connect Spoke Dispatch50 free tool calls a month

What can I ask?

Turn on the Spoke Dispatch connector, then ask in plain words. The AI picks the tools.

What delivery plans do I have for tomorrow?
Which drivers do we have on the team and are they active?
How many stops are on today's delivery routes for each driver?
Create a new delivery plan for tomorrow named Friday Deliveries.

What you can do with Spoke Dispatch in Claude and ChatGPT

For delivery dispatchers who plan and send driver routes in Spoke Dispatch.

Review a day's plans and routes

The AI lists plans with date, depot and drivers and opens one. It reads the routes with driver, stop count and whether they were distributed, started or completed.

Find stops that failed or were not attempted

The AI searches stops by keyword or filter, for example attempted = false in one country, and opens a stop to read the delivery outcome, notes and photo links.

See the stops that are not on a plan yet

The AI lists imported stops that are on no plan, with their addresses, so you know what still has to be planned.

List the drivers and depots

The AI lists drivers with active flag and depots, and depots with addresses, working hours and maximum stops.

Create a plan and add its stops

The AI creates a plan for a date with a depot and drivers, then adds stops one by one or up to 100 at once. Nothing is sent to drivers.

Changes data

Optimize a plan and send it to drivers

The AI starts the optimization, checks until it is done, and after your clear go-ahead sends each driver their route on their phone. Sending cannot be undone.

Changes data

How do I connect Spoke Dispatch?

Before you connect

The login page asks for your Spoke Dispatch API key.

Create a key in Spoke Dispatch under Settings → Integrations → API. The key acts for your whole team; keep it secret. Your key is used only to call the Spoke Dispatch API on your behalf; it is never shown to anyone.

Claude claude.ai · Desktop

Open Customize → Connectors, then click + Add → Add custom connector.
Enter the name Spoke Dispatch and this URL, then click Add:
https://spoke-dispatch.usefulapi.io/mcp
Claude opens the login page: enter your Spoke Dispatch API key.
In a chat, click + → Connectors and turn on Spoke Dispatch.

Team and Enterprise: an Owner adds the connector for the organization first.

ChatGPT chatgpt.com

Open Plugins, click +, then Add custom MCP server.
Enter the name Spoke Dispatch and this URL, choose OAuth as the authentication, confirm the warning and create it:
https://spoke-dispatch.usefulapi.io/mcp
ChatGPT opens the login page: enter your Spoke Dispatch API key.
In Plugins, install Spoke Dispatch, then choose it in a chat.

No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.

Claude Code

Run this command, then run /mcp in Claude Code to log in:

claude mcp add --transport http spoke-dispatch https://spoke-dispatch.usefulapi.io/mcp

Cursor

Add to Cursor or add this to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "spoke-dispatch": {
      "url": "https://spoke-dispatch.usefulapi.io/mcp"
    }
  }
}

VS Code

Add to VS Code or add this to .vscode/mcp.json:

{
  "servers": {
    "spoke-dispatch": {
      "type": "http",
      "url": "https://spoke-dispatch.usefulapi.io/mcp"
    }
  }
}

Codex

Run these commands. The second one opens the login page:

codex mcp add spoke-dispatch --url https://spoke-dispatch.usefulapi.io/mcp

codex mcp login spoke-dispatch

Other clients

Windsurf, Cline, Zed and other MCP clients: add this URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser.

https://spoke-dispatch.usefulapi.io/mcp

Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Spoke Dispatch API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.

Pricing

Plan	Price	Limit
Free	$0	50 tool calls / month
Proper team	$9/mo · $90/yr	10,000 tool calls / month
Pro+per team	$39/mo · $390/yr	100,000 tool calls / month

Each paid plan covers this Spoke Dispatch server only. Ask your AI to run spoke_upgrade and choose Pro or Pro+, billed monthly or yearly (it returns a Stripe Checkout link). If you already have Pro, ask to change it to Pro+. The change requires your confirmation, keeps your billing interval and charges the price difference for the rest of the period immediately. Cancel any time with spoke_cancel_subscription: your paid plan continues to the end of the paid period, with no refund for the current period, and asking to resume the same plan with spoke_upgrade before then undoes the cancel. Or write to support@usefulapi.io.

Tools 27

Show all 27 tools (the AI picks them for you)

Read only · 17

List plansspoke_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 planspoke_get_plan
One plan: title, start date, depot, driver ids, route ids, whether it is distributed/writable, optimization state and route overrides.
List plan stopsspoke_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 stopspoke_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.
Search stopsspoke_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.
List unassigned stopsspoke_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 unassigned stopspoke_get_unassigned_stop
One unassigned stop by id. Contains personal data.
List driversspoke_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 driverspoke_get_driver
One driver by id. Contains personal data.
List depotsspoke_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 depotspoke_get_depot
One depot by id.
List routesspoke_list_routes
List routes (one driver's run of a plan: stop count, driver, distributed/started/completed state), up to 20 per page.
Get routespoke_get_route
One route: title, driver, stop count and state (distributed, started, completed, recipients notified).
List route stopsspoke_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.
List operationsspoke_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 operationspoke_get_operation
One operation, e.g. the optimization started by spoke_optimize_plan: poll until done is true.
List custom stop propertiesspoke_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).

Changes data · 6

Create planspoke_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.
Update planspoke_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.
Create stopspoke_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.
Import stopsspoke_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.
Optimize planspoke_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.
Distribute plan to driversspoke_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.

Your usefulapi plan · 4

Usage status (free-tier meter)spoke_usage_status
Report the caller's current usage: the plan, calls used this month, the limit of the plan (the free monthly cap or the Pro fair use limit), remaining, and whether the limit is reached. Read-only; does not count against the meter.
Request a missing featurespoke_request_feature
Tell usefulapi that the user needs something the Spoke Dispatch tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter.
Upgrade to Pro or Pro+spoke_upgrade
Get a paid plan for Spoke Dispatch (the free tier caps monthly usage). Pro: 10,000 tool calls a month, for normal use — plan "monthly" ($9/month) or "yearly" ($90/year, 2 months free). Pro+: 100,000 tool calls a month, for automations and heavy use — plan "plus" ($39/month) or "plus_yearly" ($390/year). Without a plan it returns both Pro and Pro+, each with a payment link, for the user to choose; with a plan, one link. An existing Pro subscription changes to Pro+ in place: call without confirm first, as the reply states the exact charge for this account (the price difference for the rest of the period, or in a free Pro trial the full Pro+ price, as the trial ends); then call with confirm: true. Cancel any time: the plan then runs to the end of the paid period, so it also suits a one-time job. A link opens Stripe Checkout in the browser; after payment the account upgrades automatically. Does not count against the meter.
Cancel the Pro subscriptionspoke_cancel_subscription
Cancel the caller's Spoke Dispatch Pro subscription at the end of the paid period (no refund for the current period; Pro continues until then, then the free tier applies). Requires confirm: true. Run spoke_upgrade later to undo the cancel before the period ends. Does not count against the meter.

FAQ

What can I do with Spoke Dispatch in Claude or ChatGPT?

Review a day's plans and routes. Find stops that failed or were not attempted. See the stops that are not on a plan yet. List the drivers and depots. Create a plan and add its stops. Optimize a plan and send it to drivers. See what you can do for the details.

Is this an official Spoke Dispatch product?

No. usefulapi is an independent service. It is not affiliated with or endorsed by Spoke Dispatch. The server calls the Spoke Dispatch API with your own Spoke Dispatch access, so it sees only the data that your account can see.

Can I connect Spoke Dispatch to Claude or ChatGPT?

Yes. In Claude, add this server's URL as a custom connector. In ChatGPT, add it as a custom MCP server in Plugins. Then log in once. Cursor, VS Code, Claude Code and Codex work too. See the setup steps.

What do I need to connect?

The login page asks for your Spoke Dispatch API key. See Before you connect for where to find it.

Do I put my Spoke Dispatch key or an Authorization header in the client config?

No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Spoke Dispatch API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.

How do you keep my Spoke Dispatch credentials?

The login stores them encrypted in the authorization grant of your connection. The server uses them to call the Spoke Dispatch API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in Spoke Dispatch.

Can the AI change my Spoke Dispatch data?

Yes, if you approve it. 6 of the 23 Spoke Dispatch tools can create or change data. The other 17 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.

What does it cost?

The Free plan gives 50 tool calls / month. Pro costs $9/mo or $90/yr, with 10,000 tool calls / month. Pro+ costs $39/mo or $390/yr, with 100,000 tool calls / month. Each subscription covers this Spoke Dispatch server only. Cancel any time: your paid plan then runs to the end of the paid period. Run spoke_usage_status to see how many calls you used.

How do I subscribe or cancel?

Ask the AI to run spoke_upgrade and choose Pro or Pro+, billed monthly or yearly: it returns a Stripe Checkout link. If you already have Pro, ask to change it to Pro+. After you confirm, your existing subscription changes in place, keeps its billing interval and charges the price difference for the rest of the period immediately. To cancel, run spoke_cancel_subscription. Your paid plan continues to the end of the paid period.

What if a Spoke Dispatch tool that I need is missing?

Tell the AI what you wanted to do. It can send the request with spoke_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.

Which AI clients can I use?

Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, ChatGPT, Codex, Cursor, VS Code, Windsurf and others.

This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.

Need a tool this server does not have, or a connection to another system? We build custom integrations and MCP servers.

Spoke Dispatch MCP server

What can I ask?

What you can do with Spoke Dispatch in Claude and ChatGPT

Review a day's plans and routes

Find stops that failed or were not attempted

See the stops that are not on a plan yet

List the drivers and depots

Create a plan and add its stops

Optimize a plan and send it to drivers

How do I connect Spoke Dispatch?

Before you connect

Claude claude.ai · Desktop

ChatGPT chatgpt.com

Claude Code

Cursor

VS Code

Codex

Other clients

Pricing

Tools 27

Read only · 17

Changes data · 6

Your usefulapi plan · 4

FAQ

More Documents & Delivery MCP servers