Coinbase Wallet MCP
for LuumenAI

Inspect wallets, check balances, and send onchain transactions as approved steps

Connect Coinbase Wallet MCP and Luumen can read your Base Account and agent wallets the way you would: portfolio value per asset, delegation status and spend policy, transaction history, token lookups, and read-only JSON-RPC calls. When a transfer, swap, signature, or payment is needed, Luumen shows the exact call first and waits for your approval. Authentication uses OAuth with dynamic client registration.

The Coinbase Wallet MCP toolbox

15 tools: 7 read, 8 write. Reads answer instantly. Writes require approval by default. Everything is logged.

  • ReadChain rpc requestMake a read-only JSON-RPC call to inspect on-chain state on a supported chain (arbitrum, avalanche, base, base-sepolia, bsc, ethereum, optimism, polygon, robinhood-chain).
  • ReadGet portfolioReturns total portfolio value and per-asset breakdown for a wallet address.
  • ReadGet request statusPoll the status of an approval request by requestId (returned by send, sign, swap, or send_calls).
  • ReadGet transaction historyReturns paginated transaction history in reverse chronological order for a single chain.
  • ReadGet walletsReturns the user's Base Account and all agent wallets with delegation status, spend policy, and session authorization.
  • ReadHelpReturns guidance for helping the user with protocol-specific tasks that aren't directly supported by this MCP.
  • ReadSearch tokensSearch for tokens by symbol or name on a single chain.
  • WriteComplete x402 requestComplete a previously initiated x402 payment after the user has approved it in their Base Account. Approval by default
  • WriteFundCreate a funding request to add money to (top up) the user's wallet. Approval by default
  • WriteInitiate x402 requestInitiate an HTTPS request to an x402-enabled endpoint. Approval by default
  • WriteSendSend native tokens or any ERC-20. Approval by default
  • WriteSend callsSubmit a batch of raw contract calls for user approval. Approval by default
  • WriteSignRequest a user-approved signature. Approval by default
  • WriteSwapSwap between tokens on a mainnet chain (testnets not supported). Approval by default
  • WriteWeb requestMake an HTTP GET or POST request to a whitelisted partner API. Approval by default

One prompt, start to finish

What a governed Coinbase Wallet MCP run looks like inside Luumen.

Questions

How does LuumenAI connect to Coinbase Wallet MCP?

Authorize once with OAuth 2.0. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.

Can LuumenAI change things in Coinbase Wallet MCP on its own?

Read actions answer immediately. Anything that writes — complete x402 request, fund, initiate x402 request, send, and more — is shown as a plan and requires approval by default, including the 5 actions classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.

Who gets access to the integration?

You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.

Is there an audit trail?

Every call to Coinbase Wallet MCP — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.

Put Coinbase Wallet MCP to work with Luumen

Connect in minutes. Every action scoped, approved, and audited from day one.