One wallet, two configurations: why Coinbase’s CLI and MCP differ
Coinbase Agentic Wallet behaves differently through its CLI and through its MCP server. This is what each configuration’s documentation says in the 13 Oct 2026 snapshot, quoted as recorded.
Through the CLI
The CLI configuration is recorded as Authenticated awal CLI; sends by chain, swaps on Base mainnet.
In this snapshot, its documented tasks are: check a wallet balance and carry out a transaction.
The execution entry reads USDC send on listed chains; swaps on Base mainnet only.
The index files it under Base only, and the entry says why: Combined send/trade filter uses Base mainnet, the shared documented network. USDC sends additionally support Base Sepolia, Polygon, Solana mainnet and devnet; trading does not.
How much it can do without asking isn’t settled. The approval stage for that execution is recorded as unknown: No inspected exact confirmation or threshold workflow.
Its limits are recorded as claimed: CLI overview advertises per-session and per-transaction caps.
The record adds This is a documented claim, not validated enforcement. MCP limit controls are separate.
Through the MCP server
The MCP configuration is recorded as Payments MCP plus companion wallet; excludes CLI send/trade.
In this snapshot, its documented tasks are: check a wallet balance and pay for a service.
General transactions are documented as not available: General fund transfers and trades are not exposed to MCP agents.
Paying for services is where it acts without asking each time. That payment is recorded at stage 5, no per-action approval, on the condition Funded wallet, permitted x402 payment within configured limits.
The payment entry lists Base, Polygon PoS and Solana.
The limits sit beside that stage. They are recorded as documented enforcement: User-set per-call and per-session payment caps.
Their recorded scope is MCP x402 service payments only
. The enforcement layer is recorded as unknown. One gap is noted: Precise enforcement layer and session reset rules not established.
Stage 5 does not mean limited or safe.
Why the index keeps them apart
Read as one product, the two could suggest that the CLI can pay for services unattended, or that the MCP server can trade. Neither inference follows from this snapshot. It records no payment task for the CLI, which isn’t a finding that the CLI can’t pay, and the approval stage for the CLI’s execution entry is recorded as unknown. The MCP server’s stage 5 is recorded for paying for services only, and its general transactions are a documented no. So each configuration is its own row, and a filter only matches when the task, chain and approval stage all hold for one task in one configuration.
In practice, filtering the comparison for Execute transaction at stage 5 doesn’t list the MCP server: its stage 5 belongs to paying for services.
Compare both configurationsWho documents paying for services
Before you connect either
These entries come from documentation checked on 13 Oct 2026. Nothing was installed or hands-on tested. Read the current documentation for the exact configuration you plan to use; nothing here is advice.
Sources
Every quote above comes from claims citing these pages. Each source supports only the claims that cite it.
- Coinbase — Prerequisites; CLI commands; Authenticating an agentic walletRetrieved
- Coinbase — What is Agentic Wallet CLI?; Capabilities; SecurityRetrieved
- Coinbase — Two ways to use; Which should I use?Retrieved
- Coinbase — How does it work?; What can agents do?; You stay in control ofRetrieved
- Coinbase — What it does; NotesRetrieved
Want the first email if delivery starts? Join the first-email listAtom feed