Alchemy MCP Server

What alchemy/alchemy-mcp-server MCP server does

The alchemy/alchemy-mcp-server MCP server connects an MCP-compatible AI client to Alchemy's blockchain data APIs through a local STDIO process. It is intended for agents that need to inspect blockchain assets, wallets, transactions, transfers, and NFT holdings across supported networks.

Supported data tasks include retrieving token prices by symbol or contract address, querying historical prices by date range or natural-language time frame, checking multichain token balances, and listing address transaction history. The server can also return filtered asset transfers and NFT ownership or contract information.

Two action-oriented tools extend beyond read-only queries. sendTransaction sends transactions through Smart Contract Accounts, and swap executes token swaps through DEX protocols including Uniswap. Both depend on an external wallet agent server for signing and broadcasting operations.

How it works

An MCP client launches the local process over STDIO and passes requests to the configured tools. Blockchain data requests authenticate with an Alchemy API key supplied through the environment. The agent can then invoke individual methods based on a natural-language request, such as asking for recent transfers, ETH price history, or NFTs held by a wallet.

Transaction and swap requests use the AGENT_WALLET_SERVER endpoint to reach wallet infrastructure. The repository does not provide that wallet infrastructure itself, so those capabilities are unavailable unless the dependency is configured separately.

Setup and configuration

The documented quick-start configuration runs the package with npx:

{
  "mcpServers": {
    "alchemy": {
      "command": "npx",
      "args": ["-y", "@alchemy/mcp-server"],
      "env": {
        "ALCHEMY_API_KEY": "YOUR_API_KEY"
      }
    }
  }
}

Set ALCHEMY_API_KEY for blockchain data queries. Set AGENT_WALLET_SERVER as well if the client must send transactions or perform swaps. The README describes configuration for Claude Desktop and Cursor, and the hosted service separately documents connections for other clients.

Tools and capabilities

The local server documents methods for:

• Current token prices by symbol or address.
• Historical token prices using explicit dates, intervals, or flexible time frames.
• Token balances for addresses across multiple networks.
• Address transaction history and filtered asset transfers.
• Multichain NFT ownership with spam filtering.
• NFT contract data associated with multichain addresses.
• Smart Contract Account transactions through a wallet agent server.
• DEX token swaps through a wallet agent server.

The available tool set may differ from the hosted Alchemy MCP service because this repository is a legacy implementation.

Limitations and notes

The alchemy/alchemy-mcp-server MCP server is marked legacy and is not actively maintained. Alchemy states that the repository may be sunset and that its tool coverage and behavior can lag behind the hosted server. New deployments should therefore evaluate the hosted endpoint at https://mcp.alchemy.com/mcp, which uses OAuth and does not require a local installation or API key.

For the local package, an Alchemy API key is required for blockchain data access. Wallet actions are not self-contained: sendTransaction and swap will not work without a properly configured wallet agent server and its external signing and broadcasting support. The project is released under the MIT License.