Skip to main content

Integration overview

Install and configure the DexPaprika MCP server so AI tools can query networks, DEXes, pools, tokens, and search.

What is MCP?

MCP (Model Context Protocol) is an open protocol standard created by Anthropic that gives AI models a unified way to connect to external data sources and tools. The DexPaprika MCP server leverages this protocol to provide AI assistants like Claude with access to real-time crypto and DeFi market data, enabling advanced conversations about blockchain networks, decentralized exchanges (DEXes), liquidity pools, and tokens across the DeFi ecosystem.
Looking for an easier setup? If you prefer not to install anything locally, check out our DexPaprika Hosted MCP Server for instant access with zero installation required.

Installation Guide

Prerequisites

Before installing the DexPaprika MCP server, ensure you have:
  • Node.js (v16 or higher) installed on your system
  • npm (comes with Node.js) or yarn package manager
  • Claude Desktop or Cursor installed if you want to use the MCP server with these applications

Installation Options

Installing the DexPaprika MCP server globally makes it available throughout your system:
After installation, you can start the server by running:

Option 2: Use with npx (No Installation)

Alternatively, you can run the server directly without installation using npx:
This is useful for trying out the server without permanently installing it.

Verification

To verify that your installation was successful, run:
You should see the current version number of the DexPaprika MCP server.

Configuration

Claude Desktop Configuration

To use the DexPaprika MCP server with Claude Desktop:
  1. Download and install Claude Desktop if you haven’t already
  2. Locate your Claude Desktop configuration file:
    • macOS: ~/Library/Application\ Support/Claude/claude_desktop_config.json
    • Windows: %APPDATA%/Claude/claude_desktop_config.json
  3. If the file doesn’t exist, create it with the following content:
  1. If the file already exists, add the DexPaprika configuration to the existing mcpServers object:
  1. Save the file and restart Claude Desktop.
  2. To verify the configuration, open Claude Desktop and try asking a question about cryptocurrency data, such as “What are the top liquidity pools on Ethereum?”
Make sure you have the latest version of our package by running npm update -g dexpaprika-mcp

Cursor Configuration

If you’re using Cursor IDE with Claude:
  1. Download and install Cursor if you haven’t already
  2. Open Cursor and click on the Claude button in the sidebar
  3. Click on the settings icon (⚙️) and select “Add MCP Server”
  4. Fill in the following information:
    • Server name: dexpaprika
    • Type: command (select from dropdown)
    • Command to run: npx dexpaprika-mcp@latest
  5. Click “Add” to save the configuration
  6. Alternatively, Cursor will automatically use any MCP servers configured in Claude Desktop

Troubleshooting

If you encounter issues with the DexPaprika MCP server:
  1. Server not found errors:
    • Ensure the server is installed correctly using npm list -g dexpaprika-mcp
    • Try reinstalling with npm install -g dexpaprika-mcp
  2. Connection errors:
    • Check that your internet connection is active
    • Verify that no firewall is blocking the connection
  3. Configuration errors:
    • Double-check your configuration file syntax
    • Ensure the path to the configuration file is correct for your OS
  4. Command not found errors:
    • Ensure Node.js is installed and in your PATH
    • Try using the full path to the npm or npx executables

Features

The DexPaprika MCP server provides access to:
  • Blockchain network information across multiple chains
  • Decentralized exchange (DEX) data
  • Liquidity pool details and metrics
  • Token information and market data
  • Price and volume analytics for tokens and pools
  • Comprehensive search capabilities across DeFi entities

Available tools

New to the server? Call getCapabilities first. In one call it returns the full tool list, network name synonyms, recommended call sequences, and common pitfalls, so an agent can self-onboard before making any data calls.
The DexPaprika MCP server exposes 17 tools. Discovery and onboarding
  • getCapabilities - Agent onboarding: supported workflows, network synonyms, pitfalls, and recommended call sequences. Call this first.
  • getNetworks - List every supported blockchain network with 24h volume and indexing stats
  • getStats - Platform-wide totals: networks, DEXes, pools, and tokens indexed
  • search - Search across all networks for tokens, pools, and DEXes by name, symbol, or address
Pools
  • getNetworkPools - Top liquidity pools on a network, ranked by 24h volume by default
  • getNetworkPoolsFilter - Filter pools on a network by volume, liquidity, transactions, or creation time
  • getDexPools - Pools on a specific DEX within a network
  • getPoolDetails - Full details for one pool: tokens, price, liquidity, and 24h volume
  • getPoolOHLCV - Historical OHLCV (candlestick) data for a pool (1m to 24h intervals)
  • getPoolTransactions - Recent swaps for a pool (from/to are UNIX timestamps, capped to the last 7 days)
Tokens
  • getTokenDetails - Metadata and multi-timeframe price and volume metrics for one token
  • getTokenPools - Liquidity pools containing a specific token on a network
  • getTokenMultiPrices - USD prices for up to 10 tokens in one batched call
  • filterNetworkTokens - Filter tokens on a network by volume, liquidity, FDV, transactions, or creation time
  • getTopTokens - Top tokens on a network ranked by volume, liquidity, transactions, FDV, or 24h change
DEXes
  • getNetworkDexes - DEXes operating on a specific network
Feedback (hosted server only)
  • submitFeedback - Report a problem, unexpected response, or missing data back to the DexPaprika team
Agent notes: every read tool takes a required rationale string (1-2 sentences on what triggered the call). The pool and token list tools (getNetworkPools, getNetworkPoolsFilter, getTokenPools, getTopTokens, filterNetworkTokens) return rows under results with cursor pagination (has_next_page + next_cursor), and sort with canonical sort_by / sort_dir.
For full parameters, defaults, and return shapes for every tool, see the MCP tools reference.

Usage Examples

Once configured, you can ask Claude questions about DeFi data. Here are some example prompts:

General Market Data

  • “What are the top 5 liquidity pools across all networks by volume?”

Network-Specific Queries

  • “Which blockchain networks are supported by DexPaprika?”
  • “What are the top DEXes on the Solana network?”
  • “Show me the top 10 liquidity pools on Ethereum, ordered by volume.”

DEX and Pool Analysis

  • “What are the most active pools on Uniswap V3?”
  • “Show me details about the USDC/ETH pool on Uniswap V3.”
  • “Compare the trading volume between PancakeSwap and Uniswap.”

Token Information

  • “What’s the current price of SOL in the Raydium pool on Solana?”
  • “Find all pools that include the SHIB token.”

Search Functionality

  • “Search for pools related to ‘Bitcoin’”
  • “Find tokens with ‘Pepe’ in their name”

Advanced Queries

You can also ask Claude to perform more complex analysis:
  • “Compare the liquidity and volume of the top 3 DEXes on Ethereum”
  • “What’s the price difference of ETH between Uniswap and SushiSwap?”
  • “Show me the tokens with the highest price volatility in the last 24 hours”
  • “Analyze the trading volume trends for BNB on PancakeSwap”

Support

If you need further assistance, you can:

FAQs

No. The underlying DexPaprika API is public; the MCP server proxies public endpoints.
Claude Desktop reads claude_desktop_config.json; Cursor can add the same server via “Add MCP Server” or inherit Claude’s config.
Use absolute paths to uvx/npx in the config; many desktop apps don’t inherit shell PATH.
Yes. Every tool is a read-only data query; the server cannot modify on-chain state or your data, so no flag is needed.