Circuit (Spoke Dispatch) logoMCP server · Shipping and delivery

Circuit (Spoke Dispatch) MCP server

Circuit (Spoke Dispatch) in any MCP client, through Memtro: Circuit (Spoke Dispatch) does not publish this server. Memtro's Circuit (Spoke Dispatch) connector reads Circuit (Spoke Dispatch) through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.

What the model can do

Spoke Dispatch (Circuit for Teams) delivery routing: plans by date with their drivers, routes and optimization state, each plan's or route's stops with order references, packages, time windows, ETA and delivery outcome (recipients, addresses and proof of delivery are not read), routes with progress, unassigned stops, depots, drivers by id, and optimization results; when you ask, can create, rename, re-date or delete a plan, add, change or delete stops, optimize a plan, distribute it to its drivers, and add or delete unassigned stops.

Reads

  • circuit_plansSpoke Dispatch plans (a day's deliveries), newest dates as Spoke returns them: title, start date, depot, drivers and routes by id…
  • circuit_plan_stopsThe stops of one Spoke Dispatch plan: activity, position and route, packages and products, seller order and invoice numbers, notes, time windows…
  • circuit_routesSpoke Dispatch routes (one driver's run): title, stop count, driver and plan ids, and whether distributed, started and completed…
  • circuit_route_stopsThe stops of one Spoke Dispatch route in order, with the same fields and outcome counts as circuit_plan_stops.
  • circuit_unassigned_stopsSpoke Dispatch unassigned stops (orders not yet on a plan): order references, packages, notes and time windows…
  • circuit_depotsSpoke Dispatch depots: id and name.
  • circuit_driversSpoke Dispatch drivers by id, with whether active and their depots; names, emails and phones are not returned.
  • circuit_operationAn optimization started by circuit_optimize_plan: whether it is done or cancelled, when it ran…

Acts, when you ask

These change something in Circuit (Spoke Dispatch). The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

  • circuit_create_planCreates a Spoke Dispatch plan for a day, optionally with its depot (default the team's main depot) and drivers.
  • circuit_update_planChanges a Spoke Dispatch plan's title, date, depot or drivers.
  • circuit_delete_planPermanently deletes a Spoke Dispatch plan and all its routes and stops, even one already sent to drivers.
  • circuit_add_stopAdds a stop (a delivery or pickup) at an address to a Spoke Dispatch plan that has not started, with the recipient's details, packages…
  • circuit_update_stopChanges a stop on a Spoke Dispatch plan that has not started: recipient details, activity, packages, notes, order references or arrival window…
  • circuit_delete_stopPermanently deletes a stop and its data from a Spoke Dispatch plan that has not started.
  • circuit_optimize_planStarts optimizing a Spoke Dispatch plan: Spoke assigns its stops to the plan's drivers and orders each route.
  • circuit_distribute_planDistributes a Spoke Dispatch plan: each driver is sent their route in the Spoke driver app and the stops are allocated…
  • circuit_add_unassigned_stopAdds an unassigned stop (an order waiting to be planned) at an address, at a depot (default the main depot), with the recipient's details, packages…
  • circuit_delete_unassigned_stopPermanently deletes an unassigned stop.

Connect it

First connect Circuit (Spoke Dispatch) on Dashboard → Connections, then add Memtro to your client once. The Circuit (Spoke Dispatch) tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

Claude Code

The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

Cursor

Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Claude Desktop

Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…

OpenCode

A remote server in opencode.json.

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Pi

One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.

Any other client

Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Circuit (Spoke Dispatch) connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

  • › Which stops on today's plan failed?
  • › Has Tuesday's plan been sent to the drivers?
  • › Which unassigned stops are waiting at the main depot?
  • › Which routes have started but not finished today?
  • › Optimize tomorrow's plan.

Questions

Is this an official Circuit (Spoke Dispatch) MCP server?
No. It is Memtro's MCP server with Memtro's Circuit (Spoke Dispatch) connector behind it: the connector reads Circuit (Spoke Dispatch) through its API with the credentials you connect on Dashboard → Connections, and Circuit (Spoke Dispatch) publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
What does it cost?
Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
Can it change anything in Circuit (Spoke Dispatch)?
Only when you ask, and only what it has been granted: create a plan; update a plan's title, date, depot or drivers; delete a plan and its routes; add a stop to a plan; update a stop; delete a stop from a plan; optimize a plan; distribute a plan's routes to its drivers; add an unassigned stop; delete an unassigned stop. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
Which clients work?
Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Shipping and delivery

Where agents remember your company

Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.

7-day free trial · card on file, nothing charged until it ends · cancel any time