Skip to main content
DexPaprika ships a standard MCP server, so it works with any MCP-compatible client, not just the ones with a dedicated guide. There are two ways to connect, and most clients accept the first. Point your client at the hosted server. No install, keyless.
/sse is the recommended transport. The same server also serves streamable HTTP at https://mcp.dexpaprika.com/streamable-http for clients that prefer it.

​
Option 2: Local server (stdio)

Run the server on your machine and have the client launch it:

​
Where to put the config

The mcpServers shape above is what Claude Desktop, Cursor, VS Code, Cline, and Windsurf use. The file location differs per client (for example Windsurf keeps it in ~/.codeium/windsurf/mcp_config.json, Cline in its MCP settings pane), so check your client’s MCP docs for the exact path, then paste one of the blocks above. A few clients use a different shape: We have step-by-step guides for Cursor, VS Code, Claude Code, and Codex. For anything else, the config above is all you need.

​
What you get

17 tools across networks, pools, tokens, OHLCV, transactions, and cross-chain search. Start with getCapabilities for the runtime manifest, or read the MCP tools reference.

​
FAQs

If it supports MCP, yes. DexPaprika is a standard MCP server. Use the remote url config for a hosted connection, or the stdio command config to run it locally, in whatever place your client keeps MCP servers.
Remote (url) is simplest: no install, always up to date, keyless. Choose local (stdio) if your client does not support remote MCP servers, or you want to run the server in your own environment.
No. The server is keyless for read access. A free registered key or Pro plan raises your rate and monthly quota; see rate limits.