← ClaudeAtlas

acronis-api-patternslisted

Acronis Cyber Protect Cloud MCP fundamentals through Conduit: the three `X-Acronis-*` headers (data center URL, API client ID and secret), the partner → customer → unit tenant hierarchy and what an API client can see, the 37-tool surface (34 reads plus 3 writes that are off by default, one of them admin-only in Conduit), the `path` / `query` / `body` argument shape, the different pagination styles per API family, filter operator syntax, nanosecond alert timestamps, response size caps, and the error shape.
WYRE-AI/msp-claude-plugins · ★ 55 · API & Backend · score 84
Install: claude install-skill WYRE-AI/msp-claude-plugins
# Acronis MCP Tools & API Patterns ## Overview Acronis Cyber Protect Cloud is a multi-tenant backup, disaster recovery and endpoint protection platform. MSPs run it as a partner tenant with one customer tenant per client. The Conduit connector wraps Acronis's own MCP server and exposes a curated set of 37 tools. Tool names are `acronis_` plus the Acronis operation name, such as `acronis_fetch_all_alerts`. ## Connection & Authentication Conduit sends three headers to the Acronis connector: | Header | Conduit field | Value | |--------|---------------|-------| | `X-Acronis-Base-Url` | Data center URL | The data center Acronis shows when you create the API client, such as `https://us5-cloud.acronis.com`. Origin only: nothing after `.com`. | | `X-Acronis-Client-Id` | Client ID | The API client's ID | | `X-Acronis-Client-Secret` | Client Secret | The API client's secret | You enter these fields once in the Conduit web UI (`/connect/acronis`). Conduit stores them and injects the headers on every request; nothing is set on the client, and Conduit drops any `X-Acronis-*` header a client sends. How to get them: 1. In the Acronis management portal, open **Settings → API clients**. 2. Create an API client. Copy the Client ID, the Secret and the data center URL that Acronis shows. The secret is only shown once. 3. Don't use your Acronis portal email and password. Conduit needs an API client, which signs in with the OAuth `client_credentials` flow. When you connect, Conduit