network-terminal-mcp
Related Servers
Alternatives to network-terminal-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to interact with real terminal sessions across local and remote hosts, driving multi-turn interactive programs like TUIs, REPLs, and SSH prompts through MCP.57MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to drive switches, servers, and consoles over SSH or serial Console through 28 MCP tools, auto-detecting vendors, paging through long output, and cleaning raw byte streams into readable text. Provides structured diagnostics (interfaces, ARP/MAC/routing tables, ping, logs, health checks) plus a three-tier safety model with audit logging, credential redaction, and dry-run config changes.MIT
- AlicenseNot gradedqualityDmaintenanceProvides persistent interactive shell sessions via pseudo-terminals for MCP agents, enabling bidirectional communication, incremental reads, and stateful command execution across steps.5 npmMIT
- AlicenseNot gradedqualityFmaintenanceEnables AI agents to have persistent, fully interactive SSH sessions into remote hosts, behaving like a local terminal.6 npm2MIT
- AlicenseNot gradedqualityAmaintenanceTerminal-first SSH access for MCP clients and AI agents, enabling interactive remote sessions, file uploads, and stateful workflows.7 npm1MIT
- AlicenseNot gradedqualityDmaintenanceMCP server that enables AI agents to run fully interactive SSH sessions (via tmux) and execute commands like a human operator, with persistent sessions and multiple concurrent connections.6MIT
TDQS
Scored across 7 tools
Most tools have distinct purposes: open/close session, write, write secret, status. The only potential confusion is between terminal_read (live, quiet-based) and read_output (bounded offset slice), but descriptions clarify the difference by pointing to each other.
All names use snake_case and are readable, but conventions are mixed: some follow verb_noun (open_session, close_session, read_output), while others use noun_verb (terminal_write, terminal_read, terminal_write_secret). The 'terminal_' prefix is applied inconsistently.
Seven tools is well-scoped for an interactive terminal session server. Each tool covers a distinct lifecycle operation (open, close, write, read, secret write, status, buffered read) and none feels redundant or excessive.
The set covers the core lifecycle: open, interact, read output, check status, and close. A minor gap is the absence of a list_sessions tool to manage multiple concurrent sessions, but agents can work around this by tracking session IDs themselves.