jetkvm_mcp_server

JetKVM MCP Server exposes the complete jetkvm_client API via MCP tools, allowing an AI assistant to control a JetKVM device remotely over a standard MCP transport. The server maintains a persistent WebRTC connection to the JetKVM device and surfaces functionality as MCP tools that can be invoked by assistants such as Claude. Available tools include text input to the remote system (send_text) and the ability to capture a screenshot from the remote display (screenshot). The server is designed to support additional controls in the future (keyboard shortcuts, mouse interactions, power management, and hardware configuration) as the underlying jetkvm_client and the MCP integration evolve.

To use the server with Claude or Cursor, run the server with the correct environment variables set for your JetKVM device, then reference the MCP server in your client configuration. You can call tools like send_text to type text on the remote machine, or request a screenshot by specifying max_width and max_height to obtain a base64-encoded PNG image suitable for direct embedding in the UI. Ensure the WebRTC connection to the JetKVM device is established before requesting screenshots, typically after a short connection delay.

Prerequisites:

• Rust 1.70 or later
• A JetKVM device reachable on the network
• GStreamer libraries (for video functionality)

On NixOS / with Nix flakes:

nix develop

On other systems, install:

# System packages
# - GStreamer and development headers
# - OpenSSL and pkg-config

Installation from source:

git clone https://github.com/nilp0inter/jetkvm_mcp_server.git
cd jetkvm_mcp_server
cargo build --release

The binary will be at target/release/jetkvm_mcp_server.

Environment variables:

• JETKVM_HOST: Hostname/IP and port of the JetKVM device (e.g., 192.168.1.100:80)
• JETKVM_PASSWORD: Password for the JetKVM device

Tips:

• If you encounter GStreamer build issues, ensure development headers are installed and PKG_CONFIG_PATH includes GStreamer.
• For Claude/Desktop integration, update your MCP client configuration to reference the server binary path and provide the required environment variables.
• The server currently emphasizes keyboard control and screenshot capability; mouse control and system management are planned features (coming soon).
• When running in development, you can test locally by exporting the environment variables and launching cargo run or the released binary directly.