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
この3つを1つのスコアにまとめることはしません。意見、測定、人気はそれぞれ別のものだからです。
このサーバーのやさしい解説はまだ書いていません。以下はレジストリから読み取った事実です。
使っている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)がレジストリに届いたのは今日です。
Claude Desktop、Claude Code、Cursor、VS CodeなどのMCP対応アプリで使えます。パソコンにMCPBも必要です。
同じカテゴリには:Mirobody, FHIR MCP Server, Google Health MCP
同じカテゴリで、ほかの作者が作ったサーバー。スターの多い順。
カードの見方:★ GitHubスターi3つの柱:レビュー · チェック · 利用状況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
冒頭だけを表示しています。続きはリポジトリで読めます