← chauffeurvault.com
AI Assistant Connector
Connect Claude, ChatGPT or Claude Code to your dispatch account and run your day in plain language.
For dispatchers and company owners · Documentation · Support
What it is
The connector lets an AI assistant you already use talk to your Chauffeur Vault account. You ask in your own words and the assistant looks things up or makes changes through the same rules the dashboard follows.
- "What have I got on Thursday, and what is still uncovered?"
- "Who is free for a Jet Class to Gatwick at six?"
- "Quote the Savoy to Heathrow for four people with six bags."
- "Book Mr Patel's usual airport run for Monday 05:30 and assign Daniel."
It acts as you, for your company only. It cannot see another company's work, and an assistant connected by one dispatcher can never act as another.
Before you start
- You need a dispatcher or company owner login.
- A company owner must have AI assistants switched on for the company, under Settings → Integrations → AI assistants.
- You need an assistant that supports remote connectors: Claude (web, desktop, mobile, Team or Enterprise), Claude Code, or ChatGPT with developer mode or a published app.
Connect
Open Settings → Integrations → AI assistants in your dashboard and copy your connector URL. Then:
Claude
- Go to Customize → Connectors → Add custom connector.
- Paste the URL and continue.
- Claude sends you to Chauffeur Vault to sign in and approve. On Team or Enterprise plans, an organization owner adds the connector under Organization settings and members then connect their own accounts.
ChatGPT
- Settings → Apps & Connectors → Advanced → turn on Developer mode.
- Choose Create, paste the URL and save.
- Sign in to Chauffeur Vault when asked.
Claude Code
In a terminal:
claude mcp add --transport http chauffeur-vault <your URL>
Then claude mcp login chauffeur-vault if it asks you to authenticate again later.
You sign in with your normal Chauffeur Vault login, on our own page. You never give the assistant a password or an API key, and there are no API keys to create.
Approve the connection
Signing in is deliberately not enough to let an assistant loose on your customer list. Two more steps follow.
- Approve it. The new connection appears in Settings → Integrations → AI assistants marked as waiting. Until you approve it there, it can read nothing and change nothing. You also get an email the moment anything connects as you.
- Allow changes, if you want them. Every connection starts read-only. It can look things up and that is all, until you switch on Allow changes.
Why: an AI assistant signing in on your behalf is exactly the shape of a phishing attack, so one click is never enough here. If you ever get an email saying something connected to your account and it was not you, do nothing. It stays locked out.
| Tool | What it does | Access |
|---|
| Who am I | Which account and company the assistant is acting for | Read |
| List jobs | Jobs by date, status or driver | Read |
| Get job | One job in full, including the customer's contact details for that job | Read |
| Today's schedule | The day's runs and what is still uncovered | Read |
| List drivers | Drivers, their vehicles and availability | Read |
| Get driver | One driver in full | Read |
| List customers | Customers by name | Read |
| Get customer | One customer and their history | Read |
| Get quote | A price from your rate card, including the right number of vehicles for a group | Read |
| Get pricing | Your rate card | Read |
| Agent status | Whether your phone and WhatsApp booking agents are live | Read |
| List conversations | Recent agent calls and chats | Read |
| Get conversation | One transcript | Read |
| Create job | A new booking; the customer notice and payment link go out automatically | Change |
| Multi-trip booking | Several trips for one customer on one invoice | Change |
| Update job | Time, addresses, vehicle, price or notes | Change |
| Publish to marketplace | Offer a job to the driver marketplace | Change |
| Assign driver | Put a driver on a job | Change |
| Unassign driver | Take a driver off a job | Change |
| Cancel job | Cancel a booking; refunds follow your booking terms | Change |
Change tools work only after you have allowed changes for that connection. Every tool is labelled so that the assistant knows which ones only read and which ones alter or cancel something, and assistants ask you before using the ones that cancel.
What it deliberately cannot do
- Take payments. There is no tool for it. Payment links are sent by the platform and an assistant cannot ask for card details or promise to take money.
- Change a job's status. Drivers do that from their app.
- Touch your settings, pricing, drivers' accounts, or anything belonging to another company.
- See a customer's email, phone or notes while browsing. Lists carry the name and the job. Contact details come back only when it opens a specific booking for you.
- Call tools faster than a person reasonably would. Calls are rate limited per user.
Data and privacy
- What the assistant sees is exactly what the tool returns for your question, nothing more. We do not send your database, your conversations with the assistant, or anything the assistant did not ask for.
- Where it goes. The tool result is delivered to the assistant's provider (Anthropic for Claude, OpenAI for ChatGPT) and handled under that provider's terms and privacy policy, as with anything else you type into that assistant.
- What we keep. Which assistant connected, when, from which client, each tool it called with the outcome, and your approval and disconnection events. This is your audit trail and is shown in Settings → Integrations → AI assistants.
- Sign-in tokens are issued by our own sign-in service, expire, and are revoked the moment you disconnect.
Our privacy policy covers the platform as a whole, including the connector.
Staying in control
Everything an assistant does is recorded: which assistant, which tool, what came of it. Disconnect takes effect on its very next action, not whenever a token happens to expire. Company owners can see and disconnect every assistant connected to their company, and can switch assistants off for the whole company in one move.
Troubleshooting
- "Waiting for approval" on every tool. Approve the connection in Settings → Integrations → AI assistants.
- It reads but will not change anything. Turn on Allow changes for that connection.
- "Assistants are off for this company." A company owner needs to switch them on in Settings → Integrations → AI assistants.
- The assistant asks you to sign in again. Your session expired or you disconnected. Sign in again and the same approval applies.
- Claude Code says the connector is unauthenticated. Run
claude mcp login chauffeur-vault.
- Anything else. Email team@chauffeurvault.com with the assistant you use and the time it happened.
Technical notes
- The connector is a remote Model Context Protocol (MCP) server over Streamable HTTP, served from our API domain.
- Authentication is OAuth 2.0 with PKCE. Clients register dynamically. Static API keys are not issued or accepted.
- Every tool carries a title and read-only or destructive annotations.
- Tool results are JSON text. Lists are capped and never include customer contact details.
Documentation · Support · Terms · Privacy · chauffeurvault.com