Mirobody
Lab results to LOINC codes and UCUM units, symptoms and diagnoses to ICPC-3. Offline, no API key.
作者提供的说明(英文原文)
Every ESET Connect endpoint, plus per-customer health, exposure and QBR reports from a local mirror
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
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_PROFILE标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
链接指向作者自己的文件;我们不托管也不重新打包它。打开文件后,Claude Desktop 会进行安装。
在终端中运行这条命令
运行前请先填写空着的值。
浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
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 env这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月8日
注册名称已通过 GitHub 账户 servosity 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:ESET_PROTECT_USERNAME, ESET_PROTECT_PASSWORD, ESET_PROTECT_TOKEN, ESET_PROTECT_MCP_HTTP_TOKEN
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(0.1.0)于今天进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 MCPB。
同一分类中有:Mirobody, FHIR MCP Server, Google Health MCP
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
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
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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
只显示了开头部分;其余内容请在仓库中阅读