Mirobody
Lab results to LOINC codes and UCUM units, symptoms and diagnoses to ICPC-3. Offline, no API key.
Descripción del creador (original en inglés)
Agentless Windows Server health checks over WinRM: one verdict per server, a diffable inventory
Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.
Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.
Elige la app de IA que usas y copia la configuración.
WINDOWS_SERVER_PASSWORD, WINDOWS_SERVER_USERNAME, WINDOWS_SERVER_MCP_READ_ONLY, WINDOWS_SERVER_NO_LOCAL_DATA, WINDOWS_SERVER_MCP_HTTP_TOKEN, WINDOWS_SERVER_BASE_URL, WINDOWS_SERVER_USER_AGENT, PRINTING_PRESS_CLIENT_PROFILELos valores marcados como secretos son llaves de tu cuenta. Nunca los compartas ni los pegues en un chat.
¿Qué app usas?
Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.
Descargar el archivo .mcpb del creador
El enlace lleva al archivo del propio creador; no lo alojamos ni lo reempaquetamos. Abre el archivo y Claude Desktop lo instalará.
Ejecuta esto en tu terminal
Completa los valores vacíos antes de ejecutarlo.
Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Este se ejecuta en tu computadora, y ChatGPT solo puede conectarse a servidores en internet. Elige otra app.
Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.
WINDOWS_SERVER_MCP_READ_ONLY envWINDOWS_SERVER_NO_LOCAL_DATA envWINDOWS_SERVER_BASE_URL envWINDOWS_SERVER_USER_AGENT envEsta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.
Se ejecuta en tu computadora; la lista de herramientas aparece en tu app de IA después de instalarlo.
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 7 nov 2026
El nombre en el registro se verificó con la cuenta de GitHub servosity, dueña del repo
Todavía no hemos leído este repo en GitHub
Todavía no hemos leído este repo en GitHub
Este se ejecuta en tu computadora; no hay endpoint en internet
Se ejecuta en tu computadora y usa ajustes locales en su lugar
Se ejecuta en tu computadora; solo podemos leer listas de herramientas de endpoints en internet
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Superó 1 de 1 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
Debes completar: WINDOWS_SERVER_PASSWORD, WINDOWS_SERVER_USERNAME, WINDOWS_SERVER_MCP_HTTP_TOKEN, PRINTING_PRESS_CLIENT_PROFILE
Se ejecuta en tu computadora. Tu app de IA lo inicia cuando hace falta, y los datos no pasan por los servidores del creador (a menos que el propio servidor llame a un servicio en línea).
El repo de GitHub cambió por última vez –, y la última versión (0.1.0) llegó al registro hoy.
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. También necesitas MCPB en tu computadora.
En la misma categoría: Mirobody, FHIR MCP Server, Google Health MCP
Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.
Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
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
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
Unofficial. Community-built Claude Code Skill and MCP server for Windows Server. Not affiliated with, endorsed by, or sponsored by Microsoft Corporation.
▶ Watch the 30-second demo - demo data is simulated; every command shown exists in the real CLI.
Agentless Windows Server health checks over WinRM: one verdict per server, a diffable inventory, and no arbitrary PowerShell. 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 Windows Server skill |
|---|---|
| Claude Desktop | Run installer, then Settings > Extensions to register windows-server-mcp (no JSON editing). |
| ChatGPT (paid plans) | Run installer, host windows-server-mcp over HTTPS with WINDOWS_SERVER_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 windows-server-mcp to mcp.json under the servers key, then pick Agent mode. |
For ChatGPT, run windows-server-mcp --transport http with WINDOWS_SERVER_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 windows-server-mcp over HTTPS with WINDOWS_SERVER_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 Windows Server MCP (.mcpb) - then open Claude Desktop > Settings > Extensions and select the file. One click, no JSON, no shell. (Browse every Windows Server 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 windows-server@msp-skills
Copy this into Claude Code, Codex CLI, or Claude Cowork:
Install the Windows Server 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/windows-server/install.sh). If it uses Windows PowerShell, runiwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/windows-server/install.ps1 | iex. Then authenticate per the README and runwindows-server-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/windows-server/install.ps1 | iex
macOS / Linux:
bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/windows-server/install.sh)
The installer drops both windows-server-cli (the CLI) and windows-server-mcp (the MCP server) into your user bin path. Claude Code, Codex, and Cowork discover the Skill via SKILL.md in this directory.
Verify:
windows-server-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/windows-server/install.sh)
Windows (PowerShell):
iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/windows-server/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 windows-server@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/windows-server --force
Inside a Hermes chat session:
/skills install servosity/msp-skills/skills/windows-server --force
Hermes speaks MCP natively, so it can also use the windows-server-mcp server directly - same install path, same env vars.
Tell your OpenClaw agent (copy this):
Install the windows-server skill from https://github.com/servosity/msp-skills/tree/main/skills/windows-server. The skill defines how its required CLI (
windows-server-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.
Windows Server has no API key: the CLI signs in to each server's WinRM HTTPS listener (port 5986) with a local or domain account in that server's Administrators group. Add each server to the config file (default ~/.config/windows-server-cli/config.toml on macOS and Linux, %USERPROFILE%\.config\windows-server-cli\config.toml on Windows; override with --config or WINDOWS_SERVER_CONFIG):
[[servers]]
name = "fs01" host = "fs01.corp.example" auth = "ntlm" # or "basic" (HTTPS only) username = "CORP\\svc-monitor" cert_sha256 = "4B:EF:..." # or ca_file = "/path/to/ca.pem" for a private CA default = true
Then store its password (read from stdin, kept only in the CLI's 0600 credential store) and run the real connectivity test:
macOS / Linux:
windows-server-cli servers login fs01 --username 'CORP\svc-monitor' < password.txt
windows-server-cli servers list --agent windows-server-cli health --agent
Windows (PowerShell):
Get-Content password.txt | windows-server-cli servers login fs01 --username 'CORP\svc-monitor'
windows-server-cli servers list --agent windows-server-cli health --agent
Or share one account across servers with WINDOWS_SERVER_USERNAME and WINDOWS_SERVER_PASSWORD. Passwords shorter than 8 characters are refused. With NTLM, a local account other than the built-in Administrator gets HTTP 401 unless LocalAccountTokenFilterPolicy is 1 on the server: use a domain account, or auth = "basic" over HTTPS. doctor checks config and paths and reports whether credentials are present; it does not contact a server. health is the connectivity test.
| Question your MSP keeps asking | Command |
|---|---|
| Which of my servers need attention today, and why? | windows-server-cli health --agent |
| Which automatic services are stopped, and what stopped them? | windows-server-cli services down --agent |
| Which errors are new on this server compared with its last 7 days? | windows-server-cli eventlog new --window 24h --baseline 7d --agent |
| Who added or removed a local admin this week? | windows-server-cli local-admins changes --hours 168 --agent |
| What changed since the last inventory snapshot? | windows-server-cli inventory diff --agent |
| Which certificates expire in the next 30 days? | windows-server-cli certificates --expiring-days 30 --agent |
| Which scheduled tasks failed their last run? | windows-server-cli scheduled-tasks --failed --agent |
| Restart the Print Spooler on fs01 (after a preview) | windows-server-cli services restart Spooler --server fs01 |
health, services down, eventlog new, local-admins changes and inventory snapshot read every configured server; the single reads and the service actions act on one server (--server , or the entry marked default = true).
Full command reference: guide.md. For the AI-agent operating contract (--agent, --dry-run, when to confirm before mutating), see AGENTS.md.
Most ways to put an AI on a Windows server hand it a PowerShell prompt. This one cannot run arbitrary script: every command is one of a fixed set of read scripts that ship inside the binary, checked by SHA-256 on the server before they run, with arguments validated and passed as typed data. The server comes from your config by name (never from the agent), certificate verification is always on, and nothing is installed on the server.
On top of the reads, compound commands do work a single PowerShell call cannot: health rolls every check into one verdict per server and remembers how long each has failed, services down pairs each stop with its Service Control Manager event, eventlog new compares against the server's own history, and inventory snapshot plus inventory diff keep a local SQLite history so you see what changed between runs.
Daily server checks are still a manual round on many MSP desks. The Active Directory Pro Windows Server maintenance checklist has you "monitor critical server services" every day, review disk space weekly, and check Event Viewer's application, security and system logs "for any c
Solo se muestra el principio; lee el resto en el repo