hyperpanes-mcp
Related Servers
Alternatives to hyperpanes-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceTerminal multiplexer MCP server for orchestrating parallel AI agents. Manages workspaces, panes, surfaces with send_input/read_screen/spawn_agent/stop_agent tools. Supports Claude Code, Codex, Gemini, Cursor CLI agents with lifecycle management, browser automation, and agent status push via Claude --channels.1027Apache 2.0
- AlicenseNot gradedqualityDmaintenanceTerminal MCP server for AI coding agents with persistent PTY sessions, ring-buffer incremental reads, headless xterm screen capture, multi-agent orchestration, and a real-time web dashboard.17 npm23MIT
- AlicenseAqualityDmaintenanceMCP server to control Onda terminal from AI agents, providing tools for splitting panes, running commands, managing tabs and workspaces, and orchestrating multi-agent workflows across multiple windows.397 npmMIT
- AlicenseBqualityDmaintenanceLocal + remote terminal interaction control MCP Server. Lets AI agents control interactive TUI programs the way a human would.298 npmMIT
- AlicenseBqualityCmaintenanceA comprehensive MCP server for driving tmux sessions, windows, panes, sending keystrokes, and reading pane output locally or over SSH, enabling real-time collaborative pairing with AI.713MIT
- AlicenseAqualityCmaintenanceMCP server that gives AI agents real interactive terminal sessions for running REPLs, SSH, database clients, and any interactive CLI with clean text output and smart completion detection.751 npm18MIT
TDQS
Scored across 47 tools
Most tools are clearly distinct, but there is some potential overlap between messaging/input tools like send_message, queue_prompt, prompt_pane, and send_input, which all involve sending text to a pane. Descriptions are detailed enough to separate them, but the boundaries are not perfectly obvious at a glance.
The naming convention is predominantly verb_noun in snake_case (e.g., launch_workspace, lock_pane, enqueue_task), which is consistent. Minor deviations like whoami and send_to_parent break the pattern slightly, but overall the convention is predictable and readable.
With 47 tools, this server is far above the typical well-scoped range of 3-15. While the tool count reflects a broad feature set (panes, workspaces, queues, messaging, projects, speech), it exceeds the threshold where usability suffers, making it feel bloated and harder to navigate.
The tool set covers the domain comprehensively: pane lifecycle, workspace management, queue operations, project management, messaging, and app control. Minor gaps exist (e.g., no explicit window/tab listing tool, no move/resize pane), but agents can work around them using existing tools, so the surface is largely complete.