World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
MCP server for Kaseya VSA RMM — agents, patches, procedures, alarms, tickets.
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 0/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 12/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 12/100 |
Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Pick the AI app you use, then copy the settings.
Let your AI install it with one sentence
Please install Kaseya VSA. Follow https://mcp.popnx.com/i/wyre-technology-kaseya-vsa-mcp.md, show me the commands and wait for my OK before running them.Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads
Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 14, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
You need a Kaseya VSA key (create it on the maker’s site) · 1 setting(s) to fill in (KASEYA_VSA_TENANT_URL) · Install Docker on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Kaseya VSA for Claude on this computer, in this order: 1) Check Docker with docker --version. If it is missing, tell me to install it from https://www.docker.com/products/docker-desktop/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "kaseya-vsa": { "command": "docker", "args": [ "run", "-i", "--rm", "-e", "KASEYA_VSA_TENANT_URL", "-e", "KASEYA_VSA_PASSWORD", "-e", "KASEYA_VSA_K1_TOKEN", "-e", "AUTH_MODE", "ghcr.io/wyre-technology/kaseya-vsa-mcp:v1.1.4" ], "env": { "KASEYA_VSA_TENANT_URL": "your-value", "KASEYA_VSA_PASSWORD": "your-value", "KASEYA_VSA_K1_TOKEN": "your-value", "AUTH_MODE": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For KASEYA_VSA_PASSWORD, KASEYA_VSA_K1_TOKEN, AUTH_MODE, KASEYA_VSA_TENANT_URL, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Kaseya VSA tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
docker --versionMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Install Docker Desktop: on Mac open Docker.dmg and drag the icon to Applications (pick Apple silicon or Intel to match your Mac) · on Windows double-click Docker Desktop Installer.exe · then open the Docker Desktop app and leave it running. No curl command needed
Open the Docker download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: docker --version
Install once; it works for everything that needs Docker
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
These are program settings, not keys. No sign-up needed; fill them in as the maker describes.
KASEYA_VSA_TENANT_URL Full base URL including /api/v1.0 (e.g. https://vsa.example.com/api/v1.0)Descriptions are as written by the maker.
SettingsDeveloperEdit Config
{
"mcpServers": {
"kaseya-vsa": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"KASEYA_VSA_TENANT_URL",
"-e",
"KASEYA_VSA_PASSWORD",
"-e",
"KASEYA_VSA_K1_TOKEN",
"-e",
"AUTH_MODE",
"ghcr.io/wyre-technology/kaseya-vsa-mcp:v1.1.4"
],
"env": {
"KASEYA_VSA_TENANT_URL": "your-value",
"KASEYA_VSA_PASSWORD": "your-value",
"KASEYA_VSA_K1_TOKEN": "your-value",
"AUTH_MODE": "your-value"
}
}
}
}Paste the key only into the app’s field, never into a chat or to anyone
Use Kaseya VSA and tell me what you can do for me, then show me one thing✓ If Claude says it is using Kaseya VSA or shows a Kaseya VSA tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
KASEYA_VSA_USERNAME Local-auth username (omit if using Kaseya One token)MCP_TRANSPORT Transport mode for the server. Set to 'stdio' for local CLI use; the image defaults to 'http' for gateway hosting. · default stdioLOG_LEVEL Log verbosity: debug, info, warn, error · default infoDescriptions are as written by the maker.
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect Kaseya VSA yet
Kaseya VSA runs on your computer, but ChatGPT can only connect servers that run on the web
A · Use an app that can connect Kaseya VSA
B · Others in Other that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
Works with Claude Code, with some setup first
You need a Kaseya VSA key (create it on the maker’s site) · 1 setting(s) to fill in (KASEYA_VSA_TENANT_URL) · Install Docker on your computer first (one time)
Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Kaseya VSA for Claude Code on this computer, in this order: 1) Check Docker with docker --version. If it is missing, tell me to install it from https://www.docker.com/products/docker-desktop/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user kaseya-vsa --env KASEYA_VSA_TENANT_URL=your-value --env KASEYA_VSA_PASSWORD=your-value --env KASEYA_VSA_K1_TOKEN=your-value --env AUTH_MODE=your-value -- docker run -i --rm -e KASEYA_VSA_TENANT_URL -e KASEYA_VSA_PASSWORD -e KASEYA_VSA_K1_TOKEN -e AUTH_MODE ghcr.io/wyre-technology/kaseya-vsa-mcp:v1.1.4 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For KASEYA_VSA_PASSWORD, KASEYA_VSA_K1_TOKEN, AUTH_MODE, KASEYA_VSA_TENANT_URL, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Kaseya VSA tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
docker --versionMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Install Docker Desktop: on Mac open Docker.dmg and drag the icon to Applications (pick Apple silicon or Intel to match your Mac) · on Windows double-click Docker Desktop Installer.exe · then open the Docker Desktop app and leave it running. No curl command needed
Open the Docker download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: docker --version
Install once; it works for everything that needs Docker
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
These are program settings, not keys. No sign-up needed; fill them in as the maker describes.
KASEYA_VSA_TENANT_URL Full base URL including /api/v1.0 (e.g. https://vsa.example.com/api/v1.0)Descriptions are as written by the maker.
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --scope user kaseya-vsa --env KASEYA_VSA_TENANT_URL=your-value --env KASEYA_VSA_PASSWORD=your-value --env KASEYA_VSA_K1_TOKEN=your-value --env AUTH_MODE=your-value -- docker run -i --rm -e KASEYA_VSA_TENANT_URL -e KASEYA_VSA_PASSWORD -e KASEYA_VSA_K1_TOKEN -e AUTH_MODE ghcr.io/wyre-technology/kaseya-vsa-mcp:v1.1.4Replace “your-value” with your key before pressing Enter
Paste the key only into the app’s field, never into a chat or to anyone
You should see Kaseya VSA listed as connected
Use Kaseya VSA and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using Kaseya VSA or shows a Kaseya VSA tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
KASEYA_VSA_USERNAME Local-auth username (omit if using Kaseya One token)MCP_TRANSPORT Transport mode for the server. Set to 'stdio' for local CLI use; the image defaults to 'http' for gateway hosting. · default stdioLOG_LEVEL Log verbosity: debug, info, warn, error · default infoDescriptions are as written by the maker.
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor, with some setup first
You need a Kaseya VSA key (create it on the maker’s site) · 1 setting(s) to fill in (KASEYA_VSA_TENANT_URL) · Install Docker on your computer first (one time)
Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Kaseya VSA for Cursor on this computer, in this order: 1) Check Docker with docker --version. If it is missing, tell me to install it from https://www.docker.com/products/docker-desktop/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "kaseya-vsa": { "command": "docker", "args": [ "run", "-i", "--rm", "-e", "KASEYA_VSA_TENANT_URL", "-e", "KASEYA_VSA_PASSWORD", "-e", "KASEYA_VSA_K1_TOKEN", "-e", "AUTH_MODE", "ghcr.io/wyre-technology/kaseya-vsa-mcp:v1.1.4" ], "env": { "KASEYA_VSA_TENANT_URL": "your-value", "KASEYA_VSA_PASSWORD": "your-value", "KASEYA_VSA_K1_TOKEN": "your-value", "AUTH_MODE": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For KASEYA_VSA_PASSWORD, KASEYA_VSA_K1_TOKEN, AUTH_MODE, KASEYA_VSA_TENANT_URL, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Kaseya VSA tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
docker --versionMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Install Docker Desktop: on Mac open Docker.dmg and drag the icon to Applications (pick Apple silicon or Intel to match your Mac) · on Windows double-click Docker Desktop Installer.exe · then open the Docker Desktop app and leave it running. No curl command needed
Open the Docker download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: docker --version
Install once; it works for everything that needs Docker
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
These are program settings, not keys. No sign-up needed; fill them in as the maker describes.
KASEYA_VSA_TENANT_URL Full base URL including /api/v1.0 (e.g. https://vsa.example.com/api/v1.0)Descriptions are as written by the maker.
In the Kaseya VSA settings, KASEYA_VSA_PASSWORD, KASEYA_VSA_K1_TOKEN, AUTH_MODE, KASEYA_VSA_TENANT_URL is empty; add your key and save
Paste the key only into the app’s field, never into a chat or to anyone
Use Kaseya VSA and tell me what you can do for me, then show me one thing✓ If Cursor says it is using Kaseya VSA or shows a Kaseya VSA tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
KASEYA_VSA_USERNAME Local-auth username (omit if using Kaseya One token)MCP_TRANSPORT Transport mode for the server. Set to 'stdio' for local CLI use; the image defaults to 'http' for gateway hosting. · default stdioLOG_LEVEL Log verbosity: debug, info, warn, error · default infoDescriptions are as written by the maker.
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code, with some setup first
You need a Kaseya VSA key (create it on the maker’s site) · 1 setting(s) to fill in (KASEYA_VSA_TENANT_URL) · Install Docker on your computer first (one time)
Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Kaseya VSA for VS Code on this computer, in this order: 1) Check Docker with docker --version. If it is missing, tell me to install it from https://www.docker.com/products/docker-desktop/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "kaseya-vsa": { "type": "stdio", "command": "docker", "args": [ "run", "-i", "--rm", "-e", "KASEYA_VSA_TENANT_URL", "-e", "KASEYA_VSA_PASSWORD", "-e", "KASEYA_VSA_K1_TOKEN", "-e", "AUTH_MODE", "ghcr.io/wyre-technology/kaseya-vsa-mcp:v1.1.4" ], "env": { "KASEYA_VSA_TENANT_URL": "your-value", "KASEYA_VSA_PASSWORD": "your-value", "KASEYA_VSA_K1_TOKEN": "your-value", "AUTH_MODE": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For KASEYA_VSA_PASSWORD, KASEYA_VSA_K1_TOKEN, AUTH_MODE, KASEYA_VSA_TENANT_URL, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Kaseya VSA tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
docker --versionMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Install Docker Desktop: on Mac open Docker.dmg and drag the icon to Applications (pick Apple silicon or Intel to match your Mac) · on Windows double-click Docker Desktop Installer.exe · then open the Docker Desktop app and leave it running. No curl command needed
Open the Docker download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: docker --version
Install once; it works for everything that needs Docker
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
These are program settings, not keys. No sign-up needed; fill them in as the maker describes.
KASEYA_VSA_TENANT_URL Full base URL including /api/v1.0 (e.g. https://vsa.example.com/api/v1.0)Descriptions are as written by the maker.
In the Kaseya VSA settings, KASEYA_VSA_PASSWORD, KASEYA_VSA_K1_TOKEN, AUTH_MODE, KASEYA_VSA_TENANT_URL is empty; add your key and save
Paste the key only into the app’s field, never into a chat or to anyone
Use Kaseya VSA and tell me what you can do for me, then show me one thing✓ If VS Code says it is using Kaseya VSA or shows a Kaseya VSA tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
KASEYA_VSA_USERNAME Local-auth username (omit if using Kaseya One token)MCP_TRANSPORT Transport mode for the server. Set to 'stdio' for local CLI use; the image defaults to 'http' for gateway hosting. · default stdioLOG_LEVEL Log verbosity: debug, info, warn, error · default infoDescriptions are as written by the maker.
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.
JSON settings are under “For developers” below
Claude Code
claude mcp add --scope user kaseya-vsa --env KASEYA_VSA_TENANT_URL=your-value --env KASEYA_VSA_PASSWORD=your-value --env KASEYA_VSA_K1_TOKEN=your-value --env AUTH_MODE=your-value -- docker run -i --rm -e KASEYA_VSA_TENANT_URL -e KASEYA_VSA_PASSWORD -e KASEYA_VSA_K1_TOKEN -e AUTH_MODE ghcr.io/wyre-technology/kaseya-vsa-mcp:v1.1.4Claude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"kaseya-vsa": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"KASEYA_VSA_TENANT_URL",
"-e",
"KASEYA_VSA_PASSWORD",
"-e",
"KASEYA_VSA_K1_TOKEN",
"-e",
"AUTH_MODE",
"ghcr.io/wyre-technology/kaseya-vsa-mcp:v1.1.4"
],
"env": {
"KASEYA_VSA_TENANT_URL": "your-value",
"KASEYA_VSA_PASSWORD": "your-value",
"KASEYA_VSA_K1_TOKEN": "your-value",
"AUTH_MODE": "your-value"
}
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"kaseya-vsa": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"KASEYA_VSA_TENANT_URL",
"-e",
"KASEYA_VSA_PASSWORD",
"-e",
"KASEYA_VSA_K1_TOKEN",
"-e",
"AUTH_MODE",
"ghcr.io/wyre-technology/kaseya-vsa-mcp:v1.1.4"
],
"env": {
"KASEYA_VSA_TENANT_URL": "your-value",
"KASEYA_VSA_PASSWORD": "your-value",
"KASEYA_VSA_K1_TOKEN": "your-value",
"AUTH_MODE": "your-value"
}
}
}
}VS Code (mcp.json)
{
"servers": {
"kaseya-vsa": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"KASEYA_VSA_TENANT_URL",
"-e",
"KASEYA_VSA_PASSWORD",
"-e",
"KASEYA_VSA_K1_TOKEN",
"-e",
"AUTH_MODE",
"ghcr.io/wyre-technology/kaseya-vsa-mcp:v1.1.4"
],
"env": {
"KASEYA_VSA_TENANT_URL": "your-value",
"KASEYA_VSA_PASSWORD": "your-value",
"KASEYA_VSA_K1_TOKEN": "your-value",
"AUTH_MODE": "your-value"
}
}
}
}KASEYA_VSA_TENANT_URL required envKASEYA_VSA_USERNAME envKASEYA_VSA_PASSWORD secret required envKASEYA_VSA_K1_TOKEN secret required envMCP_TRANSPORT envAUTH_MODE secret required envLOG_LEVEL envDescriptions are as written by the maker.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026
The registry name was verified with the GitHub account WYRE-AI, which owns the repo
Code last changed 3 days ago
Uses Apache-2.0
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Not checked: only npm and PyPI packages with a version can be checked
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/wyre-technology-kaseya-vsa-mcp)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: KASEYA_VSA_PASSWORD, KASEYA_VSA_K1_TOKEN, AUTH_MODE
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed 3 days ago, and the latest version (1.1.4) reached the registry 3 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Docker on your computer.
In the same category: World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Manage monitors, status pages, incidents and maintenances in your openstatus workspace.
Validate oh-my-posh configurations and segment snippets against the official schema.
MCP server for progressive tool usage at any scale (see https://klavis.ai)
Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.
| This one Kaseya VSA | World Monitor | openstatus | Oh My Posh Validator | Strata | Jitsu | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install |
| Needs a key | Yes | No | No | No | No | No |
| Add with + in Claude | No | No | No | No | No | No |
| Basic checks | 3/3 | 4/4 | 4/4 | 4/4 | 1/4 | 4/4 |
| License | Apache-2.0 | AGPL-3.0 | AGPL-3.0 | MIT | Apache-2.0 | MIT |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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.
| 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.
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.
Copy .env.example and set the variables below.
| Variable | Required | Description |
|---|---|---|
KASEYA_VSA_TENANT_URL | For stdio and AUTH_MODE=env | Full base URL incl. /api/v1.0. The Compose gateway service does not load this. |
KASEYA_VSA_USERNAME | For stdio and AUTH_MODE=env | Local-auth username (with password). The Compose gateway service does not load this. |
KASEYA_VSA_PASSWORD | For stdio and AUTH_MODE=env | Local-auth password (secret). The Compose gateway service does not load this. |
KASEYA_VSA_K1_TOKEN | For stdio and AUTH_MODE=env | Kaseya One SSO token (alternative to username + password). The Compose gateway service does not load this. |
MCP_TRANSPORT | No | stdio (default) or http |
AUTH_MODE | No | gateway (Docker image and Compose default) or env (code default when unset). Gateway mode requires the X-Kaseya-VSA-* headers on each /mcp request and never falls back to KASEYA_VSA_*. env uses those variables only after S2S auth succeeds. |
CONDUIT_S2S_SECRET | Yes for HTTP | Service-to-service secret. Generate with openssl rand -hex 32. The HTTP server logs an error and exits non-zero when this is empty or a known placeholder (changeme, your-s2s-secret, secret, placeholder, an unresolved ${...} value, and similar public examples). Compose will not start without it. Never commit a real value. The value is never logged. |
MCP_ALLOW_INSECURE_DEV | No | Set to exactly 1 only for local development to start HTTP without CONDUIT_S2S_SECRET. The process logs a warning, does not enforce X-Gateway-S2S, and forces the listener onto 127.0.0.1 even if MCP_HTTP_HOST is a wider address. A known placeholder secret is still refused. |
MCP_HTTP_HOST | No | Bind address when MCP_TRANSPORT=http. Defaults to 127.0.0.1 when unset. A configured CONDUIT_S2S_SECRET honors this value. The container image sets 0.0.0.0. |
MCP_HTTP_PORT | No | HTTP port. Defaults to 8080. |
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.
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= ,v1= , where the hex is HMAC-SHA256 of the literal string t= 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.
npm install
npm run build KASEYA_VSA_TENANT_URL=https://vsa.example.com/api/v1.0 \ KASEYA_VSA_USERNAME=... \ KASEYA_VSA_PASSWORD=... \ npm start
HTTP refuses to start until CONDUIT_S2S_SECRET is set:
CONDUIT_S2S_SECRET="$CONDUIT_S2S_SECRET" MCP_TRANSPORT=http npm start
curl http://127.0.0.1:8080/health
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:
MCP_TRANSPORT=http MCP_ALLOW_INSECURE_DEV=1 npm start
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.
docker build -t kaseya-vsa-mcp .
docker run --rm \ -e CONDUIT_S2S_SECRET="$CONDUIT_S2S_SECRET" \ -p 127.0.0.1:8080:8080 \ kaseya-vsa-mcp
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:
CONDUIT_S2S_SECRET="$CONDUIT_S2S_SECRET" docker compose up
Single-tenant HTTP (AUTH_MODE=env) still requires the S2S secret, then uses KASEYA_VSA_*:
docker run --rm \
-e CONDUIT_S2S_SECRET="$CONDUIT_S2S_SECRET" \ -e AUTH_MODE=env \ -e KASEYA_VSA_TENANT_URL=https://vsa.example.com/api/v1.0 \ -e KASEYA_VSA_USERNAME=... \ -e KASEYA_VSA_PASSWORD=... \ -p 127.0.0.1:8080:8080 \ kaseya-vsa-mcp
Apache-2.0