MSP360
MCP server for MSP360's Managed Backup Service API — companies, computers, and backup plans.
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
ghcr.io/wyre-ai/msp360-mcp:v1.0.1claude mcp add msp360 -e 'MSP360_USERNAME=<MSP360_USERNAME>' -e 'MSP360_PASSWORD=<your msp360_password>' -e 'MCP_TRANSPORT=stdio' -e 'AUTH_MODE=env' -e 'LOG_LEVEL=info' -- docker run -i --rm ghcr.io/wyre-ai/msp360-mcp:v1.0.1
{
"mcpServers": {
"msp360": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/wyre-ai/msp360-mcp:v1.0.1"
],
"env": {
"MSP360_USERNAME": "<MSP360_USERNAME>",
"MSP360_PASSWORD": "<your msp360_password>",
"MCP_TRANSPORT": "stdio",
"AUTH_MODE": "env",
"LOG_LEVEL": "info"
}
}
}
}
Environment variables
MSP360_USERNAMErequired MSP360 Managed Backup Service provider-portal usernameMSP360_PASSWORDrequired secret MSP360 Managed Backup Service provider-portal passwordMCP_TRANSPORTTransport mode for the server. Set to 'stdio' for local CLI use; the image defaults to 'http' for gateway hosting.AUTH_MODECredential source: 'env' reads vars locally, 'gateway' expects header injection from the WYRE MCP Gateway.LOG_LEVELLog verbosity: debug, info, warn, error
Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
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.
Configuration
| Env var | Description | |||
|---|---|---|---|---|
MSP360_USERNAME | MSP360 provider-portal username. | |||
MSP360_PASSWORD | MSP360 provider-portal password. | |||
MCP_TRANSPORT | stdio (default) or http. | |||
AUTH_MODE | env (default, reads the vars above) or gateway (credentials arrive per-request via X-MSP360-Username / X-MSP360-Password headers, injected by the Conduit gateway). | |||
CONDUIT_S2S_SECRET | When set, the HTTP transport requires a valid X-Gateway-S2S header (Conduit sidecar auth) on every /mcp request. | |||
LOG_LEVEL | debug \ | info (default) \ | warn \ | error. |
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 --noEmit
Docker
docker build -t msp360-mcp .
docker run -p 8080:8080 -e MSP360_USERNAME=... -e MSP360_PASSWORD=... msp360-mcp
Frequently asked questions
What is MSP360?
MCP server for MSP360's Managed Backup Service API — companies, computers, and backup plans.
How do I install MSP360?
It runs on your machine. In Claude Code: claude mcp add msp360 -e 'MSP360_USERNAME=<MSP360_USERNAME>' -e 'MSP360_PASSWORD=<your msp360_password>' -e 'MCP_TRANSPORT=stdio' -e 'AUTH_MODE=env' -e 'LOG_LEVEL=info' -- docker run -i --rm ghcr.io/wyre-ai/msp360-mcp:v1.0.1. For other clients, paste the JSON configuration from this page into their MCP settings.
Does MSP360 need an API key?
Yes. It expects MSP360_USERNAME, MSP360_PASSWORD, which you set in its configuration.
Is MSP360 open source?
Its code is public on GitHub, but the repository does not declare a standard license.
Who maintains MSP360?
It is published by WYRE-AI. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.