Connect the MSP360 Managed Backup to Claude AI

Connect MSP360 Managed Backup to Claude AI using a custom MCP server to check backup status, diagnose failures, and onboard computers using natural language prompts. Once connected, Claude AI can access Managed Backup resources and perform actions based on your account permissions.

This feature is provided as a beta version. AI-generated results may contain errors or inaccuracies. Results provided by the MCP server should be reviewed and verified before use and are not recommended for production environments.

Prerequisites

Install or update your Claude Desktop app to the latest version. Alternatively, you can use the Claude by Anthropic mobile app.
You need a Claude account. The Free plan supports one custom connector, which is sufficient if you plan to use the MCP server for Managed Backup only.
For authorization purposes, you will be prompted to use a registered Managed Backup account (the service provider or an administrator authorized by the service provider).
The MCP server must be enabled in the Management Console by the service provider. The service provider sets the access level for the MCP server connector and grants administrators permission to use the integration in full or read-only mode.

Refer to the Manage MCP Server Integration article for details on how to enable the MCP server in the Management Console.

Custom connectors are also available in the Claude mobile apps as a beta feature. This article describes the setup in Claude Desktop for Windows.

If IP allowlisting is enabled in the MSP360 Managed Backup Management Console, add the following IP address to Settings > IP Allowlisting: 54.198.147.76. This is the address the MSP360 MCP server uses to send requests to your Managed Backup account. The AI agent connects to the MCP server, and the MCP server connects to Managed Backup, so you don’t need to allowlist the AI agent's IP ranges. Without this address, requests from the MCP server are blocked, and the AI agent can’t access your account.

You also sign in to the Management Console from your browser during setup, so the IP address you use to access the console must be allowed as well.

If you are using Claude Desktop:
Requests to the MCP server are initiated locally from your computer through the app. Therefore, add your current public IP address (or your office/VPN IP range) to the Management Console's IP allowlist. You should also add the IP address required for MCP server to the allowlist.
Important: If your ISP assigns you a dynamic IP, Claude will lose access to the server whenever your IP changes until you update the address in the console.
If you are using the Claude mobile app:
The mobile app routes requests through Anthropic’s cloud infrastructure. For this setup to work on a smartphone with IP allowlisting enabled, you will need to add Anthropic's (Claude's) IP address ranges to your allowlist. Otherwise, the mobile client will get a connection error (403 Forbidden).

If IP allowlisting is not enabled, skip this step.

Adding the MCP Server

MCP servers are added to Claude as custom connectors. Follow the steps below to add the Managed Backup MCP server.

Open the Claude app and click your account icon in the bottom-left corner to open Settings.

On Connectors, expand + Add, and select Add custom connector.

Name the custom connector and enter the following MCP server URL: https://mbs-web-mcp.services.mspbackups.com/

Click Continue, then click Add.

Once the connector is added, click Connect.

To proceed, click Continue connecting. You will be redirected to a browser window to authorize the connector.

Review the requested access and click Approve.

Complete the authorization process. Once authorization is complete, you can use the integration in Claude.

The connector is available under Settings > Connectors with the name you specified when adding it.

DBy default, approving this request gives the connector read-only access to the Managed Backup API under your account. If Full access (allow changes) is enabled, it can do anything your account can do in the Management Console: view and create backup plans, add or remove destinations, manage companies and administrators, and more. Treat approving it the same way you'd treat sharing your Management Console login.

Access is not permanent for this custom connector. It renews automatically for up to 12 hours of active use. To end it sooner, revoke the authorization. Revoking disconnects Claude immediately.

Using the Integration

Manage Connector

On the connector page, you can view its status, disconnect the connector, refresh the tool list, manage tool permissions, or remove the connector completely.

Once the Managed Backup MCP connector is connected, its tools provide access to Managed Backup resources such as backup plans, computers, users, companies, storage accounts, and backup destinations.

You can ask Claude for information or request an action in the chat. Depending on the permissions configured for the tools, Claude may ask you to confirm an action before performing it.

You can also manage permissions for multiple tools in bulk. Expand the tool permission control and select the permission that applies to all tools. The Custom option allows you to configure specific permissions for individual tools.

Example Prompts

Start with something simple, such as:

"Show me a list of computers with their most recent backup statuses".

Below you can find more prompts to explore Managed Backup MCP connector capabilities:

Show me every backup failure from the last 7 days, grouped by company.
Which computers haven't had a successful backup in 14 days?
For our top five clients, list backup issues from the last 30 days by computer, and tell me which failures are on their network rather than on our side.
Create a company called [Company name] and cap their [Storage name] storage at 500 GB.
Create an administrator [Administrator email] for [Company Name], give them access to just that company, and let them manage backups but not billing.
Create nightly Files backup plans for all [Company Name] computers, keeping 30 days of versions. Distribute their schedule evenly throughout the night.

Refer to the Use the MCP Server article for more prompts.