aiterm-mcp
Related Servers
Alternatives to aiterm-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceMCP server that launches and supervises coding-CLI subagents (claude, opencode) in detached tmux windows, collapsing the ceremony of starting a TUI coding assistant into a single tool call.5MIT
- AlicenseAqualityCmaintenanceAn MCP server that gives orchestrator agents fine-grained control over interactive Claude Code sessions running inside tmux, enabling mid-session steering, interruption, and token-efficient result extraction.15MIT
- AlicenseAqualityCmaintenanceMCP server that lets Claude Code drive the local Codex CLI as a sub-agent for concurrent queries and optional file/shell actions, using the CLI's existing login and sessions.441 npm1MIT
- AlicenseAqualityDmaintenanceAn MCP server that connects Claude Desktop to an interactive Claude Code session running in a tmux terminal.1MIT
- AlicenseAqualityDmaintenanceMCP server for orchestrating multiple Claude Code instances via tmux, enabling spawning, reading, sending, listing, and killing sessions.528 npm2MIT
- AlicenseAqualityBmaintenanceMCP server that routes Claude Desktop chat into Claude Code, enabling headless execution and terminal handoff with session continuity.4MIT
TDQS
Scored across 18 tools
Three legacy alias tools (claude_agent, codex_agent, grok_agent) duplicate agent_launch and create overlap, and pty_send/pty_read carry multiple modes (dispatch/steer, transcript recovery). Descriptions are very detailed and mark aliases as deprecated, which mitigates but does not eliminate misselection risk.
All snake_case with domain prefixes (pty_, agent_, claude_), mostly consistent. Minor deviations: claude_agent/codex_agent/grok_agent prefix by harness rather than action, and diagnostics lacks a prefix.
18 tools is slightly heavy but reasonable for a server covering PTY lifecycle, multiple agent harnesses, approvals, and diagnostics. Three legacy aliases are redundant, but the remaining 15 are well-scoped.
Covers terminal lifecycle (open/close/read/send/key/list/observe), agent lifecycle (launch/auth/configure/models/approval/turn), and diagnostics. Minor gaps: no dedicated wait/wait_process tool (handled externally via receipts) and no explicit PTY resize, but core workflows are covered.