Codex MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CODEX_API_KEY | Yes | Your Codex API key. Obtain from https://dashboard.codex.io |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_networksA | Get a list of all blockchain networks supported by Codex |
| get_network_statusC | Get the status of a specific blockchain network |
| get_network_statsC | Get metadata and statistics for a given network |
| get_token_infoC | Get detailed information about a specific token |
| get_tokensC | Get detailed information about multiple tokens |
| get_token_pricesB | Get real-time or historical prices for a list of tokens |
| filter_tokensC | Filter tokens by various criteria |
| get_token_holdersA | Returns list of wallets that hold a given token, ordered by holdings descending. Also has the unique count of holders for that token. (Codex Growth and Enterprise Plans only) |
| get_token_balancesB | Get token balances for a wallet (Codex Growth and Enterprise Plans only) |
| get_top_10_holders_percentC | Get the percentage of tokens held by top 10 holders |
| get_token_chart_dataC | Returns bar chart data to track token price changes over time. Can be queried using either a pair address or token address. |
| get_token_chart_urlsC | Chart images for token pairs (Codex Growth and Enterprise Plans only) |
| get_latest_tokensA | Get a list of the latests token contracts deployed (Codex Growth and Enterprise Plans only). Note: This endpoint is only available on Ethereum, Optimum, Base, and Arbitrum networks (network IDs 1, 10, 8453, and 42161). |
| get_token_sparklinesB | Get a list of token simple chart data (sparklines) for the given tokens |
| get_token_eventsC | Get transactions for a token pair |
| get_token_events_for_makerB | Get a list of token events for a given wallet address |
| get_detailed_pair_statsC | Get bucketed stats for a given token within a pair |
| get_detailed_pairs_statsB | Get bucketed stats for a given token within a list of pairs |
| filter_pairsC | Get a list of pairs based on various filters like volume, price, liquidity, etc. |
| get_pair_metadataB | Get metadata for a pair of tokens, including price, volume, and liquidity stats over various timeframes. |
| get_token_pairsB | Get a list of pairs for a token |
| get_token_pairs_with_metadataA | Get pairs with metadata for a specific token |
| get_liquidity_metadataB | Get liquidity metadata for a pair, including both unlocked and locked liquidity data |
| get_liquidity_locksA | Get liquidity locks for a pair, including details about locked amounts, lock duration, and owner information (Codex Growth and Enterprise Plans only) |
| filter_exchangesB | Get a list of exchanges based on various filters like volume, transactions, active users, etc. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 25 tools
Most tools have distinct purposes (token info, holders, prices, networks, etc.), but a few are closely related and could be confused, such as get_token_pairs vs get_token_pairs_with_metadata, and get_detailed_pair_stats vs get_detailed_pairs_stats vs get_pair_metadata. Descriptions are clear enough to disambiguate with careful reading.
All tool names follow a consistent verb_noun snake_case pattern, primarily using get_ or filter_. This makes the API predictable and easy to navigate.
25 tools is at the upper end of the acceptable range, but the server covers a broad domain (tokens, pairs, networks, liquidity, events, exchanges) and each tool appears to serve a specific analytical need. The count feels appropriate for a comprehensive blockchain data API.
The tool set provides comprehensive read-only coverage for the domain: token metadata, prices, holders, pairs, liquidity, events, network status, and exchange filtering. There are no obvious missing operations for a data-focused MCP server.