AI-Assisted Fleet Operations (MCP Server)
The MCP server is available by invitation while it is in early access. Contact us to request access for your organisation.
Admiral exposes an integrated Model Context Protocol (MCP) server interface, allowing engineering teams to connect autonomous AI coding agents and LLMs (such as Claude Code, Cursor, and ChatGPT) directly into their fleet management pipeline.
With Admiral's MCP server, AI assistants can query real-time device health, inspect live streaming logs, diagnose edge failures, and execute authorized operational remediation tasks safely.
Model Context Protocol (MCP) Integration Topology
Authenticated via Fine-Grained IAM Tokens with Audit-Logged Execution
Capabilities Provided by the MCP Server
- Fleet Health Inspection: Query real-time device health, CPU/memory gauges, thermals, battery states, and network latency across all enrolled machines.
- Log Retrieval & Diagnostic Analysis: Retrieve kernel, supervisor, and container logs, and the one-call device diagnosis, to find the root cause of crashes.
- Desired State as Documents: Read and patch device documents, preview what a device would receive, and adopt or discard settings changed on site.
- Controlled Canary Rollouts: Create configuration rollouts with a canary, in-flight limit, and failure budget; watch them converge; pause, resume, cancel, or roll back.
- Device Control & Remediation: Issue authorized reboots and workload restarts on devices experiencing anomalies.
- Security & IAM Scoping: All MCP actions authenticate against Admiral's fine-grained IAM policy engine, ensuring AI agents operate strictly within explicitly granted permission boundaries.
Tools accept a device by name, tag, notes, IP, or UUID and resolve it first; an ambiguous match returns candidates and changes nothing. Tools that change a device or a rollout are marked destructive so the client asks before running them; only call them on an explicit request.
Tool Reference
Find and inspect
| Tool | What it returns |
|---|---|
list_organisations, list_fleets, list_devices, search | Organisations, fleets (search, tag filter), devices (status, fleet, free-text filter), and organisation-wide search. |
find_device | Resolve a device from a natural query; returns one match or ranked candidates. |
get_device, get_device_specs, get_device_network | Device detail, hardware and OS specification, IP addresses and interfaces. |
get_device_workload, get_device_system_services | Workload state and running configuration; platform services and whether any are crash-looping. |
get_device_stats, get_device_metrics | Latest CPU, memory, disk, and health; historical metric series. |
get_device_logs, get_device_events | Historical logs (works for offline devices); lifecycle events. |
get_device_screenshot | Live capture of the device's display (online devices). |
State and diagnostics
| Tool | What it returns |
|---|---|
diagnose_device | The diagnosis: verdict, severity-ordered issues with evidence, last reboot. Stored data only; works offline. |
get_device_state | Conditions, observed generation, workload, boot, transport, time, storage, boot reasons, live operations, local override. live=true asks the device now. |
watch_device_state | Follows the device's state stream for up to 10 minutes and returns condition transitions and every progress operation seen. |
probe_device | Runs the live probe on the device (optionally only some sections). Support-scope values come back [redacted]. |
Documents
| Tool | What it does |
|---|---|
get_device_document | The device's document as JSON or YAML, with its resource version. |
patch_device_document | Apply a JSON merge patch (for example a fleet move or a workload override), optionally with if_match. Destructive. |
render_device_document | Dry-run render: what the device would receive and the diff against what it applied. |
adopt_local_override, discard_local_override | Adopt on-site settings into the document, or tell the device to drop them. Discard can take connectivity away from a device; destructive. |
Rollouts
| Tool | What it does |
|---|---|
create_rollout | Create a configuration rollout for a fleet, configuration, and version with an optional strategy (canary, max in flight, max unavailable, failure threshold, progress deadline). Destructive. |
get_rollout, list_rollout_devices | Status, paused reason, strategy, counts; per-device phase, progress, and stuck time. |
rollout_control | pause, resume, cancel, or rollback. Destructive. |
watch_rollout | Follow a rollout until it finishes or a timeout, returning status and per-device phase transitions. |
Actions
| Tool | What it does |
|---|---|
reboot_device | Reboot a device. Destructive. |
change_workload_status | Start, stop, restart, or recreate the workload. Destructive. |
Tools prefixed admin_ and list_fleet_protocols exist for the Admiral support team; see Admiral Support Team: Device Troubleshooting.