Skip to main content
ClaudeWave

MCP server for Kaseya VSA — endpoints, patches, procedures, alarms, tickets

MCP ServersOfficial Registry0 stars0 forksTypeScriptApache-2.0Updated today
ClaudeWave Trust Score
87/100
Trusted
Passed
  • Open-source license (Apache-2.0)
  • Actively maintained (<30d)
  • Clear description
  • Topics declared
Last scanned: 6/11/2026
Install in Claude Code / Claude Desktop
Method: Manual
Claude Code CLI
git clone https://github.com/wyre-technology/kaseya-vsa-mcp
claude_desktop_config.json (Claude Desktop)
{
  "mcpServers": {
    "kaseya-vsa-mcp": {
      "command": "node",
      "args": ["/path/to/kaseya-vsa-mcp/dist/index.js"],
      "env": {
        "KASEYA_VSA_TENANT_URL": "<kaseya_vsa_tenant_url>",
        "KASEYA_VSA_USERNAME": "<kaseya_vsa_username>",
        "KASEYA_VSA_PASSWORD": "<kaseya_vsa_password>"
      }
    }
  }
}
1. Run the command above in your terminal (Claude Code), or paste the JSON config into claude_desktop_config.json (Claude Desktop).
2. Replace any <placeholder> values with your API keys or paths.
3. Restart Claude. The MCP server and its tools appear automatically.
💡 Clone https://github.com/wyre-technology/kaseya-vsa-mcp and follow its README for install instructions.
Detected environment variables
KASEYA_VSA_TENANT_URLKASEYA_VSA_USERNAMEKASEYA_VSA_PASSWORD
Use cases

MCP Servers overview

# Kaseya VSA MCP Server

[![Release](https://github.com/wyre-technology/kaseya-vsa-mcp/actions/workflows/release.yml/badge.svg)](https://github.com/wyre-technology/kaseya-vsa-mcp/actions/workflows/release.yml)
[![License: Apache 2.0](https://img.shields.io/badge/License-Apache_2.0-blue.svg)](https://opensource.org/licenses/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

| 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

```bash
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

```bash
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
claudekaseyamcpmodel-context-protocolmsprmmvsa

What people ask about kaseya-vsa-mcp

What is wyre-technology/kaseya-vsa-mcp?

+

wyre-technology/kaseya-vsa-mcp is mcp servers for the Claude AI ecosystem. MCP server for Kaseya VSA — endpoints, patches, procedures, alarms, tickets It has 0 GitHub stars and was last updated today.

How do I install kaseya-vsa-mcp?

+

You can install kaseya-vsa-mcp by cloning the repository (https://github.com/wyre-technology/kaseya-vsa-mcp) or following the README instructions on GitHub. ClaudeWave also provides quick install blocks on this page.

Is wyre-technology/kaseya-vsa-mcp safe to use?

+

Our security agent has analyzed wyre-technology/kaseya-vsa-mcp and assigned a Trust Score of 87/100 (tier: Trusted). See the full breakdown of passed checks and flags on this page.

Who maintains wyre-technology/kaseya-vsa-mcp?

+

wyre-technology/kaseya-vsa-mcp is maintained by wyre-technology. The last recorded GitHub activity is from today, with 3 open issues.

Are there alternatives to kaseya-vsa-mcp?

+

Yes. On ClaudeWave you can browse similar mcp servers at /categories/mcp, sorted by popularity or recent activity.

Deploy kaseya-vsa-mcp to your cloud

Ship this repo to production in minutes. Each platform spins up its own environment with editable env vars.

Maintain this repo? Add a badge to your README

Drop the badge into your GitHub README to show it's tracked on ClaudeWave. Each badge links back to this page and reflects the live Trust Score.

Featured on ClaudeWave: wyre-technology/kaseya-vsa-mcp
[![Featured on ClaudeWave](https://claudewave.com/api/badge/wyre-technology-kaseya-vsa-mcp)](https://claudewave.com/repo/wyre-technology-kaseya-vsa-mcp)
<a href="https://claudewave.com/repo/wyre-technology-kaseya-vsa-mcp"><img src="https://claudewave.com/api/badge/wyre-technology-kaseya-vsa-mcp" alt="Featured on ClaudeWave: wyre-technology/kaseya-vsa-mcp" width="320" height="64" /></a>

More MCP Servers

kaseya-vsa-mcp alternatives