Kaseya VSA MCP Server

An MCP server for the Kaseya VSA REST API (v1.0), the RMM MSPs use to manage endpoints. It lets an AI agent read agents (managed endpoints), their software and hardware audit, patch status, agent procedures, alarms, tickets, organizations and machine groups and, on explicit request with confirmation, deploy patches or run an agent procedure on an endpoint.

• Transport: MCP Streamable HTTP at POST /mcp, health probe at GET /health

• Stateless and multi-tenant: credentials arrive on every request as HTTP headers and are never stored; every tool is listed from the first tools/list

• Python 3.12, uv, FastMCP, httpx

• License: Apache-2.0, Copyright 2026 MSPbots.ai

Authentication headers

Where to get them: create a dedicated VSA user for the integration and a personal access token for it, and give the user only the scopes the agent needs.

How they are used: the server signs in with GET {url}/api/v1.0/auth using HTTP Basic username:token and uses the returned session token as Authorization: Bearer (servers that only accept the older hashed sign-in header are tried with that form as well). A Kaseya One token is exchanged at /api/v1.0/auth/sso. Session tokens are cached in memory, keyed by a SHA-256 of the full credential set, until shortly before they expire, and renewed once when VSA answers 401. When both a login and a Kaseya One token are sent, the login is used.

A request to /mcp without the URL, or without either credential form, gets HTTP 401 naming what is missing; a non-https URL gets HTTP 400.

Related MCP server: Auvik MCP Server

Tools

All tools return a JSON string. Lists take an OData filter, top (up to 500, read 100 per request) and skip, and return {count, total, has_more, next_skip}. confirm marks tools that change the endpoint and need confirm: true.

Errors come back as a JSON envelope instead of an exception:

{"error": {"code": "unauthorized", "message": "Kaseya VSA rejected the user name and password / access token", "retryable": false}}

code is one of not_configured, unauthorized, not_found, invalid_argument, rate_limited, upstream_error. Reads are retried with backoff on 429, 5xx and network errors; writes only on 429.

Run locally

uv sync
uv run python -m kaseya_vsa_mcp          # listens on 0.0.0.0:8080

or with Docker:

docker build --platform linux/amd64 -t kaseya-vsa-mcp:dev .
docker run --rm -p 8080:8080 kaseya-vsa-mcp:dev

Configuration (environment variables, all optional): MCP_HTTP_HOST (default 0.0.0.0), MCP_HTTP_PORT (default 8080), LOG_LEVEL (default INFO). Credentials are never read from the environment.

Testing example

# list tools
curl -s http://localhost:8080/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "X-Kaseya-VSA-Tenant-Url: https://vsa.example.com" \
  -H "X-Kaseya-VSA-Username: api-user" \
  -H "X-Kaseya-VSA-Password: your-access-token" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'

# open alarms
curl -s http://localhost:8080/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "X-Kaseya-VSA-Tenant-Url: https://vsa.example.com" \
  -H "X-Kaseya-VSA-Username: api-user" \
  -H "X-Kaseya-VSA-Password: your-access-token" \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"kaseya_vsa_list_alarms","arguments":{"top":20}}}'

Unit tests (no network access needed):

uv run pytest

Delivery notes

• Tool count (12). Kept as is because the tool names are an existing contract; every earlier parameter is still accepted.

• Routes follow the VSA REST API as implemented by Kaseya's own VSAModule PowerShell module. Older versions called routes that do not exist; now: software /assetmgmt/audit/{id}/software/... (installed applications by default), hardware /assetmgmt/audit/{id}/summary plus /hardware/diskvolumes|pcianddisk|printers, patch status /assetmgmt/patch/{id}/status plus the missing patches, deploy PUT /assetmgmt/patch/runnow, procedures /automation/agentprocs and PUT /automation/agentprocs/{agent}/{procedure}/runnow, alarms /assetmgmt/alarms/{false|true} and tickets /automation/tickets (or /automation/servicedesks/{id}/tickets).

• Sign-in. Plain Basic username:token is tried first, then the older hashed header that earlier versions used exclusively.

• Confirmation for endpoint actions. Deploying patches and running procedures take confirm: true (older versions asked through an interactive prompt the gateway cannot relay). Agent procedures must be approved in VSA before they can run.

• Lists are no longer narrowed by an interactive prompt when no filter is given; top above 100 is read in pages of 100.

• Not included: the device "card" UI resource of older versions (an MCP Apps HTML view); the tools return the same data as JSON.

License

Apache License 2.0 - see LICENSE and NOTICE.