
Kaseya VSA
io.github.WYRE-AI由 GitHub 帳號 WYRE-AI 發布v1.1.8更新於 Nov 21, 2026
MCP server for Kaseya VSA RMM — agents, patches, procedures, alarms, tickets.
概覽
針對 Kaseya VSA RMM 的 MCP 伺服器,讓助理檢視受管端點、軟硬體清單、修補程式、程序、告警與工單。
- 可以做什麼
- 列出並檢視受管端點,在 MCP Apps 主機中顯示互動式裝置卡片
- 讀取某端點的軟體、硬體清單與修補程式狀態
- 部署修補程式或在端點上執行程序,操作前會要求確認
- 列出未處理告警、服務台工單、組織與機器群組
- 適用情境
- 適合需要讓助理查詢 Kaseya VSA 環境資訊,或執行查看修補程式狀態、執行程序、部署修補程式等日常 RMM 操作的場合。
- 執行需求
- 以本機 stdio 程序執行(Docker 映像或 npm 建置)。需要 KASEYA_VSA_TENANT_URL,以及 KASEYA_VSA_USERNAME 與 KASEYA_VSA_PASSWORD 組合或 KASEYA_VSA_K1_TOKEN。HTTP 模式另需 CONDUIT_S2S_SECRET 與 X-Gateway-S2S 標頭;閘道模式從 X-Kaseya-VSA-* 標頭取得憑證。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 Kaseya VSA,將其新增到工作區。
- 為需要使用其工具的對話啟用該服務。
Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。
其他 MCP 客戶端
參照 儲存庫 中的啟動說明。
README
Kaseya VSA MCP Server
[Release] [License: Apache 2.0]
Model Context Protocol (MCP) server for the Kaseya VSA RMM API. Exposes managed endpoints, software / hardware inventory, patch state, agent procedures, alarms, Service Desk tickets, organizations, and machine groups to AI assistants.
Tools
When the user omits required filters or runs a destructive action, the server uses MCP elicitation to prompt for choices or confirm.
Interactive device card (MCP Apps)
kaseya_vsa_get_agent renders as a read-only interactive device card in MCP
Apps hosts (Claude Desktop/web), showing the endpoint's name, online status,
organization, machine group, OS, IP address, and last check-in. The card is
neutral by default, brandable via window.__BRAND__ injection or
MCP_BRAND_* env vars (MCP_BRAND_NAME, MCP_BRAND_LOGO_URL,
MCP_BRAND_PRIMARY_COLOR, MCP_BRAND_ACCENT_COLOR, MCP_BRAND_BG,
MCP_BRAND_TEXT) applied at serve time. Plain-JSON behavior is unchanged in
other hosts. After editing ui/, regenerate the embedded bundle with
npm run build:ui.
Configuration
Copy .env.example and set the variables below.
Either the username + password pair OR KASEYA_VSA_K1_TOKEN is required for stdio and AUTH_MODE=env.
/health stays unauthenticated and does not read credentials. The stdio transport does not use CONDUIT_S2S_SECRET.
HTTP authentication
With MCP_TRANSPORT=http and CONDUIT_S2S_SECRET set, every /mcp request must include X-Gateway-S2S. The check is verifyS2sHeader in src/s2s-verify.ts: the header value is t=<unix seconds>,v1=<hex>, where the hex is HMAC-SHA256 of the literal string t=<unix seconds> keyed with CONDUIT_S2S_SECRET (64 lowercase hex characters). The timestamp must be within 300 seconds of the server clock. A missing or invalid header returns HTTP 401 before vendor credentials are read.
In AUTH_MODE=gateway, /mcp also requires X-Kaseya-VSA-Tenant-Url plus either (X-Kaseya-VSA-Username and X-Kaseya-VSA-Password) or X-Kaseya-VSA-K1-Token. Those headers are the only credential source for that request. A request missing them returns 401 and does not fall back to KASEYA_VSA_* in the process environment.
Each accepted request creates a fresh server instance with isolated credentials — no cross-tenant process.env pollution.
Local development
HTTP refuses to start until CONDUIT_S2S_SECRET is set:
Local HTTP without a secret is development-only. It binds 127.0.0.1 only and logs a warning. A non-loopback MCP_HTTP_HOST is ignored and the override is logged:
Docker
The image listens on 0.0.0.0 inside the container (MCP_HTTP_HOST) and defaults to AUTH_MODE=gateway. Publish the port on loopback and pass the S2S secret. In gateway mode, Kaseya credentials arrive on each request as headers; they are not read from the environment.
Compose refuses to start when CONDUIT_S2S_SECRET is unset, sets AUTH_MODE=gateway, does not inject static KASEYA_VSA_* credentials, and publishes 127.0.0.1:8080:8080:
Single-tenant HTTP (AUTH_MODE=env) still requires the S2S secret, then uses KASEYA_VSA_*:
License
Apache-2.0
來源:README.md,提交 27c3dc7
工具
0版本歷史
4- v1.1.8最新Nov 21, 2026
- v1.1.7Oct 14, 2026
- v1.1.6Oct 5, 2026
- v1.1.5Sep 16, 2026
評分
已滿足適用檢查項的 50%
該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。
- 近 30 天內可連通25 分
請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。
- 已宣告認證方式10 分
請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。
- 已列出工具15 分
請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。
- 描述必需15 分
- 圖示10 分
- 文件15 分
- 授權條款10 分