Claude KVM
Related Servers
Alternatives to Claude KVM
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceA self-hosted, VNC-backed MCP server that enables AI agents to control a dedicated macOS user session remotely, without disturbing the console user.-
- AlicenseAqualityCmaintenanceA macOS-based MCP server that allows for capturing screenshots of displays and windows, as well as recording window activity to MP4 files. It leverages a Swift CLI backend to interact with macOS CoreGraphics and AVFoundation APIs for seamless screen capture management.732 npm1MIT
- AlicenseAqualityDmaintenanceAn MCP server that allows AI agents to remotely control Windows, Linux, and macOS systems via VNC. It provides tools for mouse and keyboard interaction, text input, and screen capturing.6239 npm57MIT
- AlicenseNot gradedqualityFmaintenanceAn MCP server to control iOS Simulators.9 npm53MIT
- AlicenseNot gradedqualityCmaintenanceA production-ready MCP server for secure, session-based command execution, file manipulation, and system inspection via local terminal sessions.11 npmISC
- FlicenseAqualityDmaintenanceMCP server for macOS desktop automation enabling screenshot, click, type, scroll, and more. Retina-aware, supports CJK text input and multi-monitor, works with any MCP client without API keys.155-
TDQS
Scored across 4 tools
Tool names suggest distinct functions: queuing actions, completing tasks, failing tasks, and sending VNC commands. However, task_complete and task_failed are closely related status updates, and all lack descriptions, causing some ambiguity.
Naming is inconsistent: action_queue (noun_noun), task_complete (noun_verb), task_failed (noun_verb), vnc_command (noun_noun). The pattern mixes noun-noun and noun-verb structures without a clear convention.
Four tools is borderline low for a KVM server, but could be acceptable if the server focuses narrowly on task management and VNC control. However, typical virtualization operations are missing, making the count feel thin.
The tool set lacks fundamental operations for managing virtual machines (e.g., list, create, delete, start, stop). It only covers task status and VNC commands, leaving significant gaps for a KVM server's domain.