Detour
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Detour is the person's SSH client. Through it you work on their servers without seeing their passwords or keys. Start with list_hosts. Before using a host, call request_access with the hosts, the scopes you need and why; the person approves it in the Detour window (or with detour approve in a terminal). Then open_session on the host and use run_command in it: the person sees your session and every command in Detour. With the connect scope each command waits for the person's approval; with exec it runs at once. Ask only for what the task needs.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add_hostB | Add a host to the person's vault, or to a team (needs vault:edit; in a team, over all its hosts). To use it, request access to it. |
| add_snippetB | Save a snippet: a named command (needs vault:edit). |
| add_tunnelB | Save a tunnel through a host (needs vault:edit; for a team's host, one your access reaches): local (ssh -L), remote (ssh -R) or dynamic (SOCKS5, ssh -D). |
| chmodC | Change a file's permissions on a host. |
| close_sessionB | Close a session of yours. |
| downloadC | Download a file or folder from a host to this computer. |
| generate_keyB | Create a key in the person's vault (needs vault:edit). Returns its public key, e.g. for authorized_keys; the private key never leaves Detour. |
| list_dirC | List a folder on a host. |
| list_hostsA | The person's hosts in Detour, with the access you have to each. Never shows passwords or keys. |
| list_sessionsC | Your open sessions. |
| list_snippetsC | The person's saved snippets: named commands. |
| list_tunnelsB | The person's saved tunnels and their teams', and whether they run. |
| make_dirC | Create a folder on a host. |
| open_sessionB | Open a terminal session on a host. The person sees it as a tab in Detour. |
| read_fileB | Read a text file on a host (up to 1 MB). |
| read_screenC | What the session's terminal shows now, as text. |
| removeB | Remove a file, or a folder with everything in it, on a host. |
| remove_hostA | Remove a host from the person's vault or from a team (needs vault:edit; in a team, a host your access reaches). |
| remove_snippetC | Remove a snippet (needs vault:edit). |
| remove_tunnelA | Remove a saved tunnel (needs vault:edit; for a team's, through a host your access reaches). A tunnel you started is stopped first. |
| renameC | Rename or move a file or folder on a host. |
| request_accessA | Ask the person for access to hosts. They see your name, the hosts, the scopes and your reason, and may allow less than you asked. Waits up to 100 seconds for the answer; if it is still pending, ask the person to approve it: their answer takes effect by itself, and wait_for_access waits for it. |
| run_commandA | Run a shell command on the session's host and get its exit status, stdout and stderr. It runs non-interactively, beside the terminal (not typed into it); the person sees it in the session's tab. Don't run commands that wait for input; use send_input for interactive programs. |
| run_snippetC | Run a saved snippet in a session, like run_command. |
| send_inputA | Type into the session's terminal, as the person would: for interactive programs. Read the result with read_screen. |
| start_tunnelC | Start a saved tunnel (needs the tunnels scope on its host). |
| stop_tunnelB | Stop a tunnel you started. |
| sync_nowA | Sync the person's vault with their other devices now (needs vault:edit). |
| update_hostB | Change a host of the person's vault or of a team (needs vault:edit; in a team, a host your access reaches). |
| update_tunnelC | Change a saved tunnel (needs vault:edit; for a team's, through a host your access reaches). |
| uploadB | Upload a file or folder from this computer to a host. An existing file there is replaced. |
| wait_for_accessA | Wait for the person's answer to a request_access that is still pending (up to 100 seconds). |
| write_fileB | Write a text file on a host, replacing it if it exists. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.