DexScreener on-chain market data: search pairs, tokens, pools, trending tokens. No API key.
An MCP server that gives Claude, Cursor, and any MCP-compatible agent live on-chain market data from DexScreener — search pairs, inspect tokens and pools, and pull trending/boosted tokens across every chain.
No API key. No signup. The public DexScreener API is free (rate limited to ~60 req/min).
Most "MCP for X" repos are half-finished and break on the second request. This one ships with tests and graceful error handling so an agent can actually rely on it.
Ask things like:
| Tool | What it does |
|---|---|
search_pairs | Search pairs by symbol, name, or address across all chains |
get_token_pools | All liquidity pools for a token on a chain |
get_tokens | Market data for one or more token addresses (comma-separated) |
get_pair | Details for a specific pair/pool address |
latest_token_profiles | Freshly listed/updated tokens to watch |
top_boosted_tokens | Currently top-promoted / trending tokens |
No install needed. It runs straight from npm via npx.
Add to claude_desktop_config.json:
{
"mcpServers": {
"dexscreener": {
"command": "npx",
"args": ["-y", "dexscreener-mcp"]
}
}
}
Add to .cursor/mcp.json:
{
"mcpServers": {
"dexscreener": {
"command": "npx",
"args": ["-y", "dexscreener-mcp"]
}
}
}
Restart the client and the dexscreener tools appear.
npm install
npm run dev # run from TypeScript source over stdio
npm test # run the unit tests
npm run build # compile to dist/
Any chain DexScreener indexes — solana, ethereum, base, bsc, arbitrum, polygon, and more.
Pass the chain id as chainId.
MIT — see LICENSE.
I build custom MCP servers and AI systems (multi-agent, RAG, automation). Need a connector for your own API, or a full AI integration?
Built by Gleb.
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y dexscreener-mcpMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-glebenjoy-dexscreener-mcp": {
"command": "npx",
"args": [
"-y",
"dexscreener-mcp"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referencedexscreener-mcpnpmio.github.Glebenjoy/dexscreener-mcp works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.