← agentwallet.md

Best MCP Wallet Server for AI Agents

Updated for 2026 • 4 open-source servers compared
MCP Open Source Claude Cursor

MCP (Model Context Protocol) wallet servers expose crypto operations as tools any MCP-compatible AI client can call. Pick by chain coverage, swap support, and indexing depth. All four servers below are open-source and actively maintained by their respective protocol teams.

Quick comparison

Name Category Chains Custody Open Source Best for
Coinbase AgentKit MCP MCP EVM, Base, Solana Self-custody Wallet operations via MCP
Alchemy MCP MCP Multi-chain N/A (read-only) Blockchain data queries

Detailed breakdown

Coinbase AgentKit MCP
github.com/coinbase/agentkit
Wallet
Best for: Wallet operations via MCP protocol
The most comprehensive MCP server for active crypto operations. Provides tools for wallet creation, address management, balance queries, transaction signing, and direct blockchain interaction. Built by Coinbase with first-class support for Base and broader EVM ecosystems, plus Solana. Ideal when your AI agent needs to actually move funds, execute trades, or interact with smart contracts rather than just observe.
Alchemy MCP
github.com/alchemyplatform/alchemy-mcp
Data
Best for: Blockchain data queries via MCP
Leverages Alchemy's massive node infrastructure to serve fast, reliable blockchain data through MCP tools. Covers balance lookups, transaction receipts, contract state reads, NFT metadata, and event log filtering across multiple chains. Optimized for applications where your AI needs to answer "what happened on-chain" questions with low latency and high accuracy. Read-only by design—no signing capabilities.

Frequently asked questions

What is an MCP wallet server?

An MCP wallet server is a software bridge that exposes cryptocurrency operations—such as reading balances, signing transactions, querying blockchain data, and interacting with DeFi protocols—as standardized tools through the Model Context Protocol (MCP). MCP was developed by Anthropic to let AI assistants like Claude discover and call external capabilities dynamically.

A wallet server implements MCP so that any compatible client (Claude Desktop, Claude Code, Cursor, or other MCP hosts) can perform crypto operations without hardcoded integrations. The server handles the actual blockchain communication, private key management (where applicable), and protocol-specific logic, while the AI client simply invokes named tools with parameters.

For example, Coinbase AgentKit MCP provides wallet operations and Alchemy MCP offers blockchain data queries—both through the same uniform protocol.

Which MCP wallet server is best for Claude Code?

The best MCP wallet server for Claude Code depends on your specific use case, as each server specializes in different capabilities:

For active wallet operations—creating wallets, managing addresses, signing transactions, and executing trades—Coinbase AgentKit MCP is the strongest choice because it was purpose-built for wallet operations via MCP protocol and integrates with Coinbase's infrastructure.

For querying blockchain state, reading contract data, or building analytics dashboards, Alchemy MCP excels at blockchain data queries via MCP with its extensive node network coverage.

Both are open-source and can be configured simultaneously in Claude Code's MCP settings, so many users combine Coinbase AgentKit MCP for execution with Alchemy MCP for data intelligence.

Can MCP wallet servers sign transactions or only read?

MCP wallet servers vary in their capabilities: some support both read and write operations including transaction signing, while others are read-only.

Coinbase AgentKit MCP is explicitly designed for wallet operations via MCP protocol and supports full transaction lifecycle management—creating wallets, signing transactions, broadcasting to networks, and tracking confirmations. This makes it suitable for DeFi interactions, token transfers, and other state-changing operations.

In contrast, Alchemy MCP focuses on blockchain data queries via MCP, which are fundamentally read operations: retrieving balances, transaction histories, contract states, and event logs without requiring private key access.

The key distinction lies in whether the server manages private keys or connects to signing hardware/software. When configuring any MCP wallet server, review its tool manifest to confirm which operations require authentication and which are permissionless reads.