# Maxmove MCP server

> How the Maxmove MCP server lets ChatGPT and Claude check serviceability, quote, book, and track transports for a signed-in Maxmove user.

Maxmove runs a [Model Context Protocol](https://modelcontextprotocol.io) server that AI assistants use to work with a Maxmove account: check whether an address pair is in the service area, compare vehicle types, get binding quotes, book after explicit confirmation, and track orders.

It powers the Maxmove app in ChatGPT and the Maxmove connector in Claude. Setting those up needs no code:

  - [ChatGPT](https://maxmove.com/en/developers/docs/integrations/chatgpt): How the Maxmove app in ChatGPT connects and what it can do.
  - [Claude](https://maxmove.com/en/developers/docs/integrations/claude): How the Maxmove connector in Claude connects and what it can do.

## MCP server or REST API?

| | MCP server | REST API |
| --- | --- | --- |
| Acts as | A signed-in Maxmove user, in one workspace | Your workspace, through an API key |
| Used by | ChatGPT and Claude | Your own software |
| Bookings | Only after the user confirms in the conversation | When your software sends the request |
| Authentication | OAuth sign-in with the Maxmove account | `x-api-key` header |

The MCP server does not use the public `/v1` API or API keys. To integrate Maxmove into your own software, use the [REST API](https://maxmove.com/en/developers/docs/quickstart).

## How it works

- **Endpoint.** `https://api.maxmove.com/mcp`, using the Streamable HTTP transport.
- **Sign-in.** OAuth 2.1 with PKCE. The server publishes its protected resource metadata at `https://api.maxmove.com/.well-known/oauth-protected-resource/mcp`; the authorization server is `https://api.maxmove.com/auth`.
- **Supported clients.** ChatGPT and Claude. They identify themselves with an OAuth client metadata document, which the server accepts only from ChatGPT and Claude domains.
- **Read first, write on demand.** A new connection gets read access (`mcp:access`). The first consequential action, such as creating a booking or cancelling an order, asks the user to grant write access (`mcp:write`).
- **One workspace.** The grant is bound to the workspace that is active when the user connects. A later workspace switch in Maxmove doesn't change it; to use another workspace, the user switches it in Maxmove and reconnects.
- **Tools follow the role.** The tool list is filtered by the workspace type and the user's role, so the assistant only sees tools the user may use.

## Tools by role

| Role | What the assistant can do |
| --- | --- |
| Personal and business accounts | Check serviceability, list vehicle types, quote, review and confirm bookings, list and track orders, cancel orders, create a tracking share link, and open a support conversation. |
| Fleet control roles (owner, admin, fleet manager, dispatcher) | Inspect the order board, order details, vehicles and vehicle readiness, and make confirmed changes: move or reschedule internal orders, claim or release marketplace orders, and cancel orders. |
| Drivers | Read their own route, orders, and tours, acknowledge released tour revisions, and go off duty. Navigation, proof of delivery, package scans, and going online stay in the Maxmove Driver app. |

Every tool that books, cancels, or changes dispatch state needs the user's explicit confirmation in the conversation before it runs. Quotes need no confirmation because they change nothing.

## Bookings and payment

Quotes are binding server quotes with an expiry time. A quote never creates an order, reserves capacity, or charges anyone. The assistant creates a booking only after it has shown the reviewed quote and the user has confirmed it. The booking uses exactly the reviewed quote; changed inputs or an expired quote are rejected.

Bookings confirmed in an assistant currently support monthly invoice or cash payment. For card payment, the assistant hands the reviewed route, time, vehicle, and extras to a booking page on maxmove.com, where the user pays by card. That page prices the route again.

## Cards in the conversation

Quotes, orders, and tracking render as interactive cards in hosts that support MCP Apps: a booking summary, an order list, and an order tracking card. Booking from the summary card still requires an explicit tap by the user.

---

Source: https://maxmove.com/en/developers/docs/ai/mcp-server