Jump to
Ctrl
+
/

n8n MCP Client

Use Crypto APIs MCP in n8n Workflows

Connect any Crypto APIs MCP server to n8n's AI Agent node via the built-in MCP Client Tool. This lets the AI agent autonomously call blockchain tools — fetching balances, estimating fees, looking up transactions, and more — as part of your automated workflows.

How It Works

MCP (Model Context Protocol) is an open standard that lets AI agents discover and call tools dynamically. Each Crypto APIs MCP server exposes a set of blockchain tools over HTTP. n8n's MCP Client connects to these servers so the AI Agent can use them on demand.

Setup

1. Start the MCP server in HTTP mode:

npx @cryptoapis-io/mcp-market-data --transport http --api-key YOUR_API_KEY --port 3000

2. Wire it into your n8n workflow:

  • Add an AI Agent node
  • Under the agent's Tools section, click + Tool and select MCP Client
  • Set the SSE URL to http://localhost:3000/mcp

The AI Agent will automatically discover all available tools and call them as needed.

Using Multiple MCP Servers

Each server defaults to port 3000. Assign different ports when running several at once:

npx @cryptoapis-io/mcp-market-data --transport http --api-key YOUR_API_KEY --port 3000
npx @cryptoapis-io/mcp-blockchain-fees --transport http --api-key YOUR_API_KEY --port 3001
npx @cryptoapis-io/mcp-transactions-data --transport http --api-key YOUR_API_KEY --port 3002

Add a separate MCP Client Tool in n8n for each server, pointing to its respective port.

Hosted Option — No Self-Hosting Required

Crypto APIs provides an official hosted MCP endpoint:

https://ai.cryptoapis.io/mcp

Set this as the MCP Client URL in n8n and pass your API key via the x-api-key header. No local servers to run or manage.

Example Workflow Ideas

  • Portfolio tracker — Use Market Data + Address Latest to fetch token balances and live prices on a schedule, then send a summary via email or Slack.
  • Transaction monitor — Use Blockchain Events to set up a webhook for incoming transactions, trigger an n8n workflow on each event, and log details to a Google Sheet.
  • Fee alerts — Use Blockchain Fees on a cron to check gas prices and notify you when fees drop below a threshold.
  • Automated transfers — Chain Prepare TransactionsSigner (local) → Broadcast to build, sign, and send transactions end-to-end.

Notes

  • The Signer package is stdio-only (local signing) and does not support HTTP — use it as a standalone CLI step.
  • For production, run MCP servers as persistent processes (pm2, systemd, Docker) rather than npx.
  • Get your API key at cryptoapis.io.
Was this page helpful?
Yes
No
Powered by

On this page