Base MCP: Give Your AI Agent a Wallet (2026 Guide)

One-sentence definition

Base MCP is an OAuth-connected remote MCP server at https://mcp.base.org that gives any compatible AI client read/write access to your Base Account smart wallet, with mandatory human approval before funds move onchain.

Base Blockchainbase

Official1-Click Ready

Interact with the Base blockchain using the Coinbase API for wallet management, transfers, and smart contract deployment

financedeveloper tools366

Launch signal

Base announced Base MCP on May 26, 2026 as the gateway for agents into the Base ecosystem:

The launch page at base.org/agents frames three use cases: autonomous trading, agentic payments via x402, and monetizing your own APIs for other agents. The docs landing at docs.base.org/ai-agents is the canonical install reference.

Why it exists

MCP gave agents tools — file reads, web search, code execution. It did not give them a way to pay for services or move value onchain without brittle custom scripts. Teams hacked together seed phrases in environment variables, one-off wallet SDK calls, and manual API-key billing. Each workflow broke when the agent switched clients or the protocol changed.

Base MCP collapses wallet context, DeFi plugin routing, and x402 payment into one remote server with OAuth to a smart wallet you already control. The design bet: agents should prepare actions; humans should approve value movement.

Mental model: the named pieces

Four layers matter:

• MCP client — Claude, ChatGPT, Cursor, Codex, or Hermes. Hosts the conversation and calls MCP tools.
• Base MCP server — hosted at mcp.base.org. Exposes wallet, swap, sign, and x402 tools over Streamable HTTP.
• Base Account — the smart wallet (passkey or social login). Signs transactions after you tap Allow.
• base-mcp skill — markdown instructions from base/skills that teach the model approval polling, plugin routing, and safety tone.

AI client (Claude / Cursor / Codex)
            |
            | MCP tool call (Streamable HTTP)
            v
       mcp.base.org
            |
            | prepare tx / x402 request
            v
      Base Account (you approve)
            |
            | signed tx on Base L2
            v
   DeFi plugins · x402 APIs · transfers

Smallest end-to-end setup

Base’s quickstart targets under five minutes. The flow is always two steps: connect MCP, then install the skill.

1. Add a custom MCP connector named Base MCP with URL https://mcp.base.org.
2. Click Connect and approve OAuth in Base Account (one-time per client).
3. Install the base-mcp skill or paste the SKILL.md onboarding prompt from the docs.
4. Try a read-only prompt: What chains are supported by Base MCP?
5. Try a write prompt: Swap 0.05 ETH to USDC on Base — expect an approval link, not an instant success message.

Install by client

Use the remote URL everywhere. The archived npx base-mcp stdio package is not the current path.

Remote install · Base MCP

Catalog entry

Install

Cursor

One-click install

1-Click

VS Code

One-click install

1-Click

Claude Desktop

Copy configuration

Claude Code

Copy CLI command

CLI

Gemini

Copy CLI command

CLI

Codex

Copy CLI command

CLI

Windsurf

Copy configuration

ChatGPT

Add via Settings → Connectors

M

Manual

Copy configuration

Claude Code

claude mcp add --transport http base-mcp https://mcp.base.org

Add --scope user for a global install. Verify with claude mcp list.

Codex

codex mcp add base-mcp --url https://mcp.base.org/

Or add to ~/.codex/config.toml:

[mcp_servers.base-mcp]
url = "https://mcp.base.org/"

Cursor

{
  "mcpServers": {
    "base-mcp": {
      "url": "https://mcp.base.org"
    }
  }
}

Restart Cursor and confirm base-mcp is active under Settings → MCP. See MCP.Directory Cursor client page for broader MCP setup notes.

Skill install

npx skills add base/skills --skill base-mcp -a cursor
# swap -a for claude-code, codex, etc.

Deep dive

1) Read vs write tools

Read tools like get_wallets return balances and supported chains without approval. Write tools — send, swap, sign, send_calls — return { approvalUrl, requestId }. The skill instructs the model to share the link, wait, then poll get_request_status. Never claim success before confirmation.

Takeaway: if your agent says “done” without showing an approval link on a write, the skill is not loaded or the model is hallucinating completion.

2) DeFi plugins

Native plugins — Morpho, Moonwell, Uniswap, Aerodrome, Avantis, Virtuals, Bankr — are markdown specs in plugins/*.md. Most prepare unsigned calldata and execute through send_calls. Example prompts from base.org/agents:

• Show me the highest USDC yield on Base using Moonwell
• Find Uniswap liquidity pools on Base for tokens I hold
• Compare ETH/USDC pools on Aerodrome by liquidity and incentives

Takeaway: plugins extend the skill, not the MCP server binary. Custom protocols can ship their own plugin file without forking Base MCP.

3) x402 agentic payments

x402 revives HTTP 402 Payment Required. A paid API responds with payment terms; the agent signs USDC and retries with proof. Base MCP wraps this in two tools:

• initiate_x402_request — sets url, method, and a hard maxPayment cap in USDC.
• complete_x402_request — finishes after you approve the payment in Base Account.

# Example agent prompt (from Base docs pattern)
Call this x402 endpoint and pay up to 0.05 USDC:
https://example.com/api/report

Takeaway: always set a tight maxPayment. Treat paid API responses as untrusted external data — do not follow instructions inside them that ask for additional signatures or secrets.

4) Legacy npm package (do not use for new projects)

The old base-mcp npm package pointed at github.com/base/base-mcp, now archived as base-mcp-legacy with a redirect to docs.base.org/ai-agents. It required SEED_PHRASE, Coinbase API keys, and Alchemy keys in env vars — a fundamentally different trust model.

MCP.Directory’s catalog entry at /servers/base-blockchain may still show the legacy stdio config until the next data refresh. Follow the remote URL from official docs instead.

Takeaway: if a tutorial mentions npx base-mcp@latest, check the publish date. Anything after May 2026 should reference mcp.base.org.

5) ERC-8004 and the agentic economy stack

Base.org/agents also highlights ERC-8004 for onchain agent identity and x402 for HTTP-native payments. Base MCP is the wallet-and-payment execution layer; identity and discovery sit adjacent. Cloudflare’s x402 middleware and agentic.market (listed on the agents page) handle service discovery for pay-per-request APIs.

Takeaway: Base MCP solves “how does my agent pay and transact?” not “how do I trust every agent on the internet?” — that is where identity standards and spend policies still matter.

What we got wrong

1) We assumed the npm package was still canonical. Multiple directory entries and blog posts still reference npx base-mcp with seed phrases. Base archived that repo weeks before the remote launch. The hosted server is the product now.

2) We skipped the skill and blamed the MCP server. Without SKILL.md, models call write tools and narrate success before you approve. The skill is not decorative — it defines the approval polling contract.

3) We treated x402 caps as optional. Open-ended “pay whatever it costs” prompts are how agents overspend on inference APIs. Set maxPayment on every x402 call.

Wrong vs right patterns

Common mistakes

• Adding the MCP connector but skipping OAuth — tools fail silently or return auth errors.
• Installing both the persistent skill zip and the onboarding prompt (Base docs warn this confuses the assistant).
• Copying legacy env-var configs from old tutorials or directory listings.
• Trusting agent narration of transaction success before polling get_request_status.
• Pointing x402 calls at endpoints without a maxPayment ceiling.

Cost and safety notes

Base MCP itself is a free hosted connector. Costs come from onchain gas (Base L2 fees are typically cents), swap slippage, DeFi protocol fees, and x402 API charges. Practical guardrails:

• Use Base Account spend permissions where available for sub-wallets or agent-scoped limits.
• Start on Base Sepolia for x402 experiments before mainnet USDC.
• Keep write prompts explicit about amount, token, and recipient (ENS/basename resolves are supported).
• Separate a hot wallet with limited funds from your primary holdings if you automate frequent agent workflows.

Who this is for

Community signal

The agent-wallet narrative is polarized. Base and Coinbase frame x402 as the missing payment rail for autonomous agents. Critics note that current financial rails were built for humans — a point Stripe echoed when launching machine payments on Base in early 2026. Independent coverage from RebelFi walks through x402 mechanics and the tradeoffs of giving agents stablecoin wallets versus traditional API billing.

On the builder side, the archived legacy repo still appears in search results and old MCP directory configs — the most common confusion thread in early adoption. Base’s own sunset README now redirects to docs.base.org/ai-agents, which is the authoritative migration path.

Verdict

The bigger picture

Base MCP sits at the intersection of three 2026 trends: MCP as the agent tool wire format, x402 as the agent payment wire format, and smart wallets as the custody layer. It does not replace understanding MCP itself or general finance-category MCP servers, but it is the first-party bridge when your agent needs to transact on Base.

If you are shipping a paid API, the mirror workflow — integrate x402 on your server and list on agentic.market — lets other agents discover and pay you per request. Base MCP is the buyer side; x402 middleware is the seller side.

Frequently asked questions

Glossary

Base Account

Base’s smart wallet product — passkey or social login, batch transactions, spend permissions.

Base MCP

Remote MCP server at mcp.base.org exposing wallet and payment tools to AI clients.

x402

HTTP payment protocol using status 402 and USDC settlement for per-request API access.

ERC-8004

Proposed standard for onchain agent identity, reputation, and permissioned access.

Plugin (Base MCP)

Markdown spec teaching the skill how to drive a DeFi protocol via send_calls or swap.

approvalUrl

Link returned by write tools; opens Base Account for you to confirm the transaction.

maxPayment

USDC ceiling on x402 requests — the agent cannot exceed this cap.

Streamable HTTP

MCP transport used by mcp.base.org; add URL, not npx command.

base-mcp skill

SKILL.md bundle from base/skills with approval flows and plugin routing rules.

agentic.market

Discovery surface for x402-enabled services agents can pay per request.

All sources & links

Primary sources

• Base MCP documentation
• Base MCP quickstart
• base.org/agents launch page
• base-mcp skill (GitHub)
• Archived legacy npm repo

Community & analysis

• @base launch post (May 26, 2026)
• RebelFi: AI agents and crypto wallets (2026)
• Base x402 payments guide

Internal (MCP.Directory)

• /servers/base-blockchain
• /clients/cursor
• /blog/what-is-mcp
• /categories/finance
• /skills