MCP · the ADEV loop as agent tools

San FranciscoStreamable HTTP

Model Context Protocol is the standard that lets an AI assistant call external tools over a typed wire. The SF network exposes the ADEV loop as 8tools on its own server, so a fleet dispatcher — or the car itself — can pick a vehicle, find it a bay, estimate the charge and hold the bay, with no app and no account. The tools call the same service layer as REST, so an agent’s hold is indistinguishable from one the orchestrator placed itself.

Connect an agent

8 tools

This is a separate server from the India network’s at /api/mcp. Two networks, two connectors: an agent connected here only ever sees San Francisco, which is what stops it from answering a robotaxi dispatch with a Bengaluru tower. Add both if you want an assistant that can reason across the two.

Endpoint

https://os.autodockai.com/api/us/mcp

Claude Code (CLI)

claude mcp add --transport http autodock-us https://os.autodockai.com/api/us/mcp

.mcp.json or claude_desktop_config.json

{
  "mcpServers": {
    "autodock-us": {
      "type": "http",
      "url": "https://os.autodockai.com/api/us/mcp"
    }
  }
}

On claude.ai, add it under Settings, Connectors, Add custom connector. A hosted connector needs a public URL, so use https://os.autodockai.com/api/us/mcp rather than localhost.

Verify the server is live

Runs a real MCP handshake against the endpoint, the initialize then tools/list exchange every client does on connect, and lists exactly what the server advertises.

Discover

Read the live network: bays, sites, pricing, KPIs, and the fleet itself.

find_available_bays

Free bays near a point, by connector, minimum kW and operator.

get_site_status

One site: bay states, live draw against the grid limit, headroom.

get_pricing

Effective $/kWh now, fleet or retail, with the live TOU band.

get_fleet_stats

Fleet KPIs: on trip, charging, planning, avg SoC, kWh today.

list_fleet_vehicles

The robotaxi roster, so an agent can pick a vehicle to dispatch.

Decide

Reason before committing a vehicle: time, energy, cost.

estimate_charge_time

Taper-aware minutes, kWh and USD to a target SoC for one vehicle.

Dock

Act on the network: hold a bay for a named robotaxi, release it.

book_charging_slot

Hold a bay for a named vehicle; returns the 12-min hold window.

cancel_booking

Release a held bay back to Available.

Try it: the demo prompt

live

With Claude connected, ask one question and watch it run the loop across four tools:

Which Waymo robotaxi most needs charge? Find it a 350 kW bay near the Embarcadero, tell me how long to 80%, and hold the bay.

Claude runs Discover list_fleet_vehicles then find_available_bays, Decide estimate_charge_time, then Dock book_charging_slot, and the hold appears on the fleet map in real time. To make the agent pay for each of those calls over x402, see the x402 console.