What if your AI assistant could help you manage onchain actions directly from a conversation?
AI agents can already explain a portfolio, compare a swap or draft a payment. What they couldn't do was act on the wallet you actually hold without asking for keys you should never hand over. WalletConnect for Agents closes that gap: your agent prepares the action, and your wallet stays the only thing that can sign it.
Through the Model Context Protocol (MCP), it lets AI clients such as Claude, Claude Code and Cursor read your balances and prepare transfers and swaps on the wallet you already use, with every transaction approved by you, in your wallet app.
What you can do with WalletConnect for Agents
Check your portfolio.
Ask: “What tokens do I have on Base, and what's their USD value?” Get a breakdown of token balances and prices.
Prepare a transfer.
Say: “Send 10 USDC to this address on Arbitrum.” Your agent prepares the action and you review and approve it in your wallet.
Swap tokens.
Ask for a quote such as “How much ETH can I get for 25 USDC?” If you decide to proceed, the agent can prepare a supported Uniswap V3 swap for you to approve.
Build agent-powered payments.
Developers can use the HTTP API to integrate the same capabilities into agent workflows and backends.
Your wallet stays in control
WalletConnect for Agents never holds your signing keys. It acts as the app side of a WalletConnect session, so it can only ask your wallet to sign.
Every transaction follows the same path. First, your agent prepares an action. Next, it shows you the plan and confirms it against your original request, and any plan that doesn't match is refused. Then you approve in your wallet, and your agent tracks the transaction until it completes.
Guardrails apply before anything reaches your wallet: per-transaction caps, listed tokens only, token approvals for the exact amount of a trade and never unlimited, and plans that expire after five minutes. Anything that passes those checks still needs your signature.
Stay safe: check the URL before connecting
Until the WalletConnect for Agents MCP appears in AI app directories, you'll need to add it manually by pasting an endpoint into your AI client.
Only use the official endpoint: https://mcp.walletconnect.com/mcp. The safest way to get it is directly from WalletConnect's documentation, rather than from social replies, DMs or ads.
How to verify your connection:
- Check the complete address, character by character: https://mcp.walletconnect.com/mcp. It must use HTTPS, the exact walletconnect.com domain and the /mcp path, with no extra domains, characters or parameters.
- Watch for lookalikes. For example, mcp-walletconnect[.]com and mcp.walletconnect.com.secure-app[.]io are not WalletConnect domains.
- On first connection, check that the browser's consent page is on a genuine walletconnect.com domain. If it isn't, close it.
- Never share your seed phrase or private key. WalletConnect will never DM you a connection link or ask you to install a separate “verification” connector.
- Review each wallet request. Reject any transaction whose amount, recipient or contract you didn't intend to approve.
If anything looks suspicious, don't connect. Contact [email protected].
Remember: Your wallet approval is essential, but it doesn't make a malicious URL safe. Always verify the connection before authorizing it.
How to Get Started with WalletConnect for Agents
Once you have access, setup takes four steps: point your MCP-compatible client at the official endpoint, allow access on the consent page, choose any WalletConnect-compatible wallet, and approve the session in your wallet app.
The easiest way to get started is to follow our step-by-step setup instructions in the WalletConnect docs.
View the WalletConnect for Agents MCP documentation →
Not on the waitlist yet? Join now. We're rolling out access to more users progressively, so sign up to get the access in the upcoming wave.

