
MSP360
io.github.WYRE-AIPublished by GitHub account WYRE-AIv1.0.1Updated Oct 24, 2026
MCP server for MSP360's Managed Backup Service API — companies, computers, and backup plans.
Overview
MCP server for MSP360 Managed Backup Service that lets an assistant browse companies, computers and backup plans and check backup health.
- What you can do
- List and look up companies (customer organizations) under the provider account
- List managed computers and fetch a single computer by HID
- List backup/restore plans on a computer and read a plan's details, status and run history
- Start or stop a backup run for a plan
- Read monitoring status for the latest plan runs across all endpoints or filtered by user
- When to use it
- Useful for MSP or reseller staff who want to ask an assistant what is backed up, whether recent runs succeeded, and to trigger or stop a backup run without opening the provider portal.
- Requirements
- Runs as a local process (container image, stdio transport). Needs an MSP360 Managed Backup Service provider-portal username and password, supplied through MSP360_USERNAME and MSP360_PASSWORD, or via gateway-injected headers in gateway auth mode. Network access to the MSP360 API is required.
Installation
In SourceWeft
- Open MSP360 in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
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
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
Docker
Source: README.md at commit e4cc731
Tools
0Version history
2- v1.0.1LatestOct 22, 2026
- v1.0.0Sep 20, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.