
Axcient x360Recover
io.github.WYRE-AIPublished by GitHub account WYRE-AIv1.0.5Updated Nov 21, 2026
MCP server for Axcient x360Recover — BCDR clients, devices, jobs, vaults, and appliances.
Overview
MCP server for Axcient x360Recover that lets an assistant browse BCDR clients, devices, backup jobs, vaults and appliances.
- What you can do
- Verify the API key and read the organization it belongs to
- List and get clients (customer/site records) and devices, including per-client device listings
- Inspect AutoVerify results and device restore points
- List backup jobs and fetch job details and job history per device
- List vaults and appliances, and read or set a vault connectivity threshold
- Mint a D2C agent enrollment token
- When to use it
- Useful when you want an assistant to answer questions about a managed backup and disaster-recovery estate: which clients and devices exist, whether jobs and AutoVerify checks are healthy, and what restore points are available, without opening the x360Portal by hand.
- Requirements
- Runs as a local process over stdio (Node.js project built from source, or the published container image). Needs an Axcient x360Portal API key in AXCIENT_API_KEY for stdio or AUTH_MODE=env. HTTP hosting additionally requires CONDUIT_S2S_SECRET and, in gateway mode, an X-Axcient-Api-Key header per request. Network access to the Axcient API.
Installation
In SourceWeft
- Open Axcient x360Recover in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
axcient-mcp
MCP server for Axcient x360Recover — BCDR
clients, devices, backup jobs, vaults, and appliances. Built on
@wyre-technology/node-axcient and the
MCP v2 SDK, serving both the 2025-era initialize handshake and the 2026-07-28 stateless
envelope from a single dual-era HTTP entrypoint.
Credentials
Generate an API key in the x360Portal: Settings → API Keys (see Axcient's key management guide).
Copy .env.example. Leave CONDUIT_S2S_SECRET empty in that file.
- Local / stdio (Claude Desktop, CLI): set
AXCIENT_API_KEY. The stdio transport does not useCONDUIT_S2S_SECRET. - Hosted / gateway: the WYRE MCP Gateway injects
X-Axcient-Api-Keyper request (AUTH_MODE=gateway). The gateway compose service does not setAXCIENT_API_KEYand does not useenv_file.
/health and /healthz stay unauthenticated and do not read credentials.
X-Gateway-S2S signing
With MCP_TRANSPORT=http and CONDUIT_S2S_SECRET set, every /mcp request must include X-Gateway-S2S:
v1 is HMAC-SHA256 over the ASCII message t=<unix seconds>, keyed with CONDUIT_S2S_SECRET, hex-encoded. The timestamp must be within 300 seconds of the server clock. A missing or invalid header returns 401. The secret is never logged.
In AUTH_MODE=gateway, /mcp also requires X-Axcient-Api-Key. A request missing that header returns 401 and does not fall back to AXCIENT_API_KEY.
Run locally (stdio)
Run as HTTP (gateway / hosted)
Local HTTP without a secret is development-only. It binds 127.0.0.1 and logs a warning:
Docker
The image listens on 0.0.0.0 inside the container (MCP_HTTP_HOST) and defaults to AUTH_MODE=gateway. Publish the port on loopback and pass the S2S secret. In gateway mode, the Axcient API key arrives on each request as X-Axcient-Api-Key; it is not read from the environment.
Compose refuses to start when CONDUIT_S2S_SECRET is unset, runs AUTH_MODE=gateway, publishes 127.0.0.1:8080:8080, and does not inject AXCIENT_API_KEY:
Single-tenant HTTP (AUTH_MODE=env) still requires the S2S secret, then uses AXCIENT_API_KEY:
Tools
20 tools, flat surface (no router — well under the fleet's ~25-tool threshold).
No destructive tools exist in this surface — the x360Recover public API (v0.3.1) has no
delete/disable operations, so no confirmation/elicitation flow is wired up. See
node-axcient's README for known API quirks (error-shape inconsistencies, list-endpoint
schema documentation bugs) this server's error messages surface verbatim from the SDK.
License
Apache-2.0
Source: README.md at commit 48bdd1d
Tools
0Version history
3- v1.0.5LatestNov 21, 2026
- v1.0.4Oct 14, 2026
- v1.0.3Sep 16, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.