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 分

    請在儲存庫或註冊中心條目中宣告授權條款。