get_dex_pair_metricsLABSCO SUMMARY
On-chain metrics without touching SQL.
Dune's preset endpoints do the querying, so the set of questions is fixed but the answers arrive already shaped — pair liquidity, EigenLayer operator stats, Solana balances. It fits a research conversation better than an open-ended analytics session.
What it is
A bridge between Dune Analytics and an MCP client. It calls Dune's preset and echo endpoints rather than running SQL you write, and returns DEX pair metrics, EigenLayer operator and AVS statistics, and Solana wallet balances as structured JSON.
What you get
- Metadata and statistics for a token pair on a named chain
- The token pair holding the highest USD liquidity on a chain
- Token balances for a wallet address on Solana
- Statistics for a named EigenLayer AVS
- Statistics for every operator in an EigenLayer AVS
- JSON responses throughout, ready to be summarized or charted
Requirements
Node.js 16+ or a current Bun, and a Dune Analytics API key from your Dune account's API settings, handed to the server as an environment variable. The repository is cloned and run locally, with the client pointed at the built entry point.
Setup effort
Build from source — git clone https://github.com/ekailabs/dune-mcp-server.git
USE CASES
01
Sizing up a token pair before you trade
Name the pair and the chain and get its metadata and statistics back as JSON, without opening a Dune dashboard.
02
Finding where the liquidity actually is
Ask which pair on a chain holds the most USD liquidity, in the same thread where the trade is being thought through.
03
Checking what a Solana wallet holds
Hand over the wallet address and read its token balances back.
04
Reviewing an EigenLayer AVS
Pull the AVS's own statistics, then the statistics for every operator running it, to see how concentrated the set is.
5 tools
Listed in project docs. Your client may show a different list.
get_token_pairs_liquidityget_svm_token_balancesget_eigenlayer_avs_metricsget_eigenlayer_operator_metricsBEFORE YOU INSTALL
What to know first
Tools you get
5 tools named in the project's documentation.
Requires
Bun 1.0+
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
You clone this one yourself.
Server setup
TERMINAL
git clone https://github.com/ekailabs/dune-mcp-server.git
cd dune-mcp-server
bun installCreate a .env file in the project root based on .env.example, containing DUNE_API_KEY=<YOUR_DUNE_API_KEY>.
MCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"dune": {
"command": "bun",
"args": [
"<YOUR_PATH_TO_DUNE_MCP_SERVER>/src/index.ts",
"stdio"
]
}
}
}
