Smart hands for your AI agents - write-capable KVM+BMC+SSH MCP server: gated, verified, audited.
Kvm MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Smart hands for your AI agents - write-capable KVM+BMC+SSH MCP server: gated, verified, audited.
kvm-pilot lets an agent drive a headless box through POST, firmware, the bootloader, and an OS install with no agent on the target: it works at the pixel level through an IP-KVM (PiKVM, the GL.iNet GLKVM fork GL-RM1 / GL-RM1PE, BliKVM), at the structured-state level through a BMC (Redfish on iDRAC/iLO/OpenBMC, IPMI on BMCs that predate Redfish), at the firmware level through Intel AMT/vPro (a BIOS/POST/GRUB screenshot + power + SOL on a business laptop an HDMI-capture KVM can't see boot on), and over SSH once an OS is up. A pluggable vision subsystem reads a KVM screenshot and tells you what boot phase
The server ships on PyPI as kvm-pilot, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
Once Kvm is connected, these are the calls the assistant has available:
dry — run** short-circuits first: it logs the intended call and skips itconfirmation — a callback that can veto any destructive call that wouldVision — based boot-phase detection** — classify BIOS/GRUB/installer/crashGLKVM — fork awareness** — documents the API-enable prerequisite and GLStdlib — only client core** — the driver/vision code imports only the standardPlane — ReadDevice — StatusBliKVM — Expected to work (PiKVM-compatible API); untestedPlenty of monitoring and observability servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Kvm's toolset — dry, confirmation, Vision and 5 more — is a fair guide to whether it matches your workflow. It is maintained by DustinTrap; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| dry | run** short-circuits *first*: it logs the intended call and skips it |
| confirmation | a callback that can veto any destructive call that would |
| Vision | based boot-phase detection** — classify BIOS/GRUB/installer/crash |
| GLKVM | fork awareness** — documents the API-enable prerequisite and GL |
| Stdlib | only client core** — the driver/vision code imports only the standard |
| Plane | Read |
| Device | Status |
| BliKVM | Expected to work (PiKVM-compatible API); untested |
{
"mcpServers": {
"kvm-pilot": {
"command": "uvx",
"args": ["kvm-pilot"]
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.
Errors with full context — stack traces, issue triage and AI-powered root-cause analysis from Sentry's server.
Enables enhanced web research capabilities for large language models through intelligent search queuing and advanced content extraction.
Automates browser interactions and enables Large Language Models (LLMs) to interact with web pages through Playwright and Chrome DevTools Protocol
Guides tool usage by providing recommendations for MCP tools at each problem-solving stage.