R
Razer0028/vsphere-console-mcp
Let an AI agent see and use the console of your VMware vSphere or Proxmox VE VMs — screen, mouse and
★ 1·updated 2026-11-13
View on GitHub ↗Direct link · no redirect page
We have no copy-paste install command and no public remote endpoint, so we do not print a config. The step above is reference only, not a command we can vouch for. A made-up one is worse than none. How each client wires MCP up →
- Star count
- 1 ★ · Razer0028/vsphere-console-mcp · read from the GitHub search API · (checked 2026-11-19 20:00:48)
- Source
- collected from the punkpeye/awesome-mcp-servers list · type: MCP server
- Harvest history
- first seen 2026-11-18 · last seen 2026-11-20 · seen 3× · listed by 3 sources
- Score
- score 300 · 1 ★ · 3 sources · mcp
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: MCP servers. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
Razer0028/vsphere-console-mcp;first catalogued 2026-11-18;last seen 2026-11-20。There is no official certification or quality rating here — we record sources and dates only.README excerpt (English, untranslated) · Read the full README on GitHub →
# vsphere-console-mcp
Excerpted from the repository README (abridged)
Let an AI agent see and use the console of your VMware vSphere or Proxmox VE VMs — screen, mouse and
keyboard — with nothing installed in the guest.
日本語
An MCP server with one tool, vm, that works the way the vSphere Client's
console window or Proxmox's noVNC console does. Because it never touches the guest OS, it reaches the places SSH,
RDP and in-guest agents cannot: sign-in and lock screens, the BIOS/UEFI setup, OS installers, a VM whose network is
down, a Windows VM stuck on a blue screen or "Preparing to configure Windows".
You: web-02 stopped answering. Look at its console.
Agent: [vm look web-02] It is in emergency mode: "Give root password for maintenance".
The journal line above says /data failed to mount. Do you want me to log in and check /etc/fstab?
It is meant for an agent working with a person, not for unattended automation: the person decides, the agent
looks, reads and types. See Good to know before you use it.
Two commands come with it: vsphere-console-mcp for vCenter, and proxmox-console-mcp for Proxmox VE.
Both offer the same tool.
## Why this one
Zero dependencies. Python standard library only — no pyVmomi, no websockets, no requests, no image
library. It speaks vSphere SOAP, the console screenshot endpoint and WebMKS, and the Proxmox API, its console
websocket and the VNC protocol itself, in about 2,500 lines you can read in an afternoon. Installing it pulls in
exactly one package.
Least privilege, verified. On vSphere the service account needs Read-only plus one privilege, Console
interaction; typing works through the console connection, so it does not need
VirtualMachine.Interact.PutUsbScanCodes. On Proxmox VE an API token with only VM.Audit and VM.Console is
enough.
No power button. There is no code to power on/off, reset, snapshot or reconfigure a VM. (Keys still reach the
guest, and ctrl+alt+delete reboots a Linux text console, a boot menu or a BIOS screen — see below.)
Correct symbols on non-US keyboards. Keys go as scan codes for the guest's layout (us, jis), not as
keysyms that the hypervisor would remap as US, so @ : _ \ arrive as typed.
Guardrails on the MCP side too: an allow-list of VM names, a read-only mode, a JSON audit log that never
records typed text, and a guard that stops retrying a rejected password or API token.
## Use cases
| Situation | What the agent does |
| A VM is unreachable over the network | Reads the console: kernel panic, emergency-mode prompt, full disk, a hung boot; tells you what it sees |
| Incident triage | Screenshots several VMs in turn and summarizes which are at a login prompt and which are stuck |
| Windows VM stuck before sign-in | Reads update/repair screens, sends ctrl+alt+delete, walks recovery menus — you approve each step |
| OS installation, first boot, OOBE | Goes through screens that have no network or automation hook yet |
| BIOS / UEFI | Reads firmware screens and changes settings with the keyboard |
| Labs, training, homelabs | Drives disposable VMs end to end, including the part before SSH works |
| Runbooks and tickets | Captures the exact console screen |
## Quick start (vSphere)
### 1. Install
bash
pipx install git+https://github.com/Razer0028/vsphere-console-mcp
keyboard — with nothing installed in the guest.
日本語
An MCP server with one tool, vm, that works the way the vSphere Client's
console window or Proxmox's noVNC console does. Because it never touches the guest OS, it reaches the places SSH,
RDP and in-guest agents cannot: sign-in and lock screens, the BIOS/UEFI setup, OS installers, a VM whose network is
down, a Windows VM stuck on a blue screen or "Preparing to configure Windows".
You: web-02 stopped answering. Look at its console.
Agent: [vm look web-02] It is in emergency mode: "Give root password for maintenance".
The journal line above says /data failed to mount. Do you want me to log in and check /etc/fstab?
It is meant for an agent working with a person, not for unattended automation: the person decides, the agent
looks, reads and types. See Good to know before you use it.
Two commands come with it: vsphere-console-mcp for vCenter, and proxmox-console-mcp for Proxmox VE.
Both offer the same tool.
## Why this one
Zero dependencies. Python standard library only — no pyVmomi, no websockets, no requests, no image
library. It speaks vSphere SOAP, the console screenshot endpoint and WebMKS, and the Proxmox API, its console
websocket and the VNC protocol itself, in about 2,500 lines you can read in an afternoon. Installing it pulls in
exactly one package.
Least privilege, verified. On vSphere the service account needs Read-only plus one privilege, Console
interaction; typing works through the console connection, so it does not need
VirtualMachine.Interact.PutUsbScanCodes. On Proxmox VE an API token with only VM.Audit and VM.Console is
enough.
No power button. There is no code to power on/off, reset, snapshot or reconfigure a VM. (Keys still reach the
guest, and ctrl+alt+delete reboots a Linux text console, a boot menu or a BIOS screen — see below.)
Correct symbols on non-US keyboards. Keys go as scan codes for the guest's layout (us, jis), not as
keysyms that the hypervisor would remap as US, so @ : _ \ arrive as typed.
Guardrails on the MCP side too: an allow-list of VM names, a read-only mode, a JSON audit log that never
records typed text, and a guard that stops retrying a rejected password or API token.
## Use cases
| Situation | What the agent does |
| A VM is unreachable over the network | Reads the console: kernel panic, emergency-mode prompt, full disk, a hung boot; tells you what it sees |
| Incident triage | Screenshots several VMs in turn and summarizes which are at a login prompt and which are stuck |
| Windows VM stuck before sign-in | Reads update/repair screens, sends ctrl+alt+delete, walks recovery menus — you approve each step |
| OS installation, first boot, OOBE | Goes through screens that have no network or automation hook yet |
| BIOS / UEFI | Reads firmware screens and changes settings with the keyboard |
| Labs, training, homelabs | Drives disposable VMs end to end, including the part before SSH works |
| Runbooks and tickets | Captures the exact console screen |
## Quick start (vSphere)
### 1. Install
bash
pipx install git+https://github.com/Razer0028/vsphere-console-mcp
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/razer0028-vsphere-console-mcp/)
- Source
- awesome · https://github.com/Razer0028/vsphere-console-mcp
- Browse by field
- MCP servers
- Traction
- 1 ★
- Listed by
- 3 independent sources
- added
- today
More MCP servers
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.