Dispatch launches hosted MCP server to quote, book and track deliveries from AI assistants
Dispatch, an AI-powered last-mile delivery platform, announced on October 20, 2026 a hosted Model Context Protocol server that lets teams manage deliveries from the AI assistants they already use, including Claude and ChatGPT. The server is available now in beta through Dispatch account teams.
The hosted model removes integration work: clients connect to a single Dispatch-hosted endpoint, sign in with their existing Dispatch credentials, and receive only the tools their permissions allow. There is no server to install or maintain, and Dispatch says new features reach connected assistants without redeployment.
Through the connection, users can get delivery estimates, create orders, retrieve order details and track deliveries in real time inside a conversation. Dispatch frames the use case around moments when delivery questions arise mid-workflow, such as a sales rep needing a quote before a customer call ends or a dispatcher checking an order's location.
'AI is great at answering questions, but in logistics, the real value comes when AI can also take action,' said Merlin Triplett, Chief Technology Officer at Dispatch. 'Our customers are now able to get answers and take action in seconds enabling them to spend more time on the work that matters.'
The MCP server is part of Dispatch's investment in permission-aware AI access across DispatchOne, its platform unifying owned fleets, carriers and systems. Because every connection runs through Dispatch's identity and access controls, customers keep the same governance over AI assistants as over employees, an important consideration for operations teams exposing live order data.
Buyers evaluating the beta should confirm which operations are write-capable for their role, since quote and booking actions create real orders and charges, and should test permission scoping with non-production accounts first. Dispatch has not published general-availability timing or pricing for MCP access, and the beta requires outreach to an account team rather than self-service signup.