Mcp-Warden
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_WARDEN_APPROVAL_TRANSPORT | No | Override the approval transport at runtime. Valid values: telegram, desktop, tui. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Local-first credential broker. Use list_presets to discover available actions, then proxy_http, ssh_run, ssh_exec, sftp_transfer or db_query to execute them. Secrets never leave the broker.
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 |
|---|---|
| db_queryA | Run a NAMED QUERY against a database preset (PostgreSQL, MySQL,
or Redis). You supply |
| get_secret_for_envA | Reveal the raw secret value bound to a name. ALWAYS prompts for
approval, regardless of preset policy. Prefer |
| list_presetsA | List available mcp-warden presets — named, scoped actions you may
invoke. Returns name, description, type
(http|ssh|postgres|mysql|redis), and approval policy
(auto|prompt|deny); for SSH presets, also their named commands with
what each parameter accepts. Read-only; never returns secret values.
Use |
| proxy_httpA | Make an HTTP request through a preset. The preset selects the base
URL and authentication; you supply |
| sftp_transferA | Transfer a file between the preset's SSH host and the local
machine. |
| ssh_execA | Run a shell command on the preset's SSH host. The command must
match one of the preset's |
| ssh_runA | Run one of an SSH preset's named commands. You supply |
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 7 tools
Most tools target clearly distinct resources: HTTP via presets, SFTP transfer, named DB queries, secret reveal, and preset listing. The one fuzzy pair is ssh_exec (allow-listed shell command) vs ssh_run (preset-declared named command), which both execute on the same host and could be confused despite the descriptions drawing the distinction. Overall the boundaries are clear, with that single adjacent pair.
All names are snake_case and readable, using recognizable domain nouns (db, ssh, sftp, http, secret, presets). The ordering is mixed — noun_verb in db_query/sftp_transfer/ssh_exec/ssh_run/proxy_http versus verb_noun in get_secret_for_env/list_presets — which is a minor deviation rather than a real inconsistency.
Seven tools is well-scoped for a credential/action broker: one discovery tool, one per transport (HTTP, SSH exec, SSH named, SFTP, DB), plus an escape hatch for secrets. Each tool clearly earns its place and nothing looks redundant.
Core action paths are covered, but discovery has a real hole: db_query requires a `query_name` yet list_presets is documented as returning named commands only for SSH presets, so an agent may not be able to learn valid DB query names. The audit log is referenced on nearly every tool but there is no way to read it, and no tool surfaces or manages approval windows.