Skip to content

docs: clarify EOA wallet limitations for Base MCP onboarding #1646

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wichlene wants to merge 2 commits into
base: master
Choose a base branch
from
+8 −0
Open

docs: clarify EOA wallet limitations for Base MCP onboarding #1646

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a974b33
docs: clarify EOA wallet limitations for Base MCP onboarding
wichlene Jun 19, 2026
cc4ef4c
docs: clarify EOA wallet limitations for Base MCP onboarding
wichlene Jun 19, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions docs/ai-agents/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,14 @@ import { WalletSetupDemo } from "/snippets/WalletSetupDemo.jsx"

Base MCP gives your AI assistant direct access to your [Base Account](/base-account) (the smart wallet powering the Base App). Connect once and your assistant can check balances, send funds, swap tokens, sign messages, execute contract calls, and pay x402-enabled APIs across multiple networks. Every write action requires your approval.

<Warning>
**Wallet compatibility:** Base MCP supports only native Base Smart Wallet accounts created through the email or passkey authentication flow. Standard Externally Owned Accounts (EOAs) cannot connect directly.

Native Base Smart Wallets are initialized with a 13-word recovery phrase and a device passkey configuration. Standard EOAs use a 12–24 word recovery phrase and do not produce the passkey configuration Base MCP expects, which results in schema errors.

Upgrading an existing EOA to a Smart Wallet does **not** resolve this: the account keeps its original recovery-phrase structure and will not generate the 13-word phrase or passkey configuration required to connect.
</Warning>

## Demo

<Visibility for="humans">
Expand Down