sudo-proxy
OfficialServer 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.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| start_serverA | Start a sudo-proxy approval daemon: with no |
| executeA | Execute a command (or multi-stage pipeline) on a sudo-proxy host after a human approves it at that host's terminal. Provide |
| update_hostA | Record or update metadata for a host in the sudo-proxy registry (~/.config/sudo-proxy/hosts.json), which is surfaced in this server's instructions and in status output. Partial update: only the |
| statusA | Report the status of sudo-proxy daemons without executing any command: with |
| stop_serverA | Stop a running sudo-proxy daemon: sends a stop request over its socket; the daemon prints a shutdown notice on its terminal (no approval prompt is required), exits, and its terminal window — and SSH tunnel, for remote hosts — closes. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| known-hosts | Known sudo-proxy hosts with system info and last connection time |
TDQS
Scored across 5 tools
Each tool targets a distinct action and resource: execute runs approved commands, start_server/stop_server manage daemons, status reports state, and update_host edits registry metadata. No overlapping purposes or ambiguous boundaries.
Three tools follow a clear verb_noun snake_case pattern (start_server, stop_server, update_host), but execute is a bare verb and status is a bare noun. The deviations are minor and still readable, so mostly consistent.
Five tools is well-scoped for a proxy/daemon manager; each tool covers a necessary lifecycle operation (start, execute, status, stop, update host metadata) without redundancy.
The surface covers daemon lifecycle (start, execute, status, stop) and host metadata update, but lacks a way to remove or delete a host from the registry. Status partially covers listing, so the gap is minor.