Dune MCP Server

If you already use Dune, the dune mcp server is the piece that lets your assistant work with it directly. Dune Analytics MCP Server.

What the server does

A Model Context Protocol (MCP) server that bridges Dune Analytics data to AI agents, providing access to DEX metrics, EigenLayer operators and AVS stats, and token balances on Solana. The tools utilize the preset endpoints and echo endpoints provided by Dune.

• get_dex_pair_metrics: Get essential metadata and statistical data for a given token pair on a specific chain
• get_token_pairs_liquidity: Find the token pair with the highest USD liquidity on a given chain
• get_svm_token_balances: Get token balances for a specific wallet address on Solana
• get_eigenlayer_avs_metrics: Get statistics for a specific AVS
• get_eigenlayer_operator_metrics: Get statistics for all operators in a specific AVS
• Data Formats — All results are returned in structured JSON format for easy processing

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• Description — Retrieves essential metadata and statistical data for a given token pair
• Input — - chain (string) - The blockchain to get the DEX stats for
• Output — JSON object containing DEX metrics

Credentials and setup notes

Configuration is passed through the environment: DUNE_API_KEY, OPENAI_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

• Node.js 16+ or Bun 1.0+ - A valid Dune Analytics API key (get one from Dune Analytics)

Installation

The server ships on npm as command., so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Where it fits

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Dune's toolset — Description, Input, Output — is a fair guide to whether it matches your workflow. It is maintained by ekailabs; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Dune's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.