NanoKVM PicoClaw MCP
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@NanoKVM PicoClaw MCPcheck NanoKVM status"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
NanoKVM PicoClaw MCP
An unofficial, self-hosted MCP adapter for the PicoClaw service installed by NanoKVM. It does not contain NanoKVM firmware and is not affiliated with Sipeed or TinyAGI.
The adapter proxies NanoKVM's native PicoClaw MCP handler instead of copying its screenshot and HID action semantics into another implementation. It also has explicit NanoKVM status, reboot, and macOS recovery-key tools.
Security boundary
Keep NanoKVM on a private network. Do not expose this stdio server directly to the Internet. If remote MCP access is needed, put an authenticated gateway such as GPTAdmin in front of one private relay instance.
The gateway machine is the only system that should hold device credentials and the SSH key. Other MCP clients should authenticate to that gateway, never to the NanoKVM itself.
The adapter requires a pinned known_hosts file for every SSH operation. It
refuses unknown SSH host keys and disables agent/port forwarding.
Related MCP server: mcp-ssh-tool
Install
python3 -m pip install nanokvm-picoclaw-mcpSet device-specific values in a mode-600 environment file owned by the relay service account. Do not put them in a repository or in command-line arguments.
export NANOKVM_URL='http://nanokvm.private.example'
export NANOKVM_USER='admin'
export NANOKVM_PASSWORD='set-in-a-secret-store'
export NANOKVM_SSH_HOST='nanokvm.private.example'
export NANOKVM_SSH_USER='root'
export NANOKVM_SSH_KEY='/secure/path/nanokvm_ed25519'
export NANOKVM_SSH_KNOWN_HOSTS='/secure/path/known_hosts_nanokvm'
nanokvm-picoclaw-mcpThe server exposes nanokvm_status, nanokvm_reboot,
nanokvm_hold_recovery_keys, picoclaw_tools_list, picoclaw_tools_call,
and picoclaw_chat. Treat reboot, recovery-key and dynamic PicoClaw calls as
operator-only capabilities; a public gateway should enforce its own explicit
authorization policy.
Development
python3 -m pip install -e '.[test]'
pytest -qAll tests are offline and use fake HTTP, WebSocket, and SSH transports.
This server cannot be deployed
Maintenance
Related MCP Connectors
Run commands and read/write files on your servers over Termalin's keyless tunnels (hosted MCP).
Tailscale device, route, DNS, key, user, and ACL management over MCP and CLI.
MCP server bridging holepunchto/keet-identity-key to the Hive agentic identity network
Manage CloudPepper servers, Odoo instances, backups, and deployments over MCP.
Related MCP Servers
- FlicenseAqualityDmaintenanceEnables AI assistants to remotely control Sipeed NanoKVM hardware for BIOS-level management of servers and headless machines. It provides tools for power control, keyboard and mouse emulation, screen capture, and ISO image mounting via the Model Context Protocol.1913-
- AlicenseAqualityAmaintenanceSSH automation MCP server that enables Claude and ChatGPT to execute commands, manage files, install packages, and control services on remote servers over SSH — supporting password, key, and agent authentication.331,267 npm4MIT
- FlicenseNot gradedqualityCmaintenanceEnables secure SSH command execution and log retrieval with intelligent summarization using local LLM (Ollama) and Model Context Protocol (MCP) standards.-
- FlicenseAqualityDmaintenanceEnables AI assistants to perform comprehensive SSH operations including command execution, file transfers, port forwarding, and key management through a stateless, Docker-ready MCP server.15-