axcient-api-patternslisted

# Axcient MCP Tools & API Patterns ## Overview The Axcient MCP server wraps the x360Recover Public API (BCDR — backup continuity and disaster recovery for servers and workstations behind Axcient appliances, plus direct-to-cloud agents). It registers 20 tools covering the caller's organization, clients, devices, backup jobs, vaults, and appliances. Eighteen are read-only `GET` calls; two mutate state — `axcient_set_vault_threshold` and `axcient_get_d2c_agent_token`. ## Anti-triggers - **Datto BCDR (SIRIS/ALTO) devices** — different vendor, different API. Use `datto-bcdr`. - **Datto SaaS Protection (M365/Google Workspace backup)** — use `datto-saas-protection`. - **Unitrends appliances** — use `unitrends`. - **Billing/usage reconciliation across the whole x360 suite** — Axcient's separate Billing API is not wrapped by this server; nothing here returns invoice line items. ## Connection & Authentication ### API Key Authentication x360Recover authenticates with a single HTTP header: | Header | Value | |--------|-------| | `x-api-key` | Your Axcient API key | Generate credentials at: **partner.axcient.com > Settings > API Keys** (any administrator can create one; all administrators can view and delete keys created by others in the same organization). **Environment Variables (self-hosted / stdio mode):** ```bash export AXCIENT_API_KEY="your-api-key" ``` Through the WYRE Conduit gateway you set nothing — Conduit holds the key and injects it per request as `X-Axcie