MSP360 MCP Server
Manage and monitor MSP360 Managed Backup Service resources through MCP tools.
List and get companies and managed computers.
List and get backup/restore plans, fetch plan info and run history, and start or stop backup runs.
Retrieve account-wide or per-user monitoring status for latest plan runs.
List and get licenses, optionally filtered to unassigned licenses.
Authenticate using MSP360 provider credentials, with env or gateway modes, and run over stdio or HTTP transports.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@MSP360 MCP Server show me the latest backup monitoring status"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MSP360 MCP Server
MCP server for MSP360's Managed Backup Service API (formerly CloudBerry Lab) - companies, managed computers, backup plans, monitoring, and licenses, for AI assistants and the WYRE Conduit gateway.
Authentication
Provide the Managed Backup Service provider-portal UserName/Password pair. This server exchanges it for a short-lived bearer token via POST /api/Provider/Login and caches it, re-authenticating automatically whenever the vendor rejects the cached token (HTTP 401) - callers only ever need to supply the long-lived username/password.
Related MCP server: nable-rmm-mcp
Configuration
Env var | Description |
| MSP360 provider-portal username. |
| MSP360 provider-portal password. |
|
|
|
|
| When set, the HTTP transport requires a valid |
|
|
Request limits
HTTP request bodies are capped at 256 KiB (262144 bytes). After the
X-Gateway-S2Scheck passes, aContent-Lengthabove the cap returns 413 with a JSON-RPC error; bodies withoutContent-Lengthare capped by the MCP SDK transport. Unauthenticated requests still get 401 first.tools/callarguments are capped at 10,000 elements (every array item and object key at any depth). Larger inputs return anisErrortool result and are never dispatched.
These limits address CVE-2026-111768 / GHSA-46jr-4wx8-v453 (memory exhaustion during validation) and GHSA-f897-62hf-6gxq (no request body / batch cap).
Tools
Companies
msp360_list_companies- list companies (customer organizations) under this provider account.msp360_get_company- get a single company by ID.
Computers
msp360_list_computers- paginated list of managed computers (endpoints).msp360_get_computer- get a single computer by HID.
Backup Plans
msp360_list_plans- list backup/restore plans on a computer.msp360_get_plan- get a single plan by ID.msp360_get_plan_info- get status/info for a plan.msp360_get_plan_history- get run history for a plan, optionally filtered to a date.msp360_start_plan- start a backup run for a plan.msp360_stop_plan- stop a currently running backup for a plan.
Monitoring
msp360_get_monitoring- status data for the latest plan runs on all endpoints.msp360_get_monitoring_for_user- status data for the latest plan runs, filtered by user.
Licenses
msp360_list_licenses- list available licenses, optionally filtered to unassigned ones.msp360_get_license- get a single license by ID.
Scope
This is a v1 / MVP surface covering the core "what's backed up and is it healthy" MSP workflow. Explicitly out of scope for now: Administrators, Billing, Builds, Packages, Destinations/Accounts (storage-provisioning config), Users/Authenticate, and License Grant/Release/Revoke (mutating license assignment) and computer authorization/de-authorization - these are provider/reseller-admin-console-level operations with real billing/access consequences, distinct from day-to-day MSP monitoring, and worth a deliberate separate decision later rather than bundling into v1.
Development
npm install
npm run build
npm test
npm run lint # tsc --noEmitDocker
docker build -t msp360-mcp .
docker run -p 8080:8080 -e MSP360_USERNAME=... -e MSP360_PASSWORD=... msp360-mcpAvailable Tools
14 toolsmsp360_get_companyA
Get a single MSP360 company by ID.
Inputs: id (required).
msp360_get_computerA
Get a single managed computer by its HID.
Inputs: hid (required).
msp360_get_licenseB
Get a single MSP360 license by ID.
Inputs: id (required).
msp360_get_monitoringA
Get status data for the latest backup plan runs on all endpoints (account-wide health/alerts).
Inputs: no named parameters.
msp360_get_monitoring_for_userA
Get status data for the latest backup plan runs on online endpoints, filtered to a specific user.
Inputs: userId (required).
msp360_get_planC
Get a single backup/restore plan on a computer by plan ID.
Inputs: id (required), hid (required).
msp360_get_plan_historyA
Get run history for a backup/restore plan on a computer, optionally filtered to a specific date.
Inputs: id (required), hid (required), day, year, +1 more.
msp360_get_plan_infoC
Get status/info for a backup/restore plan on a computer.
Inputs: id (required), hid (required).
msp360_list_companiesA
List all companies (customer organizations) managed under this MSP360 provider account.
Inputs: no named parameters.
msp360_list_computersA
List managed computers (endpoints), paginated by offset/count.
Inputs: count (required), offset (required).
msp360_list_licensesB
List available MSP360 licenses, optionally filtered to only unassigned ones.
Inputs: isAvailable.
msp360_list_plansB
List backup/restore plans configured on a computer.
Inputs: hid (required).
msp360_start_planB
Start a backup run for a plan on a computer.
Inputs: id (required), hid (required), mode.
msp360_stop_planA
Stop a currently running backup for a plan on a computer.
Inputs: id (required), hid (required), force.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 14 tools
Most tools are clearly distinct by resource and action. The only potential confusion is between get_plan and get_plan_info, where the former likely returns configuration and the latter status, but descriptions help differentiate. get_plan_history and get_monitoring* are unambiguous.
All tools follow a consistent msp360_ prefix with verb_noun (list_*, get_*, start_*, stop_*) naming. Even compound names like get_monitoring_for_user follow the pattern predictably.
14 tools is well-scoped for an MSP backup management server, covering companies, computers, plans, monitoring, and licenses without excessive granularity or overlap.
The surface covers listing/getting key entities and operational actions on plans (start/stop/info/history). Minor gaps exist: no create/update/delete for plans or companies, and no restore functionality, but these may be outside the server's intended monitoring/ops scope.
Maintenance
Related MCP Connectors
Scopable MSP API: clients, quotes, assessments, compliance, QBRs. OAuth 2.1, read-only or read-write
Microsoft 365, CRM, Partner Center and tenant operations for organisations and MSPs.
Sherweb Platform MCP server to manage subscriptions and orders. Use OpenID Connect to authenticate.
Managed MCP gateway with OAuth, per-agent permissions, shared accounts and activity logs.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceProvides AI assistants and MCP clients with API access to manage Firewalla MSP resources including boxes, devices, alarms, rules, flows, and target lists.19 npmGPL 3.0
- AlicenseNot gradedqualityCmaintenanceEnables interaction with N-able RMM (N-sight) API to manage clients, sites, devices, and retrieve monitoring data such as checks, patches, and performance history.Apache 2.0
- AlicenseNot gradedqualityDmaintenanceMCP server for MSP360 platform enabling management of backup and RMM operations through Claude Desktop with 69 tools.MIT
- AlicenseCqualityBmaintenanceEnables interaction with Mango Office cloud PBX to manage calls, users, recordings, SMS, and call statistics.855 npm1MIT