Add the wallet to Claude Desktop or Claude Code's MCP config. Wallet tools appear in the picker; proposals appear in your inbox.
Works with the agentsyou already run.
There is no partnership program and no waiting list. If it speaks MCP, it connects — the only thing you control is what each connection may do.
Pick a client, issue a token, connect.
Same config shape in .cursor/mcp.json — your editor's agent can check balances and draft transactions while you code.
Connects over the standard MCP transport with its own scoped token — the same pattern as every framework.
Connects like any MCP client — same tools, same review, same audit trail. No privileged path.
Spawn canonicalwalletd mcp over stdio from any framework. If it can run a process, it can use the wallet.
No agent needed — the CLI covers the identical surface for cron jobs and CI.
We don't vet clients. We scope tokens.
Any client can connect because no client is trusted. A connection is only as powerful as the token behind it — and tokens are read-only unless you deliberately grant more. The permissions guide has copy-paste recipes for the common cases.