Detour
Related Servers
Alternatives to Detour
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables agents to securely access saved SSH hosts through GUI-approved connections, token-authorized tunnels, command execution, background tasks, and SFTP file transfer.1,155 npmMIT
- AlicenseAqualityBmaintenanceSelf-hostable remote terminal assistance over MCP. Agents create one-command connection invitations, execute commands, and manage interactive sessions on user-authorized macOS, Linux, and Windows computers without requiring an SSH daemon.7106Apache 2.0
- FlicenseNot gradedqualityCmaintenanceWeb-based SSH connection manager with an MCP server that enables AI agents to manage remote hosts via terminals, file transfers, and port forwarding, featuring human-in-the-loop approval for secure access.-
- AlicenseAqualityDmaintenanceZero-config SSH/SFTP MCP server that lets an LLM client open temporary SSH/SFTP sessions to remote hosts, run commands, and upload/download files without holding any pre-baked credentials.177 npm2MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to manage an entire fleet of servers over SSH through MCP, fanning a single intent out across many hosts with target expressions while enforcing a policy engine, approval gates, and tamper-evident audit logs. Supports rolling execution with circuit breakers, cross-host diffing, bulk file transfer, tmux sessions, and YAML workflows.19AGPL 3.0
- AlicenseAqualityBmaintenanceEnables MCP clients to securely work with local files, directories, searches, terminal sessions, and processes on paired computers via outbound connections, without exposing inbound ports.74MIT
TDQS
Scored across 33 tools
Tools are grouped cleanly by resource (sessions, files, hosts, snippets, tunnels, access), and pairs that could collide are explicitly differentiated in the descriptions — run_command vs run_snippet vs send_input, read_file vs read_screen, request_access vs wait_for_access. The only mild ambiguity is `remove` and `rename`, which act on host filesystem paths but carry no noun in the name, so an agent must infer their scope from context.
The dominant pattern is verb_noun (read_file, add_host, start_tunnel, list_snippets, request_access), applied consistently across the four collection domains. Deviations are bare verbs — remove, rename, upload, download, sync_now — and the file-level `remove` is inconsistent with its own siblings remove_host/remove_snippet/remove_tunnel; also `make_dir` uses 'make' where the rest of the server uses 'add'.
33 tools is high in absolute terms, though it is spread across six genuinely distinct sub-domains (sessions, filesystem, hosts/vault, snippets, tunnels, access negotiation), each of which needs its CRUD surface. A few could be folded (e.g. start/stop_tunnel or upload/download as a single transfer tool), so the surface is heavier than strictly necessary but not padded.
Coverage is strong: hosts have add/update/remove/list, files have read/write/list/make_dir/rename/chmod/remove/upload/download, tunnels have the full add/update/remove/start/stop/list lifecycle, and access negotiation has both request and wait. The notable gap is snippets — add/remove/list/run exist but there is no update_snippet, so a saved command can only be deleted and recreated.