Add it with one command
~/.codex/config.toml. Codex connects to it over streamable HTTP on the next run.
Or configure it manually
Add this to~/.codex/config.toml:
bearer_token_env_var or OAuth options are needed. The DexPaprika API is keyless.
Verify
Start Codex and ask a question that needs live data:What you get
The server exposes 20 tools covering networks, pools, tokens, OHLCV, transactions, and cross-chain search. See the MCP tools reference for the full list, parameters, and thegetCapabilities onboarding tool.
Resources
FAQs
Do I need an API key for Codex?
Do I need an API key for Codex?
No. The hosted DexPaprika MCP server is keyless, so there is no token or OAuth to configure. The hosted server runs tool calls on its own shared capacity, not on a plan of yours, so a key raises no limit there. The exceptions are the tools that need a paid plan, which run on your own Dev, Pro or Enterprise key; see the hosted server page. Limits for direct REST calls are on rate limits.
Which transport does Codex use?
Which transport does Codex use?
Streamable HTTP. Point Codex at
https://mcp.dexpaprika.com/streamable-http. The same server also serves SSE (/sse) for clients that prefer it.How do I remove the server?
How do I remove the server?
Delete the
[mcp_servers.dexpaprika] block from ~/.codex/config.toml, or run codex mcp to manage configured servers.