Fleetio MCP by usefulapi

Was du damit machen kannst

Für diesen Server haben wir noch keine Zusammenfassung in einfacher Sprache geschrieben. Unten stehen die Fakten, die wir aus der Registry gelesen haben.

• Verbindung: Läuft in der Cloud
• Transport: Streamable HTTP
• Kategorie: Onlineshops & Zahlungen

Installation

Wähle die KI-App, die du nutzt, und kopiere die Einstellungen.

Du brauchst

• Läuft in der CloudNichts zu installieren; die Verbindung läuft übers Internet

Welche App nutzt du?

https://fleetio.usefulapi.io/mcp

claude mcp add --transport http fleetio https://fleetio.usefulapi.io/mcp

{
  "mcpServers": {
    "fleetio": {
      "url": "https://fleetio.usefulapi.io/mcp"
    }
  }
}

{
  "servers": {
    "fleetio": {
      "type": "http",
      "url": "https://fleetio.usefulapi.io/mcp"
    }
  }
}

https://fleetio.usefulapi.io/mcp

Deine Auswahl bleibt in einem Cookie auf diesem Gerät; kein Konto nötig.

Diese Einstellungen werden aus dem Registry-Eintrag des Entwicklers erzeugt. Wenn in der README etwas anderes steht, folge der README.

Was er kann

Tool-Namen und -Beschreibungen genau so, wie der Server sie am 6. Nov. 2026 gemeldet hat. Geschrieben hat sie der Entwickler, nicht wir; wir zeigen sie als reinen Text.

• fleetio_list_accounts

  The Fleetio account(s) this API key belongs to: id, name, address, plan, units and the key's user type. The Account-Token and permission flags are never returned. GET /accounts.

• fleetio_list_vehicles

  List vehicles (not archived) with status, type, group, meter readings, VIN and license plate. Filter by name, VIN, plate, group, status or type; ids for the filters come from the lookup tools (fleetio_list_vehicle_statuses, fleetio_list_vehicle_types, fleetio_list_groups). GET /v

• fleetio_list_vehicle_meter_entries

  List the odometer / engine-hour meter readings of ONE vehicle, newest first by default. GET /vehicles/{id}/meter_entries. Returns one page (keyset paging: pass next_cursor as start_cursor).

• fleetio_list_meter_entries

  List meter readings across the account. Filter by vehicle and by date. GET /meter_entries. Returns one page (keyset paging: pass next_cursor as start_cursor).

• fleetio_list_vehicle_assignments

  List which driver (contact) was assigned to which vehicle and when; filter by vehicle or contact. GET /vehicle_assignments. Returns one page (keyset paging: pass next_cursor as start_cursor).

• fleetio_list_equipment

  List equipment (non-vehicle assets such as trailers and tools). GET /equipment. Returns one page (keyset paging: pass next_cursor as start_cursor).

• fleetio_list_work_orders

  List work orders (shop jobs) with status, vehicle, vendor and technician. Filter by vehicle, vendor, technician, number or status name (for example Open). A finished work order produces a service entry. GET /work_orders. Returns one page (keyset paging: pass next_cursor as start_

• fleetio_list_service_entries

  List service entries (completed maintenance records) with vehicle, vendor, dates and notes. Filter by reference or completion date. GET /service_entries. Returns one page (keyset paging: pass next_cursor as start_cursor).

• fleetio_list_vehicle_service_entries

  List the service entries of ONE vehicle. GET /vehicles/{id}/service_entries. Returns one page (keyset paging: pass next_cursor as start_cursor).

• fleetio_list_service_reminders

  List preventive-maintenance service reminders with next-due dates and meter values. Filter by status (ok, due_soon, overdue, snoozed), vehicle or service task. GET /service_reminders. Returns one page (keyset paging: pass next_cursor as start_cursor).

• fleetio_list_issues

  List issues (defects and problems reported against vehicles and equipment) with state, priority, assignees and due date. Filter by state, vehicle, equipment or reporter. GET /issues. Returns one page (keyset paging: pass next_cursor as start_cursor).

• fleetio_list_faults

  List diagnostic trouble codes (faults) reported by telematics devices, with vehicle, code and last occurrence. GET /faults. Returns one page (keyset paging: pass next_cursor as start_cursor).

• fleetio_list_inspection_forms

  List the inspection form templates (for example a daily DVIR) defined in the account. GET /inspection_forms. Returns one page (keyset paging: pass next_cursor as start_cursor).

• fleetio_list_submitted_inspections

  List submitted inspections (filled-in forms) with the vehicle, the driver, the number of failed items and the submit time. GET /submitted_inspection_forms. Returns one page (keyset paging: pass next_cursor as start_cursor).

• fleetio_list_fuel_entries

  List fuel purchases/fill-ups with vehicle, volume, price, total cost and efficiency. Filter by vehicle, vendor or date. Fuel-card data is never returned. GET /fuel_entries. Returns one page (keyset paging: pass next_cursor as start_cursor).

• fleetio_list_parts

  List parts (inventory catalog) with part number, manufacturer number, category and unit cost. Filter by part number, manufacturer part number or UPC. GET /parts. Returns one page (keyset paging: pass next_cursor as start_cursor).

• fleetio_list_part_stock

  List on-hand inventory of parts per part location (quantity by location). Filter by part or part location. GET /part_location_details. Returns one page (keyset paging: pass next_cursor as start_cursor).

• fleetio_list_contacts

  List contacts (drivers, technicians, employees) with name, email, phones, job title and group. Birth dates and driver-licence data are never returned. Filter by email, last name or group. GET /contacts. Returns one page (keyset paging: pass next_cursor as start_cursor).

• fleetio_list_vendors

  List vendors (repair shops, fuel stations, parts suppliers) with address and contact details. GET /vendors. Returns one page (keyset paging: pass next_cursor as start_cursor).

• fleetio_list_vehicle_renewal_reminders

  List vehicle renewal reminders (registration, insurance, inspections due) with next-due dates. Filter by vehicle or status. GET /vehicle_renewal_reminders. Returns one page (keyset paging: pass next_cursor as start_cursor).

• fleetio_list_comments

  List comments left on records. Filter by the record: commentable_type (Issue, WorkOrder, ServiceEntry, Vehicle, ...) + commentable_id. GET /comments. Returns one page (keyset paging: pass next_cursor as start_cursor).

• fleetio_list_vehicle_statuses

  Lookup: the vehicle statuses (Active, In Shop, Out of Service, ...) and their ids for filtering vehicles. GET /vehicle_statuses. Returns one page (keyset paging: pass next_cursor as start_cursor).

• fleetio_list_vehicle_types

  Lookup: the vehicle types (Car, Truck, Van, ...) and their ids. GET /vehicle_types. Returns one page (keyset paging: pass next_cursor as start_cursor).

• fleetio_list_work_order_statuses

  Lookup: the work order statuses (Open, In Progress, Completed, ...). GET /work_order_statuses. Returns one page (keyset paging: pass next_cursor as start_cursor).

• fleetio_list_issue_priorities

  Lookup: the issue priorities and their ids (needed to create an issue with a priority). GET /issue_priorities. Returns one page (keyset paging: pass next_cursor as start_cursor).

• fleetio_list_groups

  Lookup: the groups (locations/departments) and their ids. GET /groups. Returns one page (keyset paging: pass next_cursor as start_cursor).

• fleetio_list_labels

  Lookup: the labels (tags) used on vehicles, issues, work orders and service entries. GET /labels. Returns one page (keyset paging: pass next_cursor as start_cursor).

• fleetio_list_service_tasks

  Lookup: the service tasks (Oil Change, Tire Rotation, ...) and their ids. GET /service_tasks. Returns one page (keyset paging: pass next_cursor as start_cursor).

• fleetio_list_places

  List places (geofences/locations) with address, coordinates and radius. GET /places. Returns one page (keyset paging: pass next_cursor as start_cursor).

• fleetio_get_vehicle

  One vehicle with full detail: status, type, group, meters, VIN, make/model/year, license plate, dates. GET /vehicles/{id}.

• fleetio_get_equipment

  One equipment record with full detail. GET /equipment/{id}.

• fleetio_get_work_order

  One work order with full detail (status, vendor, technician, dates, totals). GET /work_orders/{id}.

• fleetio_get_service_entry

  One service entry with full detail (vehicle, vendor, notes, meter readings, totals). GET /service_entries/{id}.

• fleetio_get_part

  One part with full detail (number, manufacturer, category, costs). GET /parts/{id}.

• fleetio_get_contact

  One contact (driver/technician/employee). Birth date and driver-licence data are never returned. GET /contacts/{id}.

• fleetio_get_vendor

  One vendor with full detail. GET /vendors/{id}.

• fleetio_get_submitted_inspection

  One submitted inspection with every item's result (pass/fail/remarks), the vehicle, driver and any resulting work order. GET /submitted_inspection_forms/{id}.

• fleetio_get_inspection_form

  One inspection form template with its items. GET /inspection_forms/{id}.

• fleetio_get_issue

  One issue with full detail (state, priority, asset, reporter, due date, resolution). Optionally include comments, labels, the asset, custom fields, documents or images. GET /issues/{id}.

• fleetio_list_work_order_line_items

  The line items (labor, parts, fees) of ONE work order. GET /work_orders/{id}/work_order_line_items.

• fleetio_list_service_entry_line_items

  The line items (tasks, parts, labor) of ONE service entry. GET /service_entries/{id}/service_entry_line_items.

• fleetio_create_issue

  WRITE: create a new issue (a reported defect) on a vehicle or equipment. Fleetio may notify the people who watch or are assigned to it. Needs the asset id (fleetio_list_vehicles) and a summary; the report time defaults to now. Does not close, resolve or delete anything. POST /iss

• fleetio_create_meter_entry

  WRITE: record an odometer / engine-hour meter reading for a vehicle (primary meter, or the secondary meter with secondary=true). Fleetio rejects a value that breaks the sequence (a reading must not be lower than an earlier one by date); it cannot be deleted from here. The date de

• fleetio_add_comment

  WRITE: add a comment to an issue, work order, service entry, service reminder, vehicle or part. Fleetio notifies the watchers of that record (and anyone @mentioned in the text). Comments added here cannot be edited or deleted by this server. POST /comments.

Basischecksi

Wir prüfen Informationen, die jeder sehen kann; den Code haben wir nicht gelesen. Checks, die nicht zutreffen, werden nicht mitgezählt. · Geprüft am 6. Nov. 2026

• ✓ Bestanden

  Entwickler passt zum Repo

  Der Registry-Name wurde über die Domain usefulapi.io bestätigt (die Registry prüft, wem die Domain gehört)

• … Noch nicht geprüft

  Wird noch gepflegt

  Dieses Repo haben wir noch nicht von GitHub gelesen

• … Noch nicht geprüft

  Hat eine Lizenz

  Dieses Repo haben wir noch nicht von GitHub gelesen

• ✓ Bestanden

  Endpunkt antwortet

  Antwort in 17 ms (HTTP 200)

• – Nicht zutreffend

  Anmeldung mit OAuth

  Keine Anmeldung nötig

• ✓ Bestanden

  Keine versteckten Anweisungen in Tool-Beschreibungen

  Wir haben 44 Tool-Beschreibungen gelesen und keine versteckten Anweisungen an die KI gefunden

Im Vergleich mit anderen in Onlineshops & Zahlungeni

• Mehr Sterne als 0 % der anderen 1741 Server in dieser Kategorie
• Neuer in der Registry veröffentlicht als 93 % der anderen 1741 Server in dieser Kategorie
• Basischecks gleich gut wie oder besser als bei 100 % der anderen 1741 Server in dieser Kategorie

Verglichen mit allen aktiven Servern dieser Kategorie in der Registry. Sterne zählen nur, wenn dem Herausgeber das Repo gehört.

Alternativen

Server derselben Kategorie von anderen Entwicklern, sortiert nach Sternen.

So liest du eine Karte:★ GitHub-SterneiDrei Säulen: Bewertungen · Checks · NutzungiAktualisiert = neueste Version in der Registry veröffentlichti

README vom Entwickler

{