How do I install MSP360?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does MSP360 need an API key?

The publisher lists these environment variables: MSP360_USERNAME, MSP360_PASSWORD, MCP_TRANSPORT, AUTH_MODE, LOG_LEVEL.

What transport does MSP360 use?

MSP360 runs locally over stdio.

MSP360

by io.github.WYRE-AI

MCP server for MSP360's Managed Backup Service API — companies, computers, and backup plans.

Power your agent

Add this server

The publisher's own command. Not a PlugMCP endpoint.

Local command

docker run -i --rm ghcr.io/wyre-ai/msp360-mcp:v1.0.0

Credentials from the publisher

MSP360_USERNAME — MSP360 Managed Backup Service provider-portal username
MSP360_PASSWORD — MSP360 Managed Backup Service provider-portal password
MCP_TRANSPORT — Transport mode for the server. Set to 'stdio' for local CLI use; the image defaults to 'http' for gateway hosting.
AUTH_MODE — Credential source: 'env' reads vars locally, 'gateway' expects header injection from the WYRE MCP Gateway.
LOG_LEVEL — Log verbosity: debug, info, warn, error

Provider

Claude Code

MSP360_USERNAME=<value> MSP360_PASSWORD=<secret> MCP_TRANSPORT=<value> AUTH_MODE=<value> LOG_LEVEL=<value> claude mcp add io.github.wyre-ai-msp360-mcp -- docker run -i --rm ghcr.io/wyre-ai/msp360-mcp:v1.0.0

Run in a terminal.

Claude Desktop

{
  "mcpServers": {
    "io.github.wyre-ai-msp360-mcp": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/wyre-ai/msp360-mcp:v1.0.0"
      ],
      "env": {
        "MSP360_USERNAME": "<value>",
        "MSP360_PASSWORD": "<secret>",
        "MCP_TRANSPORT": "<value>",
        "AUTH_MODE": "<value>",
        "LOG_LEVEL": "<value>"
      }
    }
  }
}

claude_desktop_config.json

Step-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Related MCP

Related skills

View all

Questions

How do I install MSP360?: Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.
Does MSP360 need an API key?: The publisher lists these environment variables: MSP360_USERNAME, MSP360_PASSWORD, MCP_TRANSPORT, AUTH_MODE, LOG_LEVEL.
What transport does MSP360 use?: MSP360 runs locally over stdio.
When was MSP360 last checked?: Last checked 2026-10-20. MCP server for MSP360's Managed Backup Service API — companies, computers, and backup plans.

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`.

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