Coinbase Wallet MCP

@Coinbase Wallet MCP what's my current portfolio value and which assets do I hold?

Your total portfolio value is $4,287.35 across 4 assets. Breakdown: ETH (1.23 ETH) = $3,845.20, USDC (350.00 USDC) = $350.00, OP (45.8 OP) = $82.15, and BASE (12.5 BASE) = $10.00. All values reflect current market prices on Base mainnet. This data is pulled from your Base Account address and includes balances across supported chains where you hold assets.

This example uses get_portfolio to aggregate cross-chain holdings. The MCP only queries the authenticated user's own wallets—you cannot inspect third-party addresses. Portfolio values depend on real-time price feeds and may lag by a few minutes during high volatility.

@Coinbase Wallet MCP send 0.05 ETH to 0x742d35Cc6634C0532925a3b844Bc9e7595f0bEb to cover gas for our shared testnet deployment

I've initiated a send request (requestId: req_8x9k2m) to transfer 0.05 ETH from your agent wallet to 0x742d35Cc6634C0532925a3b844Bc9e7595f0bEb on Base mainnet. You'll need to approve this transaction in your Base Account app. Once approved, the transfer will execute on-chain. Estimated gas: ~0.0002 ETH. Check status anytime with get_request_status using the requestId above.

This demonstrates the two-step approval flow: the MCP initiates the request, but you must confirm in the Coinbase Wallet app before funds move. Only wallets with inSession=true (active delegation) can send. The MCP enforces spend policies configured in your wallet—requests exceeding limits will fail.

@Coinbase Wallet MCP check the last 10 transactions on my Base wallet and summarize any unusual activity or failed transfers

I pulled your last 10 transactions on Base mainnet. Nine were successful: seven USDC transfers (ranging $20–$150), one ETH swap for 0.3 ETH, and one NFT mint (0.001 ETH fee). One transaction failed: a 0.5 ETH send on March 15 at 14:32 UTC—reverted due to insufficient gas. The recipient address was 0x8f3e…4a2c. No other anomalies detected; all successful txs confirmed within 2–5 seconds.

This pairs get_transaction_history with AI reasoning to surface patterns. The MCP returns raw transaction data (status, value, gas, timestamp); the AI interprets it. Transaction history is chain-specific—you must query each chain separately if you hold assets on multiple networks. Third-party addresses cannot be queried.

When this MCP works for monthly finance close

A 6-person startup holds operating reserves in USDC on Base and needs monthly snapshots for their board deck. The CFO connects Coinbase Wallet MCP to pull portfolio value and transaction history without leaving Switchy. This works if your treasury sits in a single Base Account and you're reporting totals, not reconciling line-by-line with QuickBooks. The get_portfolio and get_transaction_history tools cover the 80% case: balances by asset and a paginated ledger. If you need multi-chain consolidation beyond the 9 supported networks or real-time alerts on inbound transfers, you'll hit the read-only boundary fast. For a monthly ritual where someone exports a CSV and pastes it into a slide, this MCP saves 15 minutes and keeps the workflow in one place.

When support teams need wallet context in real time

A 12-person crypto product team fields support tickets where users claim a transaction failed or funds never arrived. The support lead authenticates Coinbase Wallet MCP with OAuth2 so agents can query transaction history and chain state during live calls. The chain_rpc_request tool lets you inspect on-chain state across 9 networks without switching to Etherscan or a block explorer. This is the right call if your support volume is under 50 tickets a week and agents already know how to read transaction hashes. If you're triaging hundreds of tickets daily or need automated fraud detection, the 15-tool surface area won't scale—you'd want a dedicated blockchain analytics platform. For small teams where one person handles wallet questions and speed matters more than automation, this MCP turns a 3-tab workflow into a single Switchy thread.

When compliance reviews delegation without vendor dashboards

A 4-person DAO tooling team delegates spending authority to agent wallets and needs quarterly audits of who can spend what. The get_wallets tool returns every agent wallet with its spend policy and session status in one call. This MCP is the move if your compliance checklist is a spreadsheet someone updates once a quarter and you're already using Base Account for delegation. The OAuth2 flow means the auditor authenticates once and pulls fresh data without asking engineers for API keys. If your org runs multi-sig wallets on Gnosis Safe or needs real-time policy enforcement across 20+ chains, the 9-network limit and lack of write permissions make this a non-starter. For small teams where delegation is new and the audit is a human reading a list, this MCP gets you compliant without building a custom dashboard.