hdls Fleet
hdls Fleet is a headless, MCP-native fleet & maintenance backend. It manages vehicles, maintenance, and inspections, operated entirely through named tools your AI assistant calls. It stands in for tools like Fleetio, Samsara — same job, no UI to run.
💬 Just ask
"Add a new vehicle to the fleet, then show me all my vehicles."
You don't call these tools yourself — just tell your assistant in plain English. Everything below is the reference for when you (or your assistant) want the exact details.
How Fleet is organized
The headline entity is the vehicle — start there, then attach the rest to it. Records connect by reference: a work_order links to a vehicle; an inspection links to a vehicle. The vehicle_log table is an append-only timeline — every change and note lands there and is never edited or deleted.
| Entity | Purpose | Relates to |
|---|---|---|
vehicle | A fleet vehicle (VIN, plate, odometer) with type, fuel, and service status. | — |
work_order | A maintenance or repair work order against a vehicle, with service type, cost, and status. | vehicle |
inspection | A driver/safety inspection (DVIR) of a vehicle with pass/fail result and defect notes. | vehicle |
vehicle_log | Append-only event timeline for a vehicle (fuel, odometer, assignment, incidents, expenses). | vehicle |
Common workflows
Each line is one real sequence of tool calls — your assistant chains them for you.
- Set up a vehicle end to end:
create_vehicle→log_maintenance→assign_driver
Tools
Call these at https://hdls.ai/api/mcp/fleet. Required fields you must supply; optional fields refine the call. You never pass tenant_id — it is stamped server-side.
Create
| Tool | What it does | Required | Optional |
|---|---|---|---|
create_vehicle | Create a new vehicle. | name | vin, license_plate, make, model, year, vehicle_type |
Update & advance
| Tool | What it does | Required | Optional |
|---|---|---|---|
log_maintenance | Log maintenance. | id | — |
assign_driver | Assign driver to a person or record. | id | — |
record_inspection | Record an inspection. | vehicle_id | inspection_type, result, inspector, odometer, notes, inspected_at |
Find & read
| Tool | What it does | Required | Optional |
|---|---|---|---|
search_vehicles | Search vehicles by free-text and/or column filters (tenant-scoped, paginated). | — | search, filters, limit, orderBy |
Field lists come from the product's live schema and are embedded in each tool's own description — read the tool description for the exact, current fields.
Field reference
Every field you can set on each record. Custom fields you add live alongside these in data.
vehicle
| Field | Type | Required | Notes |
|---|---|---|---|
name | text | Yes | Display name. |
vin | text | ||
license_plate | text | ||
make | text | ||
model | text | ||
year | number | ||
vehicle_type | text | ||
status | text | Lifecycle state. | |
fuel_type | text | ||
odometer | numeric(12,1) | ||
current_driver | text | ||
data | json | Free-form JSON — custom fields live here. |
work_order
| Field | Type | Required | Notes |
|---|---|---|---|
vehicle_id | id | Yes | Links to a vehicle. |
title | text | Yes | Display name. |
description | text | ||
service_type | text | ||
status | text | Lifecycle state. | |
priority | text | ||
odometer | numeric(12,1) | ||
cost | numeric(14,2) | ||
currency | text | ||
vendor | text | ||
scheduled_for | date | ||
completed_at | timestamp | ||
data | json | Free-form JSON — custom fields live here. |
inspection
| Field | Type | Required | Notes |
|---|---|---|---|
vehicle_id | id | Yes | Links to a vehicle. |
inspection_type | text | ||
result | text | ||
inspector | text | ||
odometer | numeric(12,1) | ||
notes | text | ||
inspected_at | timestamp | ||
data | json | Free-form JSON — custom fields live here. |
Tailor it with custom fields
Add fields without a schema change. add_custom_field defines one, list_custom_fields shows what's defined, and promote_custom_field (admin) shares a personal field with the whole workspace. The value lives in each row's data (JSON) and is set and read through the normal record tools. See Products, tools & custom fields for the full model.
Roles & safety
- Tenant isolation is automatic. Your credential is pinned to one workspace; you never pass
tenant_id, and you can only ever see your own data (enforced by Postgres row-level security). - Role-gated. Permissions run
reader < member < admin < owner. Installing a product and promoting a custom field workspace-wide need admin/owner. - History is append-only. The
vehicle_logtimeline is never edited or deleted — it's your audit trail.
Connect
On the concierge (https://hdls.ai/api/mcp), run install_product({ slug: "fleet" }) (admin/owner) to enable it for your workspace, then add https://hdls.ai/api/mcp/fleet as a connector in your assistant — see Connect your assistant.
A worked example
The literal call your assistant makes when you ask it to create the headline record:
Tool: create_vehicle
Arguments: {
"name": "Acme Corp"
}