Axcient x360Recover + AI in 60 seconds
Unofficial. Community-built Claude Code Skill and MCP server for the Axcient API. Not affiliated with, endorsed by, or sponsored by Axcient, Inc.
Awaiting live verification - passes every mechanical gate (build, command-surface, claims, install). Be the first to confirm it against your tenant: report it works.
MSPs run Axcient x360Recover across dozens of clients, but the portal answers one entity at a time and the public API famously won’t tell you which client a device belongs to. Ask your AI “whose backups failed last night,” “who’s breaching RPO,” or “what do I bill each client this month,” and get the fleet-wide answer in one table - computed offline from a local mirror that joins the device, job, restore-point, and client data the raw API leaves unconnected.
New to the term? An MCP server is the same thing ChatGPT calls an app or connector, Claude on the web calls a connector, and Claude Code calls a Skill. One thing, many names →
Install in 60s → View on GitHub →
Instead of clicking through Axcient x360Recover, just ask
Instead of Opening the x360Recover console and checking each appliance and device one at a time every morning to find the backups that failed or silently went stale overnight
just ask: “Whose backups failed or went stale last night?”
Your agent runs: axcient-cli health --agent
Instead of Screenshotting restore-point ages and AutoVerify boot results device by device to assemble backup-compliance evidence for a client’s QBR or an audit
just ask: “Give me backup-compliance evidence for this client - restore-point age, AutoVerify, and an RPO pass/fail”
Your agent runs: axcient-cli compliance --client 42 --hours 24 --csv
Instead of Visiting each client’s usage page at month-end and reconciling protected-system counts and storage against the invoice by hand
just ask: “What does each client consume this month for invoice reconciliation?”
Your agent runs: axcient-cli billing --csv
See it in 30 seconds
Demo data is simulated. Every command shown exists in the real CLI.
What it does
| Question your MSP keeps asking | Command your agent runs |
|---|---|
| Whose backups failed or went stale across every client last night? | axcient-cli health |
| Give me one row per client: devices total, failing, stale, RPO-breach, and AutoVerify-fail counts | axcient-cli client-rollup |
| Which devices are past their recovery-point objective, grouped by client? | axcient-cli rpo --hours 24 |
| Only show the devices actually breaching RPO at the cloud tier | axcient-cli rpo --hours 24 --target cloud |
| Produce backup-compliance evidence for one client (restore-point age + AutoVerify + RPO verdict) | axcient-cli compliance --client 42 --hours 24 --csv |
| Only the compliance rows that fail RPO or AutoVerify | axcient-cli compliance --failing-only |
| What does each client consume for invoice reconciliation this month? | axcient-cli billing --csv |
| Which devices does each appliance protect, and what state are those backups in? | axcient-cli appliance-map |
| Find everything matching a client or device name across synced data | axcient-cli search "Acme Corp" |
| Refresh the local mirror, then run the morning sweep | axcient-cli sync && axcient-cli health --agent |
Full command reference at github.com/servosity/msp-skills/blob/main/skills/axcient/guide.md.
What makes this one different
Most Axcient integrations and MCP wrappers proxy each question into a live API call - fine for one device, but a fleet-wide question becomes a token-burning loop of per-entity calls (appliance, then device, then each device’s jobs) because the API has no rollup endpoint and won’t join client to device for you. This skill syncs appliances, devices, jobs, restore points, AutoVerify results, and usage into a local SQLite mirror, then answers health, client-rollup, rpo, compliance, and billing as one offline join - instant, and the AI sees the answer table, not pages of nested JSON.
It complements the x360Portal rather than replacing it: the portal and the appliance/vault UI stay best for configuring protection and running actual restores, while this skill brings every client into one place for the cross-fleet questions - whose backups failed, who’s breaching RPO, where billing and protection diverge - that the per-entity API and one-client-at-a-time portal can’t answer in a single view.
Also from Servosity. Backup & DR is Servosity’s own field - the first-party Servosity connector brings this same fleet-wide, local-mirror approach (fleet attention, stale backups, restores, QBR reporting) to Servosity Backup and DR.
The pain this closes
- Axcient’s x360Recover Public API is built around per-entity endpoints - one call for appliances, another for a device, another for that device’s jobs - and it does not hand you the client-to-device mapping directly. So the question every MSP asks each morning, “whose backups failed,” has no single fleet-wide endpoint; you walk each appliance and device by hand or click through the portal.
- A backup that “succeeded” can still be out of compliance: the job ran, but the newest restore point is hours stale, or AutoVerify never booted the image. MSPs on r/msp keep describing the same trap - finding out a recovery point wasn’t there only when a restore is needed - because job-success and restore-point-age are different questions the console shows on different screens.
- Month-end reconciliation - matching protected-system counts and storage to what each client is invoiced - means opening each client’s usage view and stitching it into a spreadsheet, since the portal reports one client at a time and the API exposes usage per client, not as a fleet rollup.
Install
Works in any of these agents - pick yours:
| Agent | Quick install |
|---|---|
| Claude Desktop | Step-by-step → |
| ChatGPT (Plus/Pro+) | Step-by-step → |
| Claude Code | Step-by-step → |
| Codex CLI | Step-by-step → |
| Cursor, Windsurf, Cline, Continue, Zed, Copilot, Gemini, Hermes, OpenClaw | Which agent? → |
Quickest path for everyone else (terminal):
macOS / Linux:
bash <(curl -fsSL https://raw.githubusercontent.com/servosity/msp-skills/main/skills/axcient/install.sh)
Windows (PowerShell):
iwr -useb https://raw.githubusercontent.com/servosity/msp-skills/main/skills/axcient/install.ps1 | iex
After install, authenticate once with your Axcient x360Recover credentials, then verify with axcient-cli --version.
Safety model
| Tier | Examples | Recommended agent policy |
|---|---|---|
| Read | axcient-cli health; axcient-cli client-rollup; axcient-cli rpo –hours 24; axcient-cli compliance –client 42 –hours 24 –csv; axcient-cli billing; axcient-cli appliance-map; axcient-cli clients get; axcient-cli vault get; axcient-cli device get-by-org-id-org-level; axcient-cli organization; axcient-cli search “Acme Corp” | Allow |
| Write (routine) | axcient-cli vault threshold set-by-vault-id |
Preview with –dry-run, then a reviewed write |
| Destructive / config | axcient-cli client vault get-d2c-agent-token-by-client-and-ids |
Human-in-the-loop only |
The skill drives the axcient-cli and axcient-mcp binaries, authenticating with an organization-scoped API key (AXCIENT_API_KEY) read from the environment and sent as the X-Api-Key header - never written to disk, never logged, never sent anywhere except the Axcient API. The surface is overwhelmingly read-only: every fleet view (health, client-rollup, rpo, compliance, billing, appliance-map) and every resource read cannot change anything. Only three commands write - vault threshold set-by-vault-id and the bulk import
Frequently asked questions
Does this work with ChatGPT?
Yes, on paid ChatGPT plans. ChatGPT connects to remote MCP servers over HTTPS, so you expose the local Axcient MCP server via a secure bridge. Step-by-step in the install guide.
Do I need to know how to code?
No. Paste one sentence into Claude Code or Codex and your agent does the install, or run a one-line installer. You enter your credentials once.
Is my Axcient data safe?
Your data stays on your machine. The CLI, MCP server, and the local mirror are all local. The AI sees query results, not raw bulk data, and credentials are never bundled or transmitted by MSP Skills.
What does it cost?
Free. Apache-2.0 licensed. You pay only for whichever AI agent you already use.
Will this hit my Axcient API rate limits?
The local mirror exists so reads stop hitting the API. After the first sync, the fleet views (health, client-rollup, rpo, compliance, billing, appliance-map) run against local SQLite with zero API calls. Live calls respect a –rate-limit throttle, and sync is incremental - it only fetches what changed since the last checkpoint.
What kind of Axcient credential do I need?
An organization-scoped API key created in the x360Portal (Settings > API Keys, admin role required). The CLI sends it as the X-Api-Key header and can only see what that key is scoped to. Set it as AXCIENT_API_KEY; nothing is written to disk.
Can I try it without a real tenant?
Yes. Axcient hosts a public mock server - set AXCIENT_BASE_URL=https://ax-pub-recover.wiremockapi.cloud/x360recover with any non-empty AXCIENT_API_KEY and the whole CLI runs against fixtures, no real credentials needed.
Does this cover x360Sync or x360Cloud?
No. This skill is the x360Recover (BCDR) public API only - vaults, appliances, devices, jobs, restore points, AutoVerify, and usage. x360Sync and x360Cloud are separate products with separate APIs.
Status
Beta. Validated against the Axcient x360Recover API surface and being validated with MSPs running it live against their own production tenants in our weekly Build Sessions.
Standards. Conforms to the open Agent Skills spec (Anthropic, Dec 2025; 40+ agents). MCP-compatible - works with any MCP-capable agent including Hermes. OpenClaw-ready (frontmatter pre-wired, awaiting OpenClaw launch).
Maintained by Servosity for the MSP community. Apache-2.0 licensed. Built with CLI Printing Press.