io.usefulapi/spoke-dispatch

up checked 2026-11-11T01:38:36.993Z

Unclaimed · Unverified

Agent searches it appeared in, last 30 days: 0. Run this server? Claim the listing: verified label, uptime alerts and analytics.

Publisher-provided title

Spoke Dispatch MCP by usefulapi

Publisher-provided description

Read Spoke Dispatch plans, stops, routes and drivers; create and optimize plans; send routes.

Summary by lookupd

Reads and manages delivery route plans, stops, drivers and depots; can create plans, optimize routes and dispatch them to drivers.

Install

Claude Code, remote (streamable-http)

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

Codex, remote (streamable-http)

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

Cursor, remote (streamable-http) → .cursor/mcp.json

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

Other clients: docs. Or tell your agent: Set up lookupd for me: read https://lookupd.com/agent.md and follow it.

Tools (23 tools)

Publisher-provided text

• 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
• 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_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 /p
• 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
• 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
• 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_get_unassigned_stop One unassigned stop by id. Contains personal data. GET /unassignedStops/{id}.
• 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_get_driver One driver by id. Contains personal data. GET /drivers/{driverId}.
• 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_get_depot One depot by id. GET /depots/{depotId}.
• 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_get_route One route: title, driver, stop count and state (distributed, started, completed, recipients notified). GET /routes/{routeId}.
• 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_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_get_operation One operation, e.g. the optimization started by spoke_optimize_plan: poll until done is true. GET /operations/{operationId}.
• 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 prop
• 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 pla
• 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 pl
• 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 t
• 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 m
• 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 Spo
• 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 / mess

Details

• Version: 1.24.3
• Transports: streamable-http
• Uptime (7 days): 100%
• Median latency: 623 ms
• First indexed: 2026-11-01T10:06:17.013Z
• Last seen in registry: 2026-11-11T00:17:34.467Z
• Repository: https://github.com/m190/usefulapi-mcp
• Website: https://usefulapi.io/spoke-dispatch/

Badge for your README

Shows this live status and links here; updates hourly.

[![lookupd status](https://lookupd.com/badge/io.usefulapi/spoke-dispatch.svg)](https://lookupd.com/servers/io.usefulapi/spoke-dispatch)

• 62033 servers
• Last crawl: 2026-11-11T15:38:39.561Z
• API base: https://api.lookupd.com
• MCP URL: https://api.lookupd.com/mcp