warden mcp
Standalone stdio MCP server exposing a warrant's Web3 tools.
warden mcp --token-file <path> # spawned by an MCP client, not run by handA Model Context Protocol server over stdio that exposes the warrant
token's Web3 tools: warden_scope and warden_sign. Token-only — no vault password.
This is an advanced / manual surface. warden run does not register it — the
default Web3 path is the agent running warden sign directly. Use warden mcp only if you want an MCP
client to call a structured warden_sign tool; wire it into that client's config yourself, pointing it
at the token via --token-file.
| Flag | |
|---|---|
--token | Warrant bearer token the tools act under. |
--token-file | Read the token from a file (0600 recommended), so it isn't inlined in the agent's config. |
Precedence: --token > --token-file > $WARDEN_TOKEN. The agent never sees keys — Warden signs
in-process and returns the signature. Web2 credential injection is the gateway's
job, not the MCP server's.