
Kaseya VSA
io.github.WYRE-AIPublished by GitHub account WYRE-AIv1.1.8Updated Nov 21, 2026
MCP server for Kaseya VSA RMM — agents, patches, procedures, alarms, tickets.
Overview
MCP server for Kaseya VSA RMM that lets an assistant browse managed endpoints, inventory, patches, procedures, alarms and tickets.
- What you can do
- List and inspect managed endpoints, including an interactive device card in MCP Apps hosts
- Read software and hardware inventory and patch status for an agent
- Deploy patches or run agent procedures, with confirmation prompts
- List open alarms, Service Desk tickets, organizations and machine groups
- When to use it
- Useful when an assistant should answer questions about a Kaseya VSA estate or carry out routine RMM actions such as checking patch state, running a procedure or deploying patches on an endpoint.
- Requirements
- Runs as a local stdio process (Docker image or npm build). Needs KASEYA_VSA_TENANT_URL plus either KASEYA_VSA_USERNAME and KASEYA_VSA_PASSWORD or KASEYA_VSA_K1_TOKEN. HTTP mode additionally requires CONDUIT_S2S_SECRET and an X-Gateway-S2S header; gateway mode takes credentials from X-Kaseya-VSA-* headers.
Installation
In SourceWeft
- Open Kaseya VSA in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
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
Source: README.md at commit 27c3dc7
Tools
0Version history
4- v1.1.8LatestNov 21, 2026
- v1.1.7Oct 14, 2026
- v1.1.6Oct 5, 2026
- v1.1.5Sep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts