# Azuga Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## Azuga

Read driver scores, trips, driving events, vehicle locations and fault codes from your Azuga fleet account.

- Record: https://musedirectory.ai/connector/azuga
- Category: Productivity
- Developer: usefulapi (https://usefulapi.io/azuga/)
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 120ms, checked 2026-11-08T02:15:46Z
- Endpoint: https://azuga.usefulapi.io/mcp
- Auth: No account needed; Pricing: unknown
- Screening: Screened, no issues found (2026-11-07T22:06:35Z)
- Source: Found in the official MCP Registry (io.usefulapi/azuga) https://registry.modelcontextprotocol.io/v0/servers?search=io.usefulapi%2Fazuga

Connects to Azuga fleet telematics so Muse can pull driver safety scores, trip history, harsh driving events, live vehicle locations and diagnostic fault codes for a small business fleet.

Example request: "Show me which vehicles in my fleet have fault codes and how each driver scored this month."

How to connect: Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use Azuga to help me. It is a free service with an MCP server at https://azuga.usefulapi.io/mcp. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.

Tools:
- azuga_get_profile: Get the signed-in Azuga user's profile: user name, device, vehicle, fleet score, reward counts and privileges. Also the cheapest authenticated call. Azuga: GET /profile/info.json.
- azuga_list_driver_scores: List driver scores with rank, fleet score, and the speeding, braking, hard-acceleration and idling sub-scores. Per driver, not per group. Azuga: GET /score/list.json.
- azuga_list_trips: List trips that started and ended between two times, with distance, duration and trip ids. Azuga: GET /trip/info.json.
- azuga_get_trip_events: Get the driving events of one trip: hard braking, extreme braking, sudden acceleration, over-speeding and idling, with time, speed, location and fuel. Good first workflow for harsh-driving reviews. Azuga: GET /trip/eventdetail.json (reports host).
- azuga_list_events: List fleet events for vehicles or groups between two times, for example speeding, idling or device events, with sorting and paging. Azuga: POST /events.json (read only).
- azuga_list_live_locations: List the live status and last known location of vehicles, optionally filtered by vehicle or group. Azuga: GET /live/location.json.
- azuga_get_vehicle_location: Get the last known location of one tracked user (username of the device holder). Azuga: GET /trackee/location/last.json?username=.
- azuga_list_vehicles: List vehicles with their names, ids, groups and device details. Filter by name, group or id. Azuga: GET /vehicle/view.json.
- azuga_list_drivers: List users of the account of one type (default driver), with names, usernames and ids. Azuga: GET /users/view.json?type=.
- azuga_list_groups: List vehicle and driver groups, with ids and names. Azuga: GET /groups/view.json.
- azuga_list_geofences: List geofences (virtual areas), with names and shapes. Filter by name or group. Azuga: GET /geofence/view.json.
- azuga_list_landmarks: List landmarks (points of interest), with names, types and addresses. Filter by name, group or type. Azuga: GET /landmark/view.json.
- azuga_get_breadcrumbs: Get the GPS trail of one vehicle between two times, one point per recording, paged. Azuga: GET /breadcrumb/location.json.
- azuga_list_pairing_history: List which driver was paired with which vehicle or device, between two times. Azuga: GET /users/pairinghistory.json.
- azuga_list_rewards: List driver rewards between two times, with status (pending, processed or all). Azuga: GET /rewards/history.json.
- azuga_get_vehicle_diagnostics: Get OBD diagnostic trouble codes (DTCs) reported by vehicles in a period, with code, definition, vehicle, location and time. Several vehicles per call. Azuga: POST /diagnostics.json (read only).

Screening checks:
- MCP handshake: pass (Answered in 178ms)
- Domain against threat feeds (Cloudflare security DNS): pass (azuga.usefulapi.io, usefulapi.io not flagged)
- Published packages against the OSV malicious-package database: n/a (No npm or PyPI package published)
- Hidden instructions or invisible characters in tool text: n/a (Tools are behind sign-in)
- Inputs asking for passwords, card numbers or seed phrases: n/a (Tools are behind sign-in)
- Domain and redirects: pass (No redirects off the domain)
- AI review of purpose and tool behavior: pass (No concerns)