[Docs Bug/Feature Request]: Clarify EOA Wallet limitations and upgrade restrictions for Base MCP Onboarding

Start with the Base MCP page at base/docs/ai-agents/index and compare its wallet description with the reported EOA and upgraded-account behavior. Add a clear warning covering supported native Smart Wallets, unsupported EOA recovery phrases, and the proposed account-creation path, then preview the page to verify the notice is visible and accurate.

Problem

The current documentation for Base MCP states that Base MCP gives an AI assistant direct access to a user's "Base Account (the smart wallet powering the Base App)". However, the documentation lacks critical technical distinctions regarding Externally Owned Accounts (EOAs) that have been imported into or interact with the Base App ecosystem

During community onboarding attempts, users utilizing native 12-word EOA seed phrases encountered blocking errors when attempting wallet recovery and passkey generation through the Base App MCP interface.

Current Behavioral Discrepancies vs. Docs

1. Recovery Phrase Generation: Native Base App Smart Wallets generate a distinct 13-word recovery phrase used for MCP validation. Normal EOA wallets use a 12-to-24-word phrase, which causes an unhandled schema error (Recovery phrase error: Check the number of words entered...) in the Base App login redirect pipeline.

2. Upgraded EOA Limitations: Upgrading an existing EOA wallet to a Smart Wallet retains the original 12-word structure. It does not generate the 13-word recovery phrase or passkey credential required to handshake with Base MCP.

Recommendation

Proposed Documentation Improvements

To prevent user drop-off and support bottlenecks, we should add a Warning/Notice Block explicitly outlining wallet requirements to related path:
base/docs/ai-agents/index

Important Wallet Compatibility Requirements

Base MCP exclusively supports native Base Smart Wallet accounts initialized via email or passkey auth pipelines.

• Standard EOA Wallets: Traditional Externally Owned Accounts (utilizing standard 12-to-24-word seed phrases) cannot directly establish an MCP connection.
• Upgraded Accounts: If you upgrade an existing EOA wallet to a Smart Wallet interface, its underlying 12-word recovery structure is preserved. It will not generate the 13-word recovery phrase or device passkey configuration required for AI Agent orchestration.
• Solution: To use Base MCP features, you must generate a fresh Smart Wallet account using an explicit passkey or email profile stored in your active device browser.

Integrating EOA wallet addresses in the future.

This is beyond my capabilities, but if the team can do this, it would be great as Base could onboard many users without making things complicated by requiring users to manage multiple addresses.