Mirobody
by thetahealth
Lab results to LOINC codes and UCUM units, symptoms and diagnoses to ICPC-3. Offline, no API key.
Runs on your computer★ 1,408Apache-2.0Updated today
Install
Kaseya VSA 10 MCP
Overview
Description from the maker (original English)
Kaseya VSA 10 API, plus a local fleet mirror for patch, health and software questions across clients
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs on your computer
- Transport: stdio
- Category: Clinics & health
- You need to fill in: KASEYA_VSA_SERVER, KASEYA_VSA_TOKEN_ID, KASEYA_VSA_TOKEN_SECRET, KASEYA_VSA_MCP_HTTP_TOKEN, PRINTING_PRESS_CLIENT_PROFILE
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on your computer with your user’s permissions (files, network, apps).
- You fill in yourself:
KASEYA_VSA_SERVER,KASEYA_VSA_TOKEN_ID,KASEYA_VSA_TOKEN_SECRET,KASEYA_VSA_MCP_READ_ONLY,KASEYA_VSA_NO_LOCAL_DATA,KASEYA_VSA_MCP_HTTP_TOKEN,KASEYA_VSA_BASE_URL,KASEYA_VSA_USER_AGENT,PRINTING_PRESS_CLIENT_PROFILE
Values marked secret are keys to your account. Never share them or paste them into a chat.
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Download the maker’s .mcpb file
The link goes to the maker’s own file; we do not host or repackage it. Open the file and Claude Desktop installs it.
Run this in your terminal
Fill in the empty values before running it.
Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
Values you fill in
- Your VSA 10 instance host name, for example yourcompany.vsax.net (no https://).
- VSA 10 API token ID (Administration > Configuration > API Access).
- VSA 10 API token secret, shown once when the token is created.
KASEYA_VSA_MCP_READ_ONLYenvOptional. Set to exactly 1 to expose only read-only tools and refuse any state-changing execute call.KASEYA_VSA_NO_LOCAL_DATAenvOptional. Set to 1 to keep no local copy of API responses: reads go to the API and the response cache is off.- Required only when running the MCP server with --transport http. Not needed for the default local stdio transport.
KASEYA_VSA_BASE_URLenvOptional. The full VSA 10 API base URL, https:// /api/v3, instead of KASEYA_VSA_SERVER. Leave blank to build it from KASEYA_VSA_SERVER.KASEYA_VSA_USER_AGENTenvOptional. Overrides the User-Agent the CLI sends on VSA 10 requests. Leave blank to use the CLI's own built-in User-Agent.- Optional: binds the MCP server to an existing tenant-gated Printing Press client profile. Leave unset for a single-tenant install.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
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 7, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account servosity, which owns the repo
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Compared with others in Clinics & healthi
- More stars than 0% of the other 1021 servers in this category
- Published to the registry more recently than 96% of the other 1021 servers in this category
- Basic checks equal to or better than 100% of the other 1021 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Kaseya VSA 10 MCP safe?
It passed 1 of 1 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.
What keys or codes does it need?
You need to fill in: KASEYA_VSA_SERVER, KASEYA_VSA_TOKEN_ID, KASEYA_VSA_TOKEN_SECRET, KASEYA_VSA_MCP_HTTP_TOKEN, PRINTING_PRESS_CLIENT_PROFILE
Does it run on my computer or in the cloud?
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).
Is it still maintained?
The GitHub repo last changed –, and the latest version (0.1.2) reached the registry yesterday.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need MCPB on your computer.
What can I use instead?
In the same category: Mirobody, FHIR MCP Server, Google Health MCP
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
FHIR MCP Server
by wso2
MCP server providing seamless access to FHIR APIs for AI tools and healthcare applications
Runs on your computer★ 137Apache-2.0Updated 9 days ago
Install
Google Health MCP
by davidmosiah
Privacy-first unofficial Google Health API v4 MCP server for health, sleep, activity, HR agents
Runs on your computer★ 79MITUpdated 4 months ago
Install
README from the maker
Open the README
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.
Kaseya VSA 10 + AI - for ChatGPT, Claude, GitHub Copilot, Microsoft 365 Copilot, Gemini, and any agent that speaks MCP
Unofficial. Community-built Claude Code Skill and MCP server for the Kaseya VSA
API. Not affiliated with, endorsed by, or sponsored by Kaseya US LLC.
▶ Watch the 30-second demo - demo data is simulated; every command shown exists in the real CLI.
Every Kaseya VSA 10 API endpoint (the platform formerly called VSA X), plus a local fleet database that answers patch, health, and software questions across all your clients offline. Works with the AI you already use - ChatGPT (Plus/Pro+), Claude Desktop, Codex, Claude Code, Claude Cowork, and GitHub Copilot - plus Microsoft 365 Copilot / Copilot Studio and Google Gemini via the remote path. Free, open source, runs on your laptop. Built for MSP owners. No code required.
Works with your agent
The six agents MSP owners actually use (self-serve, works today):
| Your AI agent | How to install the Kaseya VSA skill |
|---|---|
| Claude Desktop | Run installer, then Settings > Extensions to register kaseya-vsa-mcp (no JSON editing). |
| ChatGPT (paid plans) | Run installer, host kaseya-vsa-mcp over HTTPS with KASEYA_VSA_MCP_HTTP_TOKEN set, then register it as a Developer Mode connector if your connector settings can send the bearer token. |
| Codex CLI | Paste the install prompt below. |
| Claude Code | Paste the install prompt below. |
| Claude Cowork | Paste the install prompt below. |
| GitHub Copilot (VS Code) | Run installer, add kaseya-vsa-mcp to mcp.json under the servers key, then pick Agent mode. |
For ChatGPT, run kaseya-vsa-mcp --transport http with KASEYA_VSA_MCP_HTTP_TOKEN set, on an HTTPS host; every request sends that token. See mcp-install.md.
Also for the Microsoft and Google stacks
Big install base, but an honest heads-up: these are the remote / enterprise path, not the local binary you just installed.
| Agent | What it takes |
|---|---|
| Microsoft 365 Copilot / Copilot Studio | Not self-serve. Host kaseya-vsa-mcp over HTTPS with KASEYA_VSA_MCP_HTTP_TOKEN set, then wire it into Copilot Studio (Tools > Add a tool > Model Context Protocol > Server URL) or a declarative agent, if it can send the bearer token. Needs a Copilot Studio license + tenant admin. See mcp-install.md. |
| Google Gemini | Gemini CLI is local - same as Claude Code. The Gemini app is remote - same HTTPS path as ChatGPT. See mcp-install.md. |
Skill-native agents (also covered): Hermes and OpenClaw read this skill's
SKILL.mddirectly *and* speak MCP - see their install sections below. Also works with Cursor, Windsurf, Cline, Continue.dev, and Zed via MCP. Full per-tool wire-up: [docs/which-agent.md](../../docs/which-agent.md).
Run more than one agent? Install across all 51+ supported agents in one command:
npx skills add Servosity/msp-skills@latest(requires Node.js, then run the per-skill installer for the CLI/MCP binaries). See docs/which-agent.md.
Install in 60 seconds
Fastest for Claude Desktop - one-click .mcpb
Download Kaseya VSA MCP (.mcpb) - then open Claude Desktop > Settings > Extensions and select the file. One click, no JSON, no shell. (Browse every Kaseya VSA release on the releases page.)
Prefer the Claude Code plugin? Add the marketplace once, then install - works immediately, no directory listing required:
/plugin marketplace add Servosity/msp-skills/plugin install kaseya-vsa@msp-skills
Path A - paste one prompt into your AI agent (recommended)
Copy this into Claude Code, Codex CLI, or Claude Cowork:
Install the Kaseya VSA Skill and MCP server from Servosity/msp-skills in this agent workspace. If this workspace uses a POSIX shell (macOS, Linux, WSL, or Bash), run
bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/kaseya-vsa/install.sh). If it uses Windows PowerShell, runiwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/kaseya-vsa/install.ps1 | iex. Then authenticate per the README and runkaseya-vsa-cli --helpto explore.
The same prompt works in any agent that can run shell.
Path B - run the installer yourself
Windows (PowerShell):
iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/kaseya-vsa/install.ps1 | iexmacOS / Linux:
bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/kaseya-vsa/install.sh)The installer drops both kaseya-vsa-cli (the CLI) and kaseya-vsa-mcp (the MCP server) into your user bin path. Claude Code, Codex, and Cowork discover the Skill via SKILL.md in this directory.
Verify:
kaseya-vsa-cli --versionUpgrade to the latest version
The installer always fetches the current release - re-run it to upgrade:
macOS / Linux:
bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/kaseya-vsa/install.sh)Windows (PowerShell):
iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/kaseya-vsa/install.ps1 | iexClaude Desktop .mcpb users: download the latest .mcpb (top of this section) and re-select it in Settings > Extensions. Claude Code plugin users: /plugin update kaseya-vsa@msp-skills.
Add to Claude Desktop, GitHub Copilot, Gemini CLI, Microsoft 365 Copilot, or another MCP client
After the installer runs, see [mcp-install.md](./mcp-install.md) and [docs/which-agent.md](../../docs/which-agent.md) for the per-agent wire-up - one section per agent, including the GitHub Copilot servers key and the remote Microsoft 365 Copilot / Copilot Studio path. Claude Desktop's Settings > Extensions panel is the simplest path; the MCP config block (for users who prefer editing JSON) is documented in mcp-install.md.
Install for Hermes
From the Hermes CLI:
hermes skills install servosity/msp-skills/skills/kaseya-vsa --forceInside a Hermes chat session:
/skills install servosity/msp-skills/skills/kaseya-vsa --forceHermes speaks MCP natively, so it can also use the kaseya-vsa-mcp server directly - same install path, same env vars.
Install for OpenClaw
Tell your OpenClaw agent (copy this):
Install the kaseya-vsa skill from https://github.com/servosity/msp-skills/tree/main/skills/kaseya-vsa. The skill defines how its required CLI (
kaseya-vsa-cli) can be installed via theopenclaw:frontmatter block.
OpenClaw isn't generally available yet; the frontmatter wiring is pre-shipped and will activate the moment OpenClaw launches.
Authenticate
Create an API token in the VSA 10 console under Administration > Configuration > API Access, then set your instance host and the token ID and secret:
macOS / Linux:
export KASEYA_VSA_SERVER=yourcompany.vsax.netexport KASEYA_VSA_TOKEN_ID= export KASEYA_VSA_TOKEN_SECRET= kaseya-vsa-cli doctor
Windows (PowerShell):
$env:KASEYA_VSA_SERVER = "yourcompany.vsax.net"$env:KASEYA_VSA_TOKEN_ID = " " $env:KASEYA_VSA_TOKEN_SECRET = " " kaseya-vsa-cli doctor
KASEYA_VSA_SERVER is the host name only, without https://. The CLI sends the token only to that host and refuses redirects to any other. A server outside vsax.net needs KASEYA_VSA_BASE_URL=https:// /api/v3 instead.
doctor checks config and paths, then sends one read request (GET /assets) with your token to the configured server and reports whether the credential was accepted, rejected, or pointed at the wrong base URL. While the server still resolves to the shipped placeholder (yourcompany.vsax.net), it sends nothing and names the variable to set.
What this skill does
| Question your MSP keeps asking | Command |
|---|---|
| Which pending OS updates are exposed on the most devices, across every client? | kaseya-vsa-cli patch-exposure --by kb --severity critical,important --agent |
| Which clients carry the most critical patch exposure? | kaseya-vsa-cli patch-exposure --by org --severity critical --agent |
| Which devices are offline, without working antivirus, or with the firewall off? | kaseya-vsa-cli health --check offline,av,firewall --offline-for 72h --agent |
| Which versions of Google Chrome are installed, and on how many devices? | kaseya-vsa-cli software "Google Chrome" --versions --agent |
| Which devices with software inventory are missing our security agent? | kaseya-vsa-cli software "Huntress Agent" --absent --agent |
| Who did what in the tenant this week? | kaseya-vsa-cli audit-logs digest --since 7d --agent |
| What is going on with this one device right now? | kaseya-vsa-cli devices brief FRONTDESK-01 --agent |
| Run a script on a device and give me the output | kaseya-vsa-cli scripts run-wait --device FRONTDESK-01 --agent |
patch-exposure, health, software and audit-logs digest read the local mirror: run kaseya-vsa-cli sync first (an empty mirror answers with scanned_devices: 0). devices brief and scripts run-wait call the live API.
Full command reference: guide.md. For the AI-agent operating contract (--agent, --dry-run, when to confirm before mutating), see AGENTS.md.
What makes this different
Most Kaseya VSA integrations and MCP servers proxy each question into a live API call. That's fine for one record. It dies at scale, when you're asking which of 1,200 devices across 40 clients are still missing this month's cumulative update.
This skill syncs Kaseya VSA into a local SQLite mirror with full-text search. Aggregate questions become one local SQL join: instant, offline, and the AI sees the answer, not the raw data. Compound commands like patch-exposure, health and software join devices, their asset inventory, sites and organizations - work a stateless API wrapper can't do. scripts run-wait and tasks run-wait start an automation, wait for it to finish, and return each device's exit code and output in one call.
The pain this closes
Kaseya's own release note for VSA 10 patch status reports says reporting "is currently limited to one policy at a time" (Advanced reporting: Patch status reports, February 2026). An MSP that wants one answer to "what is missing, where" builds a report per policy and joins the exports by hand. The same is true of offline agents, disabled antivirus and full disks: the console shows them one organization or one device at a time.
patch-exposure --by kbranks every missing update by how many devices lack it, with CVSS and days since release.patch-exposure --by orgshows which clients carry the most exposure, for the QBR.healthlists every device failing an offline, antivirus, firewall, UAC, disk, CPU or memory check, with counts.software --versionsandsoftware --absentshow version drift and devices missing an
Only the beginning is shown; read the rest in the repo