TL;DR: Crypto APIs runs MCP servers that give your AI agent the same blockchain infrastructure a production backend uses. Connect to our remote server at https://ai.cryptoapis.io/mcp with your API key, or run single packages locally with npx. Your agent can read balances, transactions, blocks and fees, manage webhooks, prepare and simulate transactions, run AML checks and broadcast. Your private keys stay on your machine: the signer package makes no network calls at all.
Ask an AI assistant for the balance of a Bitcoin address and it'll usually guess, or send you to a block explorer. Give it a blockchain MCP server and it calls a real API, gets the answer and shows its work. That's the whole idea behind the Model Context Protocol. One standard way for AI clients to find tools and call them. No glue code.
What is an MCP server?
The Model Context Protocol (MCP) is an open protocol, introduced by Anthropic in November 2024, that connects AI applications to outside tools and data. An MCP server publishes a list of tools, each with a name, a description and an input schema. Your AI client reads that list, picks the tool that fits your request and calls it. Claude, Cursor, Windsurf and n8n all speak MCP.
A blockchain MCP server wraps blockchain APIs as tools. The model doesn't have to remember endpoints or chain-specific formats anymore. It picks a tool like address balance, transaction details or fee recommendations, fills in the parameters and gets structured JSON back.
Option 1: our remote MCP server
This is the fastest start. We host a remote server that puts all 14 tool packages, 50 tools in total, behind one endpoint over streamable HTTP. You don't install anything. Your client sends your API key in the x-api-key header.
In a client that takes a URL and headers, such as Cursor, your config looks like this:
{
"mcpServers": {
"cryptoapis": {
"url": "https://ai.cryptoapis.io/mcp",
"headers": { "x-api-key": "YOUR_API_KEY" }
}
}
}
You can also connect to a single product with /mcp/{product}, for example https://ai.cryptoapis.io/mcp/address-latest if you only want balances. Fewer tools mean faster start-up and a smaller context for the model. That matters once your agent juggles several servers at a time.
Option 2: local packages with npx
Every product is also a standalone, open-source package on npm under the @cryptoapis-io scope: Address Latest, Address History, Block Data, Transactions Data, Contracts, Blockchain Fees, Market Data, HD Wallet, Blockchain Events, Prepare Transactions, Simulate, Signer, Broadcast and Utils. Each one runs with a single command, so there's nothing to clone or build. Add the ones you need to your Claude Desktop, Cursor or Windsurf config:
{
"mcpServers": {
"cryptoapis-address-latest": {
"command": "npx",
"args": ["-y", "@cryptoapis-io/mcp-address-latest", "--api-key", "YOUR_API_KEY"]
}
}
}
Local packages use stdio by default. For n8n or your own integration, start a package in HTTP mode with --transport http --port 3000 and it serves /mcp plus a /health check.
What can your AI agent do with it?
- Read blockchain data. Current balances, nonces and recent transactions for Ethereum and other EVM chains, Bitcoin and other UTXO chains, Solana, XRP and Kaspa. Full history for synced addresses. Transaction details, internal transactions, token transfers and logs, blocks by height or hash, and token and contract data.
- Price and estimate. Fee recommendations, EIP-1559 estimates and gas limits, plus asset prices and exchange rates.
- Watch addresses. Create and manage Blockchain Events webhooks for confirmed and unconfirmed coin and token transfers, new blocks and confirmations.
- Work with HD wallets. Sync an xPub, derive receiving addresses and read balances and transactions across the whole wallet.
- Move funds without handing over keys. Prepare an unsigned transaction, simulate it, sign it locally, then broadcast.
- Check counterparties. Run AML Verify Address or Screen Transaction before your agent sends to an address or credits a deposit.
Keys and safety: what your agent can't do
You don't let a model near money without guardrails. So we built in 3. Here they are.
- Signing stays local.
@cryptoapis-io/mcp-signersigns EVM, UTXO, Tron and XRP transactions on your machine. It makes no API calls and doesn't need an API key. Your private key never leaves your process, and we only ever see the signed transaction. - State-changing actions ask first. Broadcasting, creating or deleting a webhook, and syncing an address or HD wallet don't run on the first call. Your agent gets a confirmation step, has to bring the request back to you, and repeats the call with a one-time token that expires after 60 seconds.
- No extra access. The MCP tools call the same public REST API that's on our developer portal. Your agent can do exactly what your API key allows, nothing more. Credits used and credits left come back with every response, so your agent can tell you what a task cost.
A real workflow: pay an invoice in USDT
- You ask: "Pay this invoice from our treasury address on Ethereum."
- The agent checks the treasury balance and the current fee recommendations.
- It screens the recipient with AML Verify Address and tells you the risk band.
- It prepares an unsigned ERC-20 transfer and simulates it, so you see the outcome and the gas before anything's signed.
- The signer package signs it locally with your key.
- The agent asks you to confirm, broadcasts, and hands back the transaction hash.
Every step is a documented API call you can audit later. No black box. Each response also reports the credits it used.
FAQ
What is a blockchain MCP server?
It's an MCP server that exposes blockchain APIs as tools an AI client can call: balances, transactions, blocks, fees, webhooks and transaction building, returned as structured data the model can reason over.
Which AI clients work with the Crypto APIs MCP servers?
Any MCP-compatible host, including Claude, Cursor, Windsurf and n8n. Our remote server needs a client that supports streamable HTTP. The local packages run over stdio or HTTP.
Does the AI agent get access to my private keys?
No. Transactions are prepared unsigned and signed locally by the signer package, which runs on your machine and makes no network calls. Only the signed transaction gets broadcast.
Is the Crypto APIs MCP server in the official MCP Registry?
Yes. It's listed as io.github.CryptoAPIs-io/mcp. You can read more in our registry announcement.
Connect your agent
Our MCP Servers documentation lists every package, its tools and the product-scoped endpoints. Using n8n? Start with the n8n MCP Client guide. Everything your agent calls is the Crypto APIs Blockchain API, so the same key works in your backend and in your agent.