Onda MCP
Related Servers
Alternatives to Onda MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceTerminal 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.2026Apache 2.0
- AlicenseAqualityAmaintenanceMCP server for hyperpanes terminal workspace app, enabling AI agents to compose and launch workspace layouts, inspect and drive terminal panes, stream output, and orchestrate agent hierarchies.471MIT
- AlicenseAqualityDmaintenanceMCP server that gives AI assistants full visibility into your tmux sessions — browse sessions, windows, and panes, read terminal output, and send commands.1451 npm1MIT
- AlicenseBqualityDmaintenanceLocal + remote terminal interaction control MCP Server. Lets AI agents control interactive TUI programs the way a human would.297 npmMIT
- AlicenseAqualityDmaintenanceMCP server for terminal control enabling AI to manage terminal sessions via iTerm2 or tmux, with features like screen reading, keyboard/mouse input, and background execution.912 npm21MIT
- 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.714MIT
TDQS
Scored across 39 tools
Most tools target distinct resources (panes, terminals, workspaces, windows, tabs) and actions, with clear descriptions. Some overlap exists between terminal_run, terminal_send, terminal_send_keys, and terminal_spawn, but their purposes are differentiated enough (newline, raw text, key sequences, exec). Overall, an agent can reliably select the right tool with careful reading.
The dominant pattern is domain_verb (e.g., onda_terminal_run, onda_workspace_focus, onda_pane_split), which is consistent. However, a few tools break the pattern: onda_context, onda_status, onda_app_info, onda_ping are nouns without a domain prefix, and onda_launch_session is a verb_noun with no domain. This mixed convention makes the set slightly harder to predict.
At 39 tools, this is well above the 25+ threshold for 'too many' per the calibration guide. While the domain is broad (panes, terminals, workspaces, windows, tabs, session), the count feels heavy and could overwhelm an agent. Several tools could potentially be merged (e.g., workspace_locate and workspace_list, window_focus and window_mount_workspace are distinct but related).
The tool set covers the full lifecycle of terminals, panes, workspaces, tabs, and windows: list, create, close, focus, read, subscribe, poll, kill, mount/unmount, and layout inspection. It even includes a high-level launch_session macro for complex workflows. Minor gaps exist (e.g., no explicit pane resize or terminal resize tool), but agents can work around them via window layout and tile tools.