Alchemy MCP Server logo

Alchemy MCP Server

by alchemy

Connects AI agents to Alchemy blockchain APIs for token, NFT, wallet, transfer, transaction, and swap operations.

Install Alchemy MCP Server

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "alchemy-alchemy-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@alchemy/mcp-server"
      ],
      "env": {
        "ALCHEMY_API_KEY": "YOUR_VALUE_HERE",
        "AGENT_WALLET_SERVER": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y @alchemy/mcp-server

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 1mo ago.

Overview

Alchemy blockchain APIs are exposed locally through the alchemy/alchemy-mcp-server MCP server over STDIO. It provides tools for token prices, historical data, multichain balances, transaction history, transfers, NFTs, transactions, and swaps. Local use requires an Alchemy API key, while sending transactions or swapping also requires a configured wallet agent server. This repository is legacy and not actively maintained; new users should prefer Alchemy's hosted OAuth server.

Use cases

  • Query token prices and historical market data
  • Inspect multichain wallet balances and NFT holdings
  • Review address transactions and filtered asset transfers
  • Send blockchain transactions through a configured wallet agent
  • Execute token swaps through supported DEX protocols

Key features

  • Token prices by symbol or contract address
  • Historical price queries with date and time-frame filters
  • Multichain token and NFT ownership lookups
  • Transaction history and asset transfer filtering
  • Smart Contract Account transactions and Uniswap swaps

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

20/20 checks healthy over the last 78d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 9d ago via OSV.dev · @alchemy/mcp-server (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars88Stargazers on the source repository.
npm downloads2kPackage downloads in the last 30 days.
Last commit1mo agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Directory activity3 viewsConfig copies, upvotes, and views on AllMCPs.

How Alchemy MCP Server works

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:

config.json
{
  "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.

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.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Alchemy MCP Server

Run it through an MCP client's STDIO configuration with `npx -y @alchemy/mcp-server`, and provide the `ALCHEMY_API_KEY` environment variable.

Yes. The README provides a Claude Desktop configuration using the local STDIO package. Claude Desktop can also connect to Alchemy's hosted HTTP server.

The local server requires an Alchemy API key in the `ALCHEMY_API_KEY` environment variable.

Yes, but both functions require a configured wallet agent server specified with `AGENT_WALLET_SERVER`.

No. It is labeled legacy and not actively maintained. Alchemy recommends its hosted MCP server for new users.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewAlchemy MCP Server AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/alchemy-alchemy-mcp-server?style=directory)](https://allmcps.com/mcp/alchemy-alchemy-mcp-server)
HTML Embed
<a href="https://allmcps.com/mcp/alchemy-alchemy-mcp-server"><img src="https://allmcps.com/api/badge/alchemy-alchemy-mcp-server?style=directory" alt="Alchemy MCP Server on AllMCPs" /></a>