MSP360

io.github.WYRE-AI由 GitHub 账号 WYRE-AI 发布v1.0.1更新于 Oct 24, 2026

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

概览

AI 生成的概览

面向 MSP360 托管备份服务的 MCP 服务器,让助手查看公司、计算机与备份计划,并检查备份健康状况。

可以做什么
  • 列出并查询服务商账户下的公司(客户组织)
  • 列出受管计算机,并按 HID 获取单台计算机
  • 列出某台计算机上的备份/恢复计划,并读取计划详情、状态与运行历史
  • 启动或停止某个计划的备份运行
  • 查看所有终端或按用户筛选的最新计划运行监控状态
适用场景
适合 MSP 或经销商人员用助手查询哪些数据已备份、最近运行是否成功,并在不打开服务商门户的情况下启动或停止备份运行。
运行要求
以本地进程方式运行(容器镜像,stdio 传输)。需要 MSP360 托管备份服务服务商门户的用户名和密码,通过 MSP360_USERNAME 与 MSP360_PASSWORD 提供,或在网关认证模式下由网关注入请求头。需要访问 MSP360 API 的网络连接。
安装前请注意
服务商门户密码是长期有效的凭据,可访问整个服务商账户,需谨慎保管。启动和停止计划的工具会改变真实终端上的备份状态。README 说明计费、许可证和计算机授权等操作在本版本中被有意排除。

安装

在 SourceWeft 中

  1. 打开 控制台中的 MSP360,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

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

Env varDescription
MSP360_USERNAMEMSP360 provider-portal username.
MSP360_PASSWORDMSP360 provider-portal password.
MCP_TRANSPORTstdio (default) or http.
AUTH_MODEenv (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_SECRETWhen set, the HTTP transport requires a valid X-Gateway-S2S header (Conduit sidecar auth) on every /mcp request.
LOG_LEVELdebug | info (default) | warn | error.

Request limits

  • HTTP request bodies are capped at 256 KiB (262144 bytes). After the X-Gateway-S2S check passes, a Content-Length above the cap returns 413 with a JSON-RPC error; bodies without Content-Length are capped by the MCP SDK transport. Unauthenticated requests still get 401 first.
  • tools/call arguments are capped at 10,000 elements (every array item and object key at any depth). Larger inputs return an isError tool 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

bash
npm installnpm run buildnpm testnpm run lint   # tsc --noEmit

Docker

bash
docker build -t msp360-mcp .docker run -p 8080:8080 -e MSP360_USERNAME=... -e MSP360_PASSWORD=... msp360-mcp

来源:README.md,提交 e4cc731

工具

0
SourceWeft 曾在隔离沙箱中以无凭据方式启动该软件包一次,以列出其工具,但未能完成:该软件包类型无法在沙箱中运行。

版本历史

2
  1. v1.0.1最新Oct 22, 2026
  2. v1.0.0Sep 20, 2026

评分

已满足适用检查项的 40%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分

    请在仓库或注册中心条目中声明许可证。