Mirobody
Lab results to LOINC codes and UCUM units, symptoms and diagnoses to ICPC-3. Offline, no API key.
Beschreibung vom Entwickler (englisches Original)
Every ESET Connect endpoint, plus per-customer health, exposure and QBR reports from a local mirror
Diese drei werden nie zu einer Punktzahl zusammengefasst: Meinungen, Messungen und Beliebtheit sind verschiedene Dinge.
Für diesen Server haben wir noch keine Zusammenfassung in einfacher Sprache geschrieben. Unten stehen die Fakten, die wir aus der Registry gelesen haben.
Wähle die KI-App, die du nutzt, und kopiere die Einstellungen.
ESET_PROTECT_USERNAME, ESET_PROTECT_PASSWORD, ESET_PROTECT_REGION, ESET_PROTECT_TOKEN, ESET_PROTECT_BASE_URL, ESET_PROTECT_USER_AGENT, ESET_PROTECT_MCP_READ_ONLY, ESET_PROTECT_NO_LOCAL_DATA, ESET_PROTECT_MCP_HTTP_TOKEN, PRINTING_PRESS_CLIENT_PROFILEAls geheim markierte Werte sind Schlüssel zu deinem Konto. Gib sie nie weiter und füge sie nie in einen Chat ein.
Welche App nutzt du?
Wähle oben deine App. Wir merken sie uns, damit der Button beim nächsten Mal „In … installieren“ anzeigt.
Die .mcpb-Datei des Entwicklers herunterladen
Der Link führt zur Datei des Entwicklers selbst; wir hosten sie nicht und verpacken sie nicht neu. Öffne die Datei, dann installiert Claude Desktop sie.
Führe das in deinem Terminal aus
Trag die leeren Werte ein, bevor du ihn startest.
Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
Dieser Server läuft auf deinem Computer, und ChatGPT kann sich nur mit Servern im Internet verbinden. Wähle eine andere App.
Deine Auswahl bleibt in einem Cookie auf diesem Gerät; kein Konto nötig.
ESET_PROTECT_REGION envESET_PROTECT_BASE_URL envESET_PROTECT_USER_AGENT envESET_PROTECT_MCP_READ_ONLY envESET_PROTECT_NO_LOCAL_DATA envPRINTING_PRESS_CLIENT_PROFILE envDiese Einstellungen werden aus dem Registry-Eintrag des Entwicklers erzeugt. Wenn in der README etwas anderes steht, folge der README.
Läuft auf deinem Computer; die Tool-Liste erscheint nach der Installation in deiner KI-App.
Wir prüfen Informationen, die jeder sehen kann; den Code haben wir nicht gelesen. Checks, die nicht zutreffen, werden nicht mitgezählt. · Geprüft am 8. Nov. 2026
Der Registry-Name wurde mit dem GitHub-Konto servosity bestätigt, dem das Repo gehört
Dieses Repo haben wir noch nicht von GitHub gelesen
Dieses Repo haben wir noch nicht von GitHub gelesen
Dieser Server läuft auf deinem Computer; es gibt keinen Endpunkt im Internet
Läuft auf deinem Computer und nutzt stattdessen lokale Einstellungen
Läuft auf deinem Computer; Tool-Listen können wir nur von Endpunkten im Internet lesen
Verglichen mit allen aktiven Servern dieser Kategorie in der Registry. Sterne zählen nur, wenn dem Herausgeber das Repo gehört.
Er hat 1 von 1 zutreffenden Basischecks bestanden. Den Code haben wir nicht gelesen. Bevor du einen Schlüssel oder Token hinzufügst, sieh nach, welche Zugriffe der Server verlangt, und nutze einen Schlüssel, der nur die Berechtigungen hat, die du brauchst.
Das musst du eintragen: ESET_PROTECT_USERNAME, ESET_PROTECT_PASSWORD, ESET_PROTECT_TOKEN, ESET_PROTECT_MCP_HTTP_TOKEN
Er läuft auf deinem Computer. Deine KI-App startet ihn bei Bedarf, und die Daten laufen nicht über die Server des Entwicklers (außer der Server ruft selbst einen Onlinedienst auf).
Das GitHub-Repo wurde zuletzt – geändert, und die neueste Version (0.1.0) kam heute in die Registry.
Apps, die MCP unterstützen, etwa Claude Desktop, Claude Code, Cursor und VS Code. Außerdem brauchst du MCPB auf deinem Computer.
In derselben Kategorie: Mirobody, FHIR MCP Server, Google Health MCP
Server derselben Kategorie von anderen Entwicklern, sortiert nach Sternen.
So liest du eine Karte:★ GitHub-SterneiDrei Säulen: Bewertungen · Checks · NutzungiAktualisiert = neueste Version in der Registry veröffentlichti
Lab results to LOINC codes and UCUM units, symptoms and diagnoses to ICPC-3. Offline, no API key.
MCP server providing seamless access to FHIR APIs for AI tools and healthcare applications
Privacy-first unofficial Google Health API v4 MCP server for health, sleep, activity, HR agents
Unverändert aus dem Repo des Entwicklers übernommen. PopNx MCP hat den Inhalt weder geprüft noch empfiehlt es ihn. HTML, Bilder und Skripte wurden entfernt. Links führen von dieser Website weg.
Unofficial. Community-built Claude Code Skill and MCP server for the ESET
API. Not affiliated with, endorsed by, or sponsored by ESET, spol. s r.o.
▶ Watch the 30-second demo - demo data is simulated; every command shown exists in the real CLI.
Every ESET Connect endpoint in one binary, plus per-customer health, exposure and QBR reports built from a local mirror of your MSP tree. 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.
The six agents MSP owners actually use (self-serve, works today):
| Your AI agent | How to install the ESET skill |
|---|---|
| Claude Desktop | Run installer, then Settings > Extensions to register eset-protect-mcp (no JSON editing). |
| ChatGPT (paid plans) | Run installer, host eset-protect-mcp over HTTPS with ESET_PROTECT_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 eset-protect-mcp to mcp.json under the servers key, then pick Agent mode. |
For ChatGPT, run eset-protect-mcp --transport http with ESET_PROTECT_MCP_HTTP_TOKEN set, on an HTTPS host; every request sends that token. See mcp-install.md.
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 eset-protect-mcp over HTTPS with ESET_PROTECT_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.
.mcpbDownload ESET MCP (.mcpb) - then open Claude Desktop > Settings > Extensions and select the file. One click, no JSON, no shell. (Browse every ESET 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 eset-protect@msp-skills
Copy this into Claude Code, Codex CLI, or Claude Cowork:
Install the ESET 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/eset-protect/install.sh). If it uses Windows PowerShell, runiwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/eset-protect/install.ps1 | iex. Then authenticate per the README and runeset-protect-cli --helpto explore.
The same prompt works in any agent that can run shell.
Windows (PowerShell):
iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/eset-protect/install.ps1 | iex
macOS / Linux:
bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/eset-protect/install.sh)
The installer drops both eset-protect-cli (the CLI) and eset-protect-mcp (the MCP server) into your user bin path. Claude Code, Codex, and Cowork discover the Skill via SKILL.md in this directory.
Verify:
eset-protect-cli --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/eset-protect/install.sh)
Windows (PowerShell):
iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/eset-protect/install.ps1 | iex
Claude Desktop .mcpb users: download the latest .mcpb (top of this section) and re-select it in Settings > Extensions. Claude Code plugin users: /plugin update eset-protect@msp-skills.
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.
From the Hermes CLI:
hermes skills install servosity/msp-skills/skills/eset-protect --force
Inside a Hermes chat session:
/skills install servosity/msp-skills/skills/eset-protect --force
Hermes speaks MCP natively, so it can also use the eset-protect-mcp server directly - same install path, same env vars.
Tell your OpenClaw agent (copy this):
Install the eset-protect skill from https://github.com/servosity/msp-skills/tree/main/skills/eset-protect. The skill defines how its required CLI (
eset-protect-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.
Create a dedicated ESET Connect API user (a Superuser or Root does it in ESET PROTECT Hub, ESET Business Account or ESET MSP Administrator 2, with the Integrations toggle on), then give the CLI its email and password. ESET_PROTECT_REGION is the region of your ESET PROTECT console (eu by default; de, us, ca or jpn):
ESET_PROTECT_USERNAME=<value> ESET_PROTECT_PASSWORD=<value> ESET_PROTECT_REGION=<value> eset-protect-cli auth login
On Windows (PowerShell):
$env:ESET_PROTECT_USERNAME = "<value>"
$env:ESET_PROTECT_PASSWORD = " " $env:ESET_PROTECT_REGION = " " eset-protect-cli auth login
auth login exchanges the email and password for a one-hour ESET Connect token, caches the token for that region and user, and proves it with one read call (it exits 4 when ESET rejects the credentials or the API user cannot read devices, and 5 when the token request or the probe fails for another reason, such as a network error or an ESET outage); other commands mint and refresh the token on their own. The password is not written to disk. ESET_PROTECT_TOKEN is optional, for a token you minted yourself. eset-protect-cli doctor checks config, paths, reachability and the credentials, and exits 0 even when a row fails, so scripts should add --fail-on error.
Then fill the local mirror the per-customer views read from:
eset-protect-cli sync --resources devices,device-groups,detections,incidents
Re-run it before a triage or report run (the views read what was last synced), and run eset-protect-cli sync --full now and then: a plain sync adds and updates, while --full also drops devices and groups that were deleted in ESET.
| Question your MSP keeps asking | Command |
|---|---|
| Which customers have devices that need attention, are muted or stopped checking in? | eset-protect-cli fleet health |
| What should my techs work first this morning, detections and open incidents together? | eset-protect-cli triage --since 24h --min-severity medium |
| Which customers and devices are exposed to this CVE, and is a patch available? | eset-protect-cli exposure --cve CVE-2024-3400 |
| Give me one customer's quarter: device health, detections, incidents, top CVEs and patches | eset-protect-cli report customer "Acme Dental" --since 90d |
| Which devices have not checked in for two weeks, most stale first? | eset-protect-cli fleet stale --days 14 |
| Which security patches are still missing, ranked by the devices and CVE risk they fix? | eset-protect-cli patches backlog --security-only |
| Is the same file hash showing up at more than one customer this week? | eset-protect-cli detections spread --since 7d --min-customers 2 |
| Isolate this machine from the network (show me the exact task first) | eset-protect-cli respond isolate "FRONTDESK-01" |
Full command reference: guide.md. For the AI-agent operating contract (--agent, --dry-run, when to confirm before mutating), see AGENTS.md.
Most ESET 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 my 40 customers have machines that need attention or stopped checking in, worst first".
ESET Connect has no "which customer owns this device" call: the answer is the nearest ancestor device group linked to a company, which only the synced group tree can tell you. This skill syncs your ESET PROTECT tree into a local SQLite mirror, so fleet health, triage and detections spread are local joins across devices, device groups, detections and incidents, each row attributed to its customer. Live views such as exposure, patches backlog and report customer read ESET directly and attribute every hit through the same tree. A partial scan reports truncated and rejected_rows instead of passing for a clean result.
MCP servers such as maciekaz/ESET-MCP and Fenrindale/eset-protect-mcp expose the ESET Connect endpoints as tools. This one covers the endpoints too, and adds the per-customer rollups on top. ESET's own ESET LiveAI (formerly AI Advisor) is a generative AI assistant inside ESET PROTECT and ESET Inspect; t
Nur der Anfang wird gezeigt; den Rest findest du im Repo