get_walletsLABSCO SUMMARY
Wallet actions in the chat; signing stays where you can see it.
Every write tool returns an approval URL and a request ID: the agent shows you the link, you approve in Coinbase Wallet, and only then does get_request_status confirm completion. Reads skip that step, so balances and history come back straight away.
What it is
Coinbase's hosted Wallet MCP (formerly Base MCP) at https://mcp.base.org, connecting an AI assistant to your Coinbase Wallet, formerly the Base App. Reads answer immediately; every write returns an approval link you open in Coinbase Wallet before anything executes. There is nothing to install.
What you get
- Balances, portfolio value and wallet details
- Sending native tokens or ERC-20 tokens to an address, ENS name, basename or cb.id name
- Token swaps on supported mainnet chains
- EIP-712 typed data and plain message signing
- Batched contract calls under a single approval, over EIP-5792
- x402 payments in USDC on Base or Base Sepolia
- Transaction history, filterable by asset and paged through
- Partner plugins — Aerodrome, Morpho, KyberSwap, OpenSea, Virtuals and others — routed through the same approval flow
Requirements
A Coinbase Wallet and a client that takes a remote HTTP server. Add https://mcp.base.org as a custom connector in Claude or ChatGPT, or run claude mcp add --transport http base-mcp https://mcp.base.org; connecting sends you to Coinbase Wallet, where you click Allow once.
Setup effort
One command, then sign in — claude mcp add --transport http base-mcp https://mcp.base.org, then approve the OAuth sign-in
USE CASES
Paying someone by name instead of by address
Send to a basename, ENS name or cb.id — the name resolves, and you get an approval link before anything moves.
Swapping without leaving the conversation
Ask for the swap on a supported mainnet chain, read the plan, then approve it in Coinbase Wallet.
Signing in to a protocol that wants typed data
Sign EIP-712 typed data or a plain message from the assistant, through the same approve-then-confirm step.
Batching multiple contract interactions under one approval
Batch the interactions so the wallet asks once rather than once per call.
Paying for an x402 API the agent needs
Settle the request in USDC on Base or Base Sepolia instead of provisioning an API key.
Reviewing what the wallet has been doing
Browse past transactions, filter by asset, and page back through the history.
13 tools
Listed in project docs. Your client may show a different list.
get_portfoliosearch_tokenssendswapget_transaction_historysignsend_callsget_request_statusinitiate_x402_requestcomplete_x402_requestweb_requestchain_rpc_requestBEFORE YOU INSTALL
What to know first
Tools you get
13 tools named in the project's documentation.
Requires
- A Coinbase Wallet (formerly Base App) to approve the connection and every write
- A client that can reach a remote MCP server over HTTP
INSTALLATION
Connect your client
Server setup
claude mcp add
Claude Code
claude mcp add --transport http base-mcp https://mcp.base.orgHosted endpoint
https://mcp.base.orgAdd this hosted endpoint to your MCP client, then sign in.
MCP Clients
Codex
[mcp_servers.base-mcp]
url = "https://mcp.base.org/"Cursor
{
"mcpServers": {
"base-mcp": {
"url": "https://mcp.base.org"
}
}
}Claude.ai, Claude Desktop
https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=Coinbase%20Wallet%20MCP&connectorUrl=https%3A%2F%2Fmcp.base.orgChatGPT
Settings → Connectors → Create → New App; MCP Server URL https://mcp.base.org, Authentication OAuth, then click Allow in Coinbase Wallet
Hermes
mcp_servers:
base-mcp:
url: "https://mcp.base.org"