Local MCP
Run the Walletguide MCP server on your own machine over stdio, launched by your client and authenticated with an API key.
An npm package your client launches. Authenticated with an API key, so it reaches exactly the one wallet that key belongs to.
Claude Desktop
{
"mcpServers": {
"walletguide": {
"command": "npx",
"args": ["-y", "@walletguide/mcp"],
"env": { "WALLETGUIDE_API_KEY": "wg_…" }
}
}
}Restart Claude Desktop and the tools appear.
Claude Code
claude mcp add walletguide --env WALLETGUIDE_API_KEY=wg_… -- npx -y @walletguide/mcpConfiguration
| Variable | Default | What it does |
|---|---|---|
WALLETGUIDE_API_KEY | required | Your wg_ key |
WALLETGUIDE_MCP_WRITES | off | 1 or true adds the tools that change data |
WALLETGUIDE_BASE_URL | https://api.walletguide.com | Point at another api |
WALLETGUIDE_WALLET_ID | the key's wallet | Only needed to be explicit |
The key is scoped to one wallet, so tools default to it and walletId is optional.
Enabling writes
"env": {
"WALLETGUIDE_API_KEY": "wg_…",
"WALLETGUIDE_MCP_WRITES": "1"
}That takes the catalogue from 46 tools to 149. Everything destructive is annotated as such, so a client that confirms before running one will confirm.
When nothing appears
A stdio server is launched by a config file, so a misconfiguration usually looks like a client that silently has no tools. The server writes its reason to stderr, which most clients keep in a log. Missing key, wrong key, unreachable host: all three say so there.
Check the key by hand first:
curl -H "Authorization: Bearer wg_…" https://api.walletguide.com/wallets