Read driver scores, trips, driving events, vehicle locations and fault codes from your Azuga fleet account.
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.
Try asking Muse: "Show me which vehicles in my fleet have fault codes and how each driver scored this month."
Source: Found in the official MCP Registry (io.usefulapi/azuga) · First listed November 7, 2026
Each bar is one check, every 15 minutes. Green means it answered. Last checked 4 h ago.
What Muse can see: It does not ask you to sign in, so it cannot see your accounts. It only sees what Muse sends it from your request.
Before it acts: Read what Muse plans to do before you approve it, and remove the app from Muse when you stop using it.
musedirectory.ai is not part of Meta. More about how Muse handles your information
Not in Muse's Connectors list yet, but Muse can still use it. Copy the request below and paste it into Muse. 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.
https://azuga.usefulapi.io/mcpNot in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
Azuga is a remote MCP server, so any assistant that can add a custom connector by link can use it. Same link, same tools.
In ChatGPT, open Settings, then Connectors (called Apps & Connectors on some accounts).
Under Advanced settings, switch on Developer mode. That is what lets you add a connector by link.
Choose Create, give it a name, paste the link as the MCP server URL, and save. If it needs a sign-in, ChatGPT asks for it here.
Start a chat, open the tools menu, pick the connector, and ask. ChatGPT asks before it runs a tool the first time.
Custom connectors need a paid ChatGPT plan, and on Team, Enterprise and Edu accounts only an admin can add them. Our "Working" label means the server answered us; it cannot tell whether your plan lets you add it. All connectors that work in ChatGPT
In Claude, open Settings, then Connectors.
Choose Add custom connector, give it a name, and paste the link.
If it needs a sign-in, Claude sends you to it. Then turn the connector on in a chat from the tools menu and ask.
Custom connectors are available on paid Claude plans; on Team and Enterprise accounts an admin may need to add them. Our "Working" label means the server answered us; it cannot tell whether your plan lets you add it. All connectors that work in Claude
https://azuga.usefulapi.io/mcpResponse time at the last check: 120ms. Worked in 100% of checks over 30 days.
Screened, no issues found
Screening looks for known threats and hidden instructions at the time of the check, and runs again weekly and whenever the tool list changes. It cannot see the server's code, so only connect what you need and review what Muse asks to do. How screening works.
azuga_get_profileGet 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_scoresList 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_tripsList trips that started and ended between two times, with distance, duration and trip ids. Azuga: GET /trip/info.json.azuga_get_trip_eventsGet 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_eventsList 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_locationsList the live status and last known location of vehicles, optionally filtered by vehicle or group. Azuga: GET /live/location.json.azuga_get_vehicle_locationGet the last known location of one tracked user (username of the device holder). Azuga: GET /trackee/location/last.json?username=.azuga_list_vehiclesList vehicles with their names, ids, groups and device details. Filter by name, group or id. Azuga: GET /vehicle/view.json.azuga_list_driversList users of the account of one type (default driver), with names, usernames and ids. Azuga: GET /users/view.json?type=.azuga_list_groupsList vehicle and driver groups, with ids and names. Azuga: GET /groups/view.json.azuga_list_geofencesList geofences (virtual areas), with names and shapes. Filter by name or group. Azuga: GET /geofence/view.json.azuga_list_landmarksList landmarks (points of interest), with names, types and addresses. Filter by name, group or type. Azuga: GET /landmark/view.json.azuga_get_breadcrumbsGet the GPS trail of one vehicle between two times, one point per recording, paged. Azuga: GET /breadcrumb/location.json.azuga_list_pairing_historyList which driver was paired with which vehicle or device, between two times. Azuga: GET /users/pairinghistory.json.azuga_list_rewardsList driver rewards between two times, with status (pending, processed or all). Azuga: GET /rewards/history.json.azuga_get_vehicle_diagnosticsGet 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).https://azuga.usefulapi.io/mcpNot 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.
At the last check (November 8, 2026, 02:15 UTC) the endpoint was working, answering in 120ms. Over the last 7 days it answered 100% of health checks. It is checked every 15 minutes.
It was screened on November 7, 2026 with the result "screened, no issues found". Screening checks the domain against threat feeds and reads the tools for hidden instructions and requests for passwords or card numbers. It cannot see the server's code, so grant only the access you need.
It exposes 16 tools, including azuga_get_profile, azuga_list_driver_scores, azuga_list_trips, azuga_get_trip_events. For example, you could ask Muse: "Show me which vehicles in my fleet have fault codes and how each driver scored this month."
This listing was added from public sources (Found in the official MCP Registry (io.usefulapi/azuga)). If you build Azuga, claim it to correct the details and get your badge.
Paste this on your site or README. It always shows the latest check.
<a href="https://musedirectory.ai/connector/azuga"><img src="https://musedirectory.ai/badge/azuga.svg" alt="Azuga on musedirectory.ai" width="236" height="40"></a>