Base, Coinbase’s Ethereum layer-2 crypto network, launched Base MCP in May 2026. The tool lets AI clients such as ChatGPT, Claude, Codex, and Cursor propose wallet actions through a user’s Base Account. But does that mean you give AI clients control over your crypto when you connect?
This guide explains how Base MCP works, where the AI client’s role ends, and what users should check before they connect a wallet.
KEY TAKEAWAYS
➤ Base MCP connects Base Account to AI clients such as ChatGPT, so the assistant can prepare wallet actions from chat.
➤ Every write action still requires user approval through Base Account, and the assistant does not hold private keys.
➤ The main risk moves away from direct key exposure and toward approval fatigue, prompt injection, and malicious plugins
Can ChatGPT manage your crypto wallet through Base MCP?
ChatGPT can help prepare crypto wallet actions through Base MCP, such as balance checks, transfers, swaps, transaction reviews, and DeFi app interactions. However, Base says every write action still needs approval through Base Account. The AI assistant proposes the action, while the user reviews and confirms or cancels it before any crypto moves.
What is Base MCP?
Base MCP is a tool that connects a user’s Base Account with AI clients that support the Model Context Protocol. MCP is an open standard developed by Anthropic that helps AI tools exchange information with external apps and request actions through a structured system.
Base launched the tool on May 26, 2026. Its launch post lists ChatGPT, Claude, Codex, and Cursor as supported clients, while the official documentation outlines the wallet actions an agent can prepare for a user.
Base MCP is not a separate crypto wallet. It acts as the link between a user’s Base Account and a compatible AI client, so wallet requests can start from chat while approval remains with the user.
What Base MCP means for AI wallet access
Base MCP brings AI clients closer to wallet and DeFi workflows without turning them into custodians. Base’s launch post says the tool supports initial skill plugins for apps such as Uniswap, Morpho, Moonwell, Aerodrome, Bankr, Avantis, and Virtuals. That means a compatible AI client can prepare actions across several on-chain apps, not just show basic wallet information.
The key question is control. Base’s answer is no: the AI client can prepare the request, but Base Account still requires user approval before any write action goes through.
What can AI clients like ChatGPT do through Base MCP?
ChatGPT can prepare a defined set of wallet actions when connected through Base MCP. It does not gain custody of funds, and it does not sign transactions inside the chat window.
The same basic flow applies to other supported AI clients, such as Claude, Codex, and Cursor.
The table below summarizes core actions Base lists in its documentation.
| Base MCP action | What it means for the user |
| Check balance and portfolio | The assistant can read wallet balances and portfolio details on Base. |
| Send tokens | The assistant can prepare transfers for the native token or ERC-20 tokens. |
| Swap tokens | The assistant can help set up token swaps on supported pairs. |
| View transaction history | The assistant can pull past transactions for context or review. |
| Sign messages | The assistant can prepare message or typed-data signature requests. |
| Execute contract calls | The assistant can batch several contract interactions into one approval. |
| Pay x402 APIs | The assistant can pay x402-enabled APIs with USDC on Base or Base Sepolia. |
Each item above describes a prepared action. The agent assembles the request, then hands it to the user for review.
How does the approval flow work?
The approval step is where Base MCP differs from a hypothetical “AI controls my wallet” design. The agent does not push a transaction on its own. It opens a review window that the user must accept.
A typical write action works like this.
- The user asks ChatGPT or another connected AI client to perform a wallet task.
- Base MCP builds the proposed action from that request.
- Base Account opens a review window with the asset changes and key parameters.
- The user checks the token, amount, address, chain, and fee.
- The user confirms or cancels the request.
- Crypto moves only after a confirmed approval.
Base explains the same logic in its launch post. When the agent wants to run a transaction, it sends a link that opens Base Account, shows the expected asset changes, and lets the user accept or reject the action before it executes.
The Base documentation makes the same point in stricter language, stating that every write action requires user approval through the Base Account.
What can still go wrong with Base MCP?
A non-custodial design lowers some classic AI-wallet risks. For instance, the AI client does not receive a seed phrase, a private key, or signing rights inside the chat window. That reduces one major risk because a leaked private key can give attackers direct access to funds.
Other risks move to the approval layer and the broader agent stack.
- Approval fatigue can lead a user to confirm requests without reading them, which is the easiest way for a bad action to slip through.
- Prompt injection in shared content, links, or plugin outputs can push an AI agent toward actions the user did not ask for.
- Untrusted plugins or unofficial MCP servers can pretend to mimic Base, which makes connection-source checks important.
- Token approvals for swap and DeFi contracts carry their usual smart contract risk, which the AI layer does not reduce.
- Mistakes in chain selection, slippage, or wallet address still settle on-chain and remain hard to reverse.
That’s why you should ideally treat the AI client as a transaction drafter, not as a means for a safety check. The protection rests with the user reviewing each Base Account confirmation, not with the assistant deciding what is safe.
What to check before you connect
A short pre-flight list helps reduce the risks above:
- Confirm that the MCP connection points at the official Base source listed in Base documentation.
- Verify which AI client you are using and that it supports MCP write actions through a trusted account.
- Read each Base Account review window in full, not the chat summary alone.
- Cross-check token, amount, recipient, chain, and fee against your original request.
- Avoid open-ended prompts such as “handle my portfolio,” which can produce vague approvals.
- Start with small test amounts on a fresh action type or plugin.
- Disconnect the MCP integration when you no longer need it.
- Never paste seed phrases, private keys, or recovery details into any AI chat.
So, is Base MCP the right fit for you?
Base MCP could make sense if you want a faster way to start wallet actions from chat and are comfortable with manual checks for each approval. It is not a fit if you expect AI to manage funds for you or if you approve wallet prompts in a hurry. The tool can help draft transfers, swaps, and contract calls, but the final check is still on you.
A relatively safe approach would be to start with small amounts, verify every detail, and treat Base MCP as a convenience layer, not a substitute for your own review.
