Skip to main content
There are two ways to pull live DexPaprika data into n8n, and both are keyless:
  • The dedicated n8n-nodes-dexpaprika community node gives you typed operations (token prices, pools, OHLCV, search) you can drop straight into a workflow or hand to an AI Agent as a tool.
  • The built-in MCP Client Tool node connects an AI Agent to all 17 DexPaprika tools over the hosted MCP server with nothing to install.
Use the community node when you want explicit, deterministic steps in a workflow. Use the MCP Client Tool when you want a model to pick from the full tool set on its own.

​
Option 1: the DexPaprika community node

n8n-nodes-dexpaprika is published on npm and carries the n8n-community-node-package tag, so it shows up in n8n’s community node search.

​
Install

On a self-hosted n8n instance:
  1. Go to Settings > Community Nodes.
  2. Click Install.
  3. Enter n8n-nodes-dexpaprika and confirm.
The DexPaprika node then appears in the node panel.
Community nodes install on self-hosted n8n. We are submitting the node to the n8n Creator Portal for the verified badge, which also makes verified nodes available on n8n Cloud.

​
Operations

The node covers three resources:
  • Token: search, get details, get USD prices for up to 10 tokens at once, get top tokens on a network.
  • Pool: get top pools on a network, get pool details, get historical OHLCV candles.
  • Network: list networks, list DEXes on a network, get platform stats.
It is also marked usableAsTool, so you can wire it into an AI Agent node’s Tool input and let the agent call these operations directly.

​
Option 2: the built-in MCP Client Tool node

If you would rather not install anything, n8n’s MCP Client Tool node connects an AI Agent to the hosted server and exposes all 17 tools.
  1. In your workflow, add an AI Agent node (Tools Agent).
  2. Add an MCP Client Tool node and connect its output into the AI Agent node’s Tool input.
  3. On the MCP Client Tool node, create an MCP credential:
    • Transport: SSE
    • SSE Endpoint: https://mcp.dexpaprika.com/sse
    • Authentication: None
  4. Set Tools to Include to All.
The agent can now call any of the 17 DexPaprika tools when it needs live data.
Use the SSE transport. n8n also has an HTTP Streamable option, but an open issue (n8n-io/n8n#24967) reports the transport selector being ignored on some builds, so prefer SSE until it is confirmed fixed on your version.

​
Tools and the rationale field

The hosted server exposes all 17 DexPaprika tools: networks, pools, tokens, OHLCV, transactions, and cross-chain search. See the MCP tools reference for the full list. Every read tool takes a required rationale string. It is part of each tool’s schema, so the agent model fills it automatically. If you drive the agent with a smaller model and hit validation errors, add an instruction telling it to include a short rationale.

​
Example

Wire either node into a Tools Agent and prompt it with, for example, “What are the top 5 pools on Base by 24h volume?” The agent calls the top-pools operation and returns live results, which you can pass to any downstream n8n node (a message, a spreadsheet, a database).

​
Resources

​
FAQs

No. The hosted server and the community node both read keyless. A free registered key or Pro plan raises your rate and monthly quota; see rate limits.
The community node gives typed operations you can place directly in a workflow or attach to an AI Agent. The built-in MCP Client Tool needs no install and exposes all 17 tools to an agent. Pick the node for deterministic steps, the MCP Client Tool for open-ended agent use.
On self-hosted n8n, go to Settings > Community Nodes, click Install, and enter n8n-nodes-dexpaprika. Verified nodes are also available on n8n Cloud; our Creator Portal submission is in progress.
Use SSE (https://mcp.dexpaprika.com/sse) for now. HTTP Streamable exists but has a known transport-selection bug on some n8n builds.