Kaseya VSA

MCP server for Kaseya VSA RMM — agents, patches, procedures, alarms, tickets.

Quick Install

Automated & IDE Setup

Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.

Add to Cursor Add to VS Code

Manual Client & Custom JSON ConfigExpand JSON ▾

Client Config & Setup

Choose your client or environment

Target File:~/Library/Application Support/Claude/claude_desktop_config.json

claude_desktop_config.json

{
  "mcpServers": {
    "kaseya-vsa": {
      "command": "npx",
      "args": [
        "-y",
        "kaseya-vsa"
      ]
    }
  }
}

💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.

Documentation Overview

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

Tool	Description
`kaseya_vsa_list_agents`	List managed endpoints (agents). Optional `$filter`.
`kaseya_vsa_get_agent`	Get an agent's details by ID (renders as an interactive card in MCP Apps hosts).
`kaseya_vsa_get_software_inventory`	Installed software for an agent.
`kaseya_vsa_get_hardware_inventory`	Hardware audit for an agent.
`kaseya_vsa_get_patch_status`	Pending and installed patches for an agent.
`kaseya_vsa_deploy_patches_now`	Force a patch deploy on an agent (destructive — confirmation required).
`kaseya_vsa_list_procedures`	Agent procedures available to run.
`kaseya_vsa_run_procedure`	Execute a procedure on an agent (destructive — confirmation required).
`kaseya_vsa_list_alarms`	Open alarms (optional state filter; date-window elicitation if missing).
`kaseya_vsa_list_tickets`	Service Desk tickets (returns a friendly message if SD module isn't enabled).
`kaseya_vsa_list_organizations`	Tenant organizations.
`kaseya_vsa_list_machine_groups`	Machine group hierarchy.

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

Environment-variable mode (default)

Variable	Required	Description
`KASEYA_VSA_TENANT_URL`	yes	Full base URL incl. `/api/v1.0`
`KASEYA_VSA_USERNAME`	one of	Local-auth username
`KASEYA_VSA_PASSWORD`	one of	Local-auth password (secret)
`KASEYA_VSA_K1_TOKEN`	one of	Kaseya One SSO token (alternative to username + password)
`MCP_TRANSPORT`	no	`stdio` (default) or `http`
`MCP_HTTP_PORT`	no	HTTP listen port (default `8080`)
`AUTH_MODE`	no	`env` (default) or `gateway`

Either the username + password pair OR the KASEYA_VSA_K1_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

Terminal

npm install
npm run build
KASEYA_VSA_TENANT_URL=https://vsa.example.com/api/v1.0 \
  KASEYA_VSA_USERNAME=... \
  KASEYA_VSA_PASSWORD=... \
  npm start

Run as HTTP for testing:

bash

MCP_TRANSPORT=http npm start
curl http://localhost:8080/health

Docker

Terminal

docker build -t kaseya-vsa-mcp .
docker run --rm -p 8080:8080 \
  -e KASEYA_VSA_TENANT_URL=https://vsa.example.com/api/v1.0 \
  -e KASEYA_VSA_USERNAME=... \
  -e KASEYA_VSA_PASSWORD=... \
  kaseya-vsa-mcp

License

Apache-2.0

Read the full README →View source on GitHub →

Related MCP Servers

View all in Developer Tools View all alternatives

Reviews

No reviews yet — be the first to share how this listing worked for you.

Frequently Asked Questions about Kaseya VSA

Add the following block to your claude_desktop_config.json under mcpServers: "mcpServers": { "kaseya-vsa": { "command": "npx", "args": ["-y", "Kaseya VSA"] } }

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:

Live Dynamic SVG Preview

Markdown (GitHub README)

[![AllMCPs](https://allmcps.com/api/badge/kaseya-vsa?style=directory)](https://allmcps.com/mcp/kaseya-vsa)

HTML Embed

<a href="https://allmcps.com/mcp/kaseya-vsa"><img src="https://allmcps.com/api/badge/kaseya-vsa?style=directory" alt="Kaseya VSA on AllMCPs" /></a>

Technical Specs & Signals

CategoryDeveloper Tools

27Quality signal: Emerging · 27/100How this signal is calculated ▾

Server availabilityNot measured

Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.

Verified ownership8/20

Documentation & tools11/30

Adoption & activity1/15

Community engagement0/10

A guidance signal from public completeness & health data — not a user rating. New listings start lower and rise as they add docs, get verified, and grow adoption. Signals we can't observe for a listing are skipped, not counted against it.

★ Featured

AllMCPs Server

The official MCP server for AllMCPs.com - submit and manage tools directly from your AI. The open directory for MCP servers. Connect Claude, Cursor, Windsurf, and AI agents to databases, tools, files, and APIs. Explore 10,000+ servers. AllMCPs is the premier, open directory for discovering, evaluating, and installing Model Context Protocol (MCP) servers to equip AI agents and LLMs with real-world superpowers.

Explore Server →

Own this project?

This directory is pre-filled from public sources. Claim via GitHub README, site badge, or DNS TXT to unlock edit access and the Official badge and attach your website — proof is checked automatically, then reviewed by our team.

Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.

Claim & get free dofollow

Share & Embed

Add our SVG badge (dark/light directory styles) or embeddable widget to your site.

Explore more

More in 💻 Developer Tools →Best MCP servers for Developers →Alternatives to Kaseya VSA →Install in Claude Desktop Install in Cursor Install in VS Code

Documentation Overview

Kaseya VSA MCP Server

Tools

Tool	Description
`kaseya_vsa_list_agents`	List managed endpoints (agents). Optional `$filter`.
`kaseya_vsa_get_agent`	Get an agent's details by ID (renders as an interactive card in MCP Apps hosts).
`kaseya_vsa_get_software_inventory`	Installed software for an agent.
`kaseya_vsa_get_hardware_inventory`	Hardware audit for an agent.
`kaseya_vsa_get_patch_status`	Pending and installed patches for an agent.
`kaseya_vsa_deploy_patches_now`	Force a patch deploy on an agent (destructive — confirmation required).
`kaseya_vsa_list_procedures`	Agent procedures available to run.
`kaseya_vsa_run_procedure`	Execute a procedure on an agent (destructive — confirmation required).
`kaseya_vsa_list_alarms`	Open alarms (optional state filter; date-window elicitation if missing).
`kaseya_vsa_list_tickets`	Service Desk tickets (returns a friendly message if SD module isn't enabled).
`kaseya_vsa_list_organizations`	Tenant organizations.
`kaseya_vsa_list_machine_groups`	Machine group hierarchy.

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)

Configuration

Environment-variable mode (default)

Variable	Required	Description
`KASEYA_VSA_TENANT_URL`	yes	Full base URL incl. `/api/v1.0`
`KASEYA_VSA_USERNAME`	one of	Local-auth username
`KASEYA_VSA_PASSWORD`	one of	Local-auth password (secret)
`KASEYA_VSA_K1_TOKEN`	one of	Kaseya One SSO token (alternative to username + password)
`MCP_TRANSPORT`	no	`stdio` (default) or `http`
`MCP_HTTP_PORT`	no	HTTP listen port (default `8080`)
`AUTH_MODE`	no	`env` (default) or `gateway`

Either the username + password pair OR the KASEYA_VSA_K1_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

Terminal

npm install
npm run build
KASEYA_VSA_TENANT_URL=https://vsa.example.com/api/v1.0 \
  KASEYA_VSA_USERNAME=... \
  KASEYA_VSA_PASSWORD=... \
  npm start

Run as HTTP for testing:

bash

MCP_TRANSPORT=http npm start
curl http://localhost:8080/health

Docker

Terminal

docker build -t kaseya-vsa-mcp .
docker run --rm -p 8080:8080 \
  -e KASEYA_VSA_TENANT_URL=https://vsa.example.com/api/v1.0 \
  -e KASEYA_VSA_USERNAME=... \
  -e KASEYA_VSA_PASSWORD=... \
  kaseya-vsa-mcp

License

Apache-2.0