Live vehicle health
Check battery, GPS and RTK fix quality, vibration, unhealthy sensors, armed state, flight mode, and firmware while the aircraft is online.
Connect Claude, ChatGPT, Cursor, and other MCP clients to your SkyRelay account. Query live telemetry, analyze flight history, and inspect flight-controller parameters using natural language.
SC0042 is online, with its flight controller connected and currently disarmed.
No issues appear in these checks. Use your normal preflight procedure before flying.
SkyRelay gives your agent structured access to the data it needs—without custom integration code or manual dashboard checks.
Check battery, GPS and RTK fix quality, vibration, unhealthy sensors, armed state, flight mode, and firmware while the aircraft is online.
Summarize past flights, review tracks and mode changes, and inspect battery and GPS trends—even when the drone is switched off.
Read live parameters or automatic backups saved at flight start. Compare settings between flights to investigate behavior changes.
Start with a device serial or name. Your agent can choose the appropriate tools and turn the results into an answer.
Use the remote MCP URL below. Your client will open SkyRelay’s sign-in and consent flow—no access token to copy.
https://api.skyrelay.us/mcp
Streamable HTTP transport · OAuth 2.1 · drone:read scope
Add the server, then run /mcp to sign in:
claude mcp add --transport http skyrelay https://api.skyrelay.us/mcp
Add this entry under mcpServers in mcp.json:
"skyrelay": {
"url": "https://api.skyrelay.us/mcp"
}
Add the same skyrelay entry shown for Cursor to ~/.kimi-code/mcp.json for every project, or .mcp.json for one project. Start a new session, then approve sign-in when prompted or run /mcp-config login skyrelay.
These are the exact tools available to your agent. Device arguments accept the serial shown in SkyRelay, such as SC0042, or the device name.
| Tool | What it returns |
|---|---|
| list_devices() | Your Conduits with serial, name, service tier, online state, last seen, and whether a flight controller is connected. |
| Tool and arguments | What it returns |
|---|---|
| get_vehicle_status(device) | Vehicle type, autopilot, firmware, armed state, flight mode, system status, unhealthy sensors, and battery summary. |
| get_battery(device) | Pack and available per-cell voltages, current, consumed mAh, remaining percentage, temperature, charge state, and estimated time left. |
| get_gps(device) | Fix type including RTK float/fixed, satellites, HDOP/VDOP, accuracy, position, and altitude for the first and optional second GPS. |
| get_vibration(device) | Vibration per axis in m/s², an ok / high / severe assessment, and accelerometer clipping counts. |
| get_param(device, name) | The current value of one flight-controller parameter, such as BATT_LOW_VOLT. |
| list_params(device, prefix?) | All live parameters, optionally filtered by a prefix such as BATT_. A full download typically takes 10–30 seconds over cellular. |
| Tool and arguments | What it returns |
|---|---|
| list_flights(device, since?, limit?) | Recorded flights, newest first: start/end, duration, distance, maximum altitude, takeoff/landing points, and parameter-backup availability. since is an ISO date or time; limit defaults to 20, maximum 50. |
| get_flight(flight_id) | One flight’s summary plus battery and GPS statistics, mode changes, and up to 100 downsampled track points with altitude, speed, and battery. |
| get_param_backup(device, flight_id?, prefix?) | Parameters automatically saved at flight start—the latest backup or one for a specific flight, with optional prefix filtering. |
Your agent can inspect your data, not operate your aircraft.
drone:read scope after your approval.Common responses and what to check next.
Check Conduit power and cellular connectivity. Recorded-data tools still work while the aircraft is off.
Confirm the flight controller is powered, connected to the Conduit, and configured for MAVLink.
Track devices are visible in list_devices, but their live and recorded per-device data requires Link.
Check that the flight has finished recording. Not every flight controller reports every battery, GPS, or sensor field.
Connect your MCP client and get operational answers without clicking through dashboards.
Connect your AI agent →