
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 分