Local MCP capabilities provider for Expo
Acronis Cyber Protect Cloud is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Acronis Cyber Protect Cloud MCP: alerts, policies, resources, agents, tenants and EDR incidents.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --env 'ACRONIS_BASE_URL=${ACRONIS_BASE_URL}' --env 'ACRONIS_CLIENT_ID=${ACRONIS_CLIENT_ID}' --env 'ACRONIS_CLIENT_SECRET=${ACRONIS_CLIENT_SECRET}' --transport stdio acronis-cyber-protect-cloud-mcp '--' docker run -i --rm --platform linux/amd64 -e ACRONIS_BASE_URL -e ACRONIS_CLIENT_ID -e ACRONIS_CLIENT_SECRET ghcr.io/wyre-ai/acronis-mcp:v1.0.1
# 2 — ask your agent for something these tools do
# acronis_fetch_tenant, acronis_fetch_tenants_batch, acronis_fetch_tenant_children and 34 more
It needs ACRONIS_BASE_URL, ACRONIS_CLIENT_ID, ACRONIS_CLIENT_SECRET: this reads them from your environment, so export them first.
Acronis Cyber Protect Cloud costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Acronis Cyber Protect Cloud as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. It has not been scanned here, so read the surface, and its source, before you approve it.
This is a public server: you run it yourself and this marketplace is not in the path. You need Docker installed and running. Only the required variables are passed into the container. To set an optional one (ACRONIS_ENABLE_WRITES, MCP_TRANSPORT, AUTH_MODE, LOG_LEVEL), add -e NAME before the image name and give it a value in the entry’s env: an unset -e would clear the default the image sets. Claude Code registers it in one command; --scope user makes it available in every project. Claude Code reads ACRONIS_BASE_URL (Acronis datacenter URL, https only, hostname must end with .acronis.com (e.g. https://us5-cloud.acronis.com)), ACRONIS_CLIENT_ID (Acronis API client ID (OAuth client_credentials)), ACRONIS_CLIENT_SECRET (Acronis API client secret) from your environment each time it starts the server, so the value stays out of its config: export them in your shell profile (macOS, Linux), or run setx ACRONIS_BASE_URL …, setx ACRONIS_CLIENT_ID …, setx ACRONIS_CLIENT_SECRET … and open a new terminal (Windows). The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user --env 'ACRONIS_BASE_URL=${ACRONIS_BASE_URL}' --env 'ACRONIS_CLIENT_ID=${ACRONIS_CLIENT_ID}' --env 'ACRONIS_CLIENT_SECRET=${ACRONIS_CLIENT_SECRET}' --transport stdio acronis-cyber-protect-cloud-mcp '--' docker run -i --rm --platform linux/amd64 -e ACRONIS_BASE_URL -e ACRONIS_CLIENT_ID -e ACRONIS_CLIENT_SECRET ghcr.io/wyre-ai/acronis-mcp:v1.0.1Reconnect, or start a new session, and the tools appear in the model’s tool list.
It reaches a system of yours, so it needs your own credential rather than the publisher’s: ACRONIS_BASE_URL — Acronis datacenter URL, https only, hostname must end with .acronis.com (e.g. https://us5-cloud.acronis.com); ACRONIS_CLIENT_ID — Acronis API client ID (OAuth client_credentials); ACRONIS_CLIENT_SECRET — Acronis API client secret. You set them in your own client’s config, on your machine — this marketplace never holds it.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
37 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Fetches a tenant by ID.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| path | object | yes | URI path parameters |
| query | object | no | Query parameters |
Gets several tenants at once, by up to 100 tenant IDs, by parent tenant, or as a tenant and everything under it.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | object | no | Query parameters |
Lists the IDs of the tenants directly under a tenant, such as a partner's customers.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| path | object | yes | URI path parameters |
| query | object | no | Query parameters |
Fetches a list of UUIDs of the tenant's users.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| path | object | yes | URI path parameters |
| query | object | no | Query parameters |
Gets details for several users at once.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | object | no | Query parameters |
Fetches a user by ID.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| path | object | yes | URI path parameters |
| query | object | no | Query parameters |
Fetches information about the currently authenticated user.
No parameter schema on file.
Searches for tenants and users.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | object | no | Query parameters |
Provides MFA status for tenant and progress of TOTP enablement by users.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| path | object | yes | URI path parameters |
Fetches a list of common usage metrics of the tenant.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| path | object | yes | URI path parameters |
| query | object | no | Query parameters |
Fetches all alerts by optional filtering parameters.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | object | no | Query parameters |
Fetches the information about the alert by ID.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| path | object | yes | URI path parameters |
| query | object | no | Query parameters |
Lists the alert categories that are turned on.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | object | no | Query parameters |
Fetches the alert counters that may be grouped by optional parameters.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | object | no | Query parameters |
Gets the most recent of the most severe alerts for each group, grouped by the scope you choose.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | object | no | Query parameters |
Fetches all registered alert types.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | object | no | Query parameters |
Fetches the resources' statuses that contain the alerts with the highest severity found for the resources.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | object | no | Query parameters |
Fetches count of alerts per customer.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | object | no | Query parameters |
Fetches alerts of the specified customers.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | object | no | Query parameters |
Returns count of active alerts and last modification time.
No parameter schema on file.
Lists protection policies (called protection plans in the Acronis console).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | object | no | Query parameters |
Gets one protection policy and its settings by ID.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| path | object | yes | URI path parameters |
| query | object | no | Query parameters |
Lists where policies are applied, meaning which resources each policy covers, with optional filters.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | object | no | Query parameters |
Counts problems with applied policies, grouped by issue.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | object | no | Query parameters |
Gets the status of every resource a given policy is applied to.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | object | no | Query parameters |
Lists resources (machines, mailboxes and other workloads), with optional filters.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | object | no | Query parameters |
Fetch a count of all resources that match filter parameters.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | object | no | Query parameters |
Gets one resource (a machine, mailbox or other workload) by ID.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| path | object | yes | URI path parameters |
| query | object | no | Query parameters |
Shows which resources are protected and which aren't.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | object | no | Query parameters |
Lists the Acronis agents installed on machines in a tenant.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | object | no | Query parameters |
Gets one Acronis agent by ID.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| path | object | yes | URI path parameters |
Lists EDR security incidents, with optional filters.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | object | no | Query parameters |
Gets the details of one EDR security incident by ID.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| path | object | yes | URI path parameters |
| query | object | no | Query parameters |
| headers | object | no | Request headers |
Gets the status of a response action that was started on an incident, such as isolating a machine.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| path | object | yes | URI path parameters |
| query | object | no | Query parameters |
Marks an alert as a false positive, or clears that mark. This changes the alert in Acronis for everyone.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| path | object | yes | URI path parameters |
| body | object | no | payload |
Changes an incident's investigation state, or adds a comment to the incident. The change is saved in Acronis.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| path | object | yes | URI path parameters |
| query | object | no | Query parameters |
| headers | object | no | Request headers |
| body | object | no | The investigation state update by a MDR vendor. |
Runs a protection policy right away on every resource it's applied to, which starts backup or protection jobs on those machines. Admin only.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| body | object | no | Request body (JSON object) |
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source is public; its licence metadata reads NOASSERTION rather than naming a licence
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Acronis Cyber Protect Cloud or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing ships as a container image. The scanner reads packages on npm and PyPI and public source; an image is neither, so there is no grade here — not a withheld one, an unmeasured one.
Release history
It installs from a container image rather than from a versioned package, so the command cannot be pinned to a release. The history below is for reading; the current release on file is 1.0.1.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Acronis Cyber Protect Cloud can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.