Fleet management with AI: your agent reads the fleet.
The VehDB MCP server turns your curated fleet list into a native tool for Claude, Cursor and any MCP client. The agent reads the list your team maintains — then researches every vehicle against the full catalog, in the same conversation.
OAuth2 for AI providers, Bearer tokens for everything else. Free tier included.
Which vans do we own, and what tires do they take?
You own 2 vans. OEM fitments:
- · 2022 Transit 250 → LT245/75R16
- · 2020 Sprinter 2500 → LT245/75R16
via my_lists + tire_sizes_for_vehicle
How it works
Three steps, no integration project
1 · Curate the fleet
Your team saves vehicles into lists in the dashboard — statuses (owned, wishlist, considering) and notes. This stays human: the list is your source of truth.
2 · Connect the MCP server
One URL and a token in your AI client's config. OAuth2 for AI providers, plain Bearer tokens otherwise. Two minutes, no SDK.
3 · Ask in plain language
The agent calls my_lists to read the fleet, then search_vehicles, get_vehicle and tire_sizes_for_vehicle to research each row — and answers in one message.
In practice
Ask things a spreadsheet can't answer
Every prompt below chains your list with the catalog — the agent does the lookups, you keep the answer.
“What’s on our fleet right now, grouped by status?”
my_lists
“Which wishlist trucks are AWD diesels under $0.09/mile in fuel?”
my_lists · search_vehicles
“Pull OEM tire sizes for every vehicle we own.”
my_lists · tire_sizes_for_vehicle
“Compare the EPA fuel cost of our three “considering” picks.”
my_lists · get_vehicle
No magic
What the agent can and can't do
Trust comes from boundaries. Here's exactly where they are.
| Capability | How | Status |
|---|---|---|
| Read the fleet list | my_lists (MCP) | Live |
| Research each vehicle — specs, EPA fuel economy | search_vehicles · get_vehicle | Live |
| OEM & alternate tire fitments per vehicle | tire_sizes_for_vehicle | Live |
| Recall exposure across the fleet | GET /v1/lists/recalls + daily email digest | Via API |
| Add or remove fleet vehicles | dashboard | Human, by design |
The agent never invents your fleet — it can only read the list your team actually curated.
Setup
One config block away
Any MCP client: paste the server, drop in a token from the dashboard, ask your first fleet question.
{ "mcpServers": { "vehdb": {
"url": "https://mcp.vehdb.com/mcp",
"headers": { "Authorization": "Bearer TOKEN" } } } }
Tools your agent gets: search_vehicles · get_vehicle · my_lists · tire_sizes_for_vehicle