acronis-mcp

Acronis MCP server — exposes the Acronis Cyber Protect Cloud platform APIs as MCP tools.

Naming note: app.mspbots.ai calls this integration "Acronis" (sys_integration.subject_code = ACRONIS, type "BackUp Disaster Recovery Software"). The underlying vendor product is Acronis Cyber Protect Cloud, and its public API surface is officially named the "Acronis Cyber Platform APIs" (developer.acronis.com).

MSPbots Connector

The MCP Gateway built for MSPs: visible, controlled, and your data stays where it belongs.

Get started at connect.mspbots.ai →

MSPbots Connector gives your AI clients one MCP URL to reach your entire MSP stack (RMM, PSA, documentation, security, finance), and gives you control over who can call which tool and a record of everything that was called.

Hosted service: connect.mspbots.ai · Free to use.

Why Connector

Quick start

1. Sign up at connect.mspbots.ai.

2. Connect your vendors. Pick from 150+ connectors and authorize each one on the vendor's own page, or bring your own API keys. No extra vendor accounts needed.

3. Set access. Create roles and decide which tools each role may call. Nothing is allowed until you allow it.

4. Add your MCP URL to your AI client. Copy the URL from your Connector dashboard into Claude, ChatGPT, Cursor, VS Code, Gemini, Codex, or any MCP-capable client.

5. Ask your AI to do real work, and watch every call appear in the audit log.

Features

Unified gateway

• One MCP URL for all your AI clients

• 150+ connectors across the MSP stack

• Custom MCP servers supported, free

• Authorization happens on each vendor's own page; the AI never sees passwords or tokens

• Bring your own credentials: use the vendor API keys you already have

• Multiple accounts per app; connect once, reuse across AI clients

• Tool search: finds the right action for the task

• One sign-in; vendor credentials are injected behind the scenes and OAuth tokens refresh automatically

Visibility

• Audit log for every tool call (who, which vendor, when)

• Usage dashboard: call volume, top vendors, error rate, per-user activity

• Export audit logs to CSV, or stream to Loki, Graylog, or LogScale (SIEM)

• Optional recording of tool arguments and result summaries (off by default, enabled per organization)

Control

• Per-role, per-tool allowlist, deny by default

• owner / admin / member roles

• SCIM provisioning with Entra ID, Okta, JumpCloud, and Google Workspace

Security

• Credentials encrypted one record at a time (AES-256-GCM, per-record key)

• AI clients authenticate with OAuth 2.1 + PKCE

• Vendor responses are scanned for prompt-injection patterns and returned as structured data. This is one layer of defense, not a guarantee against every attack.

• Static egress IP for customer firewall and API allowlisting

Pricing

Free.

Links: connect.mspbots.ai · mspbots.ai

Related MCP server: saas-alerts-mcp

Overview

This server implements the Model Context Protocol (Streamable HTTP/SSE transport) and covers the 14 read-only interfaces that MSPbots' own Acronis integration actually uses across 5 Acronis sub-APIs, matching the interface scope configured in MSPbots' sys_integration/sys_integration_api tables:

It follows the MSPbots Vendor MCP Service SOP: stateless, no stored credentials, per-request header authentication.

The underlying API authenticates via OAuth2 Client Credentials (POST <datacenter-url>/api/2/idp/token with client_id + client_secret, matching the "Data Center URL / Client ID / Client Secret" fields configured in MSPbots' own Acronis integration). This server does not perform the token exchange itself — it receives an already-obtained bearer access token per request, the same pattern used for other real-OAuth2 vendors in this MCP fleet (e.g. BizRatings, ConnectWise Asio): the gateway mints/refreshes the token from client_id/client_secret, and only the resulting token — plus the tenant's data center URL — reaches this server.

Quick Start

Docker (recommended)

docker compose up --build

The server starts on http://localhost:8080.

Local (uv)

uv sync
python -m acronis_mcp

Health Check

curl http://localhost:8080/health
# {"status": "ok", "service": "acronis-mcp", "transport": "http"}

No credentials are required for the health endpoint.

Authentication

Every request to /mcp must include the following HTTP headers:

Missing either header returns 401 Unauthorized.

Environment Variables

MCP Endpoint

POST http://localhost:8080/mcp

Connect your MCP client with:

• Transport: http (Streamable HTTP / SSE)

• Headers: X-Acronis-Token: <access_token> (required), X-Acronis-Datacenter-Url: <datacenter_url> (required)

Tool List

14 tools, matching the exact interface count MSPbots' own Acronis integration uses.

Alert Manager (6)

Task Manager (2)

Agent Manager (1)

Resource Management (2)

Policy Management (2)

Account Management (1)

Test Example

Fetch alerts:

{
  "method": "tools/call",
  "params": { "name": "acronis_get_alerts", "arguments": { "limit": 10, "show_deleted": false } }
}

Equivalent curl against the running server (streamable HTTP MCP endpoint):

curl -X POST http://localhost:8080/mcp \
  -H "Content-Type: application/json" \
  -H "X-Acronis-Token: <access_token>" \
  -H "X-Acronis-Datacenter-Url: https://us5-cloud.acronis.com" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/call",
    "params": { "name": "acronis_get_alerts", "arguments": { "limit": 10 } }
  }'

A parameterized call:

{
  "method": "tools/call",
  "params": {
    "name": "acronis_get_tenant",
    "arguments": { "tenant_id": "890f6ce1-918d-43c8-9f9c-8febb5bec432" }
  }
}

API Reference

• API library: https://developer.acronis.com/doc/outbound/apis/index.html

• Alert Manager v1: https://developer.acronis.com/doc/alerts/v1/reference/index.html

• Task Manager v2: https://developer.acronis.com/doc/tasks/v2/reference/index.html

• Agent Manager v2: https://developer.acronis.com/doc/agents/v2/reference/index.html

• Resource & Policy Management v4: https://developer.acronis.com/doc/resource-policy-management/v4/reference/index.html

• Account Management v2: https://developer.acronis.com/doc/account-management/v2/reference/index.html

Known Gaps / Implementation Notes

• Scope is intentionally bounded to the 14 interfaces MSPbots' own Acronis integration is configured to use, not the full Acronis Cyber Platform API surface (which also includes PSA, Event Manager, Disaster Recovery, EDR, Vaults Management, File Sync & Share, and write/management endpoints across every sub-API) — per this task's requirement that interface count stay consistent with MSPbots.

• Endpoints with a large filter surface (e.g. acronis_get_alerts, acronis_get_customer_alerts, acronis_get_tasks, acronis_get_resources, acronis_get_policies) expose the most commonly-used filters as named parameters plus a generic extra_params: dict for the remaining, less-common query filters documented in the vendor API reference.

• X-Acronis-Datacenter-Url has no default — Acronis Cyber Protect Cloud tenants are provisioned on one of several regional data centers with no single fallback, so the caller must always supply it (matches the "Data Center URL" field being a required field in MSPbots' own Acronis integration config).

• Not yet tested against a live Acronis account — only protocol-level verification (health check, 401 on missing headers, tools/list returning all 14 tools) has been done so far.