Kaseya VSA MCP server
MCP server for Kaseya VSA RMM — agents, patches, procedures, alarms, tickets.
0 stars
Reviews
Write oneNobody has reviewed Kaseya VSA yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Kaseya VSA tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.10 · 2026-10-31 · same rubric, same numbers if you re-run it
- –Code scanpackage could not be scannedn/a
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitystatic API keys via environment variables6/15
- Maintenancelast push 2 days ago15/15
- Maintainer identityregistry namespace matches repository owner7/10
How Kaseya VSA compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 70/100
- higher than 35% of 48,255 servers
Release history: 3 versions in the registry since 2026-08-26, latest 2026-10-14, typically one every 40 days.
Install Kaseya VSA in Claude Code, Cursor or VS Code
claude mcp add kaseya-vsa-mcp -- docker run -i --rm ghcr.io/wyre-ai/kaseya-vsa-mcp:v1.1.7
What the publisher says
From the Kaseya VSA repository's README, as published. We do not edit it. Read it on GitHub
Kaseya VSA MCP Server
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)
kaseyavsagetagent 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 MCPBRAND env vars (MCPBRANDNAME, MCPBRANDLOGOURL, MCPBRANDPRIMARYCOLOR, MCPBRANDACCENTCOLOR, MCPBRANDBG, MCPBRANDTEXT) 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
Environment-variable mode (default)
Either the username + password pair OR the KASEYAVSAK1_TOKEN is required.
Gateway mode
When deployed behind the WYRE MCP Gateway, set AUTH_MODE=gateway and the server will read credentials from per-request HTTP headers:
- X-Kaseya-VSA-Tenant-Url (required)
- X-Kaseya-VSA-Username (with password)
- X-Kaseya-VSA-Password (with username)
- X-Kaseya-VSA-K1-Token (alternative to username + password)
Each request creates a fresh server instance with isolated credentials — no cross-tenant process.env pollution.
Local development
npm install
npm run build
KASEYA_VSA_TENANT_URL=https://vsa.example.com/api/v1.0 \
KASEYA_VSA_USERNAME=... \
KASEYA_VSA_PASSWORD=... \
npm startRun as HTTP for testing:
MCP_TRANSPORT=http npm start
curl http://localhost:8080/healthDocker
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Kaseya VSA: common questions
- Is Kaseya VSA MCP server safe?
- Mostly: it is graded B (70/100). Read the Kaseya VSA safety report
- How do I install Kaseya VSA?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Kaseya VSA need an API key?
- Yes. The registry entry asks for
KASEYA_VSA_PASSWORD,KASEYA_VSA_K1_TOKEN. - Is Kaseya VSA maintained?
- The last commit was 6 days ago (2026-10-29). The latest release is v1.1.7.