Add Josepavese/nido to the GitHub MCP Registry (curation request) #3572

Curation request: Josepavese/nido

Server name: nido
Repo: https://github.com/Josepavese/nido
Type: Local MCP server (Go, stdio), also distributed as an MCPB bundle and an npm launcher.

What it does

Nido gives agents disposable or persistent QEMU/KVM Linux VMs on the developer's machine: nido_vm, nido_template, nido_image, nido_blueprint, nido_system tools plus read-only resources (nido://fleet/vms, nido://catalog/blueprints, nido://system/config). It is useful for coding agents that need a real sandbox to build, test and break things without touching the host.

Registry evidence

• Official MCP Registry: io.github.Josepavese/nido (versions 4.5.17 → 4.8.1, published through GitHub OIDC from the release workflow).
• Glama: https://glama.ai/mcp/servers/Josepavese/nido
• npm launcher: nido-mcp (downloads the release binary, verifies SHA-256, runs it).
• Install: brew install Josepavese/nido/nido, scoop install nido, go install github.com/Josepavese/nido/v4/cmd/nido@latest, or the release installers.
• MCP smoke test: nido mcp --help / the server initializes over stdio; the repo ships CLI and MCP tests.

Why it fits

GitHub Copilot and agent developers need local VM isolation to run model-generated code and system-level changes. Nido is the local, KVM-backed counterpart to cloud sandbox servers already in the registry, with no account and no remote control plane.

Happy to provide a demo transcript or adjust metadata.