# Claude integration

> How the Maxmove connector in Claude connects to a Maxmove account over MCP and OAuth, what it can do per role, and how bookings and payment work.

The Maxmove connector for Claude lets a signed-in Maxmove user check serviceability, compare vehicle types, get binding quotes, book after explicit confirmation, and track orders in a Claude conversation.

For setup, see [Use Maxmove in Claude](https://maxmove.com/en/help/business-api/claude-maxmove-setup).

## How it connects

Claude connects to the [Maxmove MCP server](https://maxmove.com/en/developers/docs/ai/mcp-server) at `https://api.maxmove.com/mcp` over the Model Context Protocol. It does not use the public `/v1` API or API keys.

- **Sign-in.** The user opens **Customize → Connectors** in Claude, selects Maxmove, and signs in with their Maxmove account (OAuth 2.1 with PKCE). Claude identifies itself with an OAuth client metadata document on a `claude.ai` domain.
- **Permissions.** The connection starts with read access. The first booking, cancellation, or dispatch change asks the user to grant write access.
- **Workspace.** The connection is bound to the Maxmove workspace that was active when the user connected. To switch, the user changes the workspace in Maxmove and reconnects.
- **Disconnect.** Disconnecting Maxmove under **Customize → Connectors** revokes Claude's access.

## Data flow

**1. Quote**

The user describes the transport. Claude calls the quote tool with the addresses as the user gave them; Maxmove geocodes them and checks serviceability and the vehicle. Where Claude supports MCP Apps, the quote renders as a booking summary card.

**2. Confirm**

Claude books only after the user confirms the reviewed quote in the conversation or taps the button on the card. The booking redeems exactly that quote.

**3. Track**

The user can follow an order's status, driver, and arrival time, list their orders, cancel one, or open a support conversation.

Orders booked this way are normal Maxmove orders in the workspace, marked as booked through Claude. They don't send `/v1` webhook events.

## What it can do

The tools depend on the workspace type and the user's role: personal and business accounts can quote, book, track, and cancel; fleet control roles can inspect the order board and vehicle readiness and make confirmed dispatch changes; drivers can read their own routes, orders, and tours. See [Tools by role](https://maxmove.com/en/developers/docs/ai/mcp-server#content-tools-by-role).

## Payment

Bookings confirmed in Claude use monthly invoice or cash payment. For card payment, Claude 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.

## Requirements

- A Maxmove account with an active personal, business, fleet, or driver workspace and an eligible role.
- A Claude plan and region in which Anthropic offers connectors.
- Addresses inside the Maxmove [service area](https://maxmove.com/en/developers/docs/coverage).

---

Source: https://maxmove.com/en/developers/docs/integrations/claude