mcp-sudo
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.
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| store_passwordC | Store sudo password encrypted. Only needs to be done once. |
| sudo_execA | Execute a command with sudo using the stored password. Args: command: The shell command to run with sudo. timeout: Timeout in seconds (default 120). |
| has_passwordA | Check if a sudo password is already stored. |
| clear_passwordB | Remove the stored sudo password. |
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 4 tools
Each tool has a clear, distinct purpose: storing, checking, clearing password, and executing commands. No overlap or ambiguity between tools.
All tool names follow a consistent verb_noun pattern (store_password, has_password, clear_password, sudo_exec) with snake_case. The naming is predictable and clear.
With 4 tools covering password management and sudo execution, the number is perfectly scoped for the domain. Each tool serves a necessary function without redundancy.
The tool set covers the essential password lifecycle and command execution. A minor gap is the lack of an explicit update tool, but store_password likely allows overwriting.