Skip to main content
Glama
Codex MCP Server

Codex MCP Server

Official
by Codex-Data

Codex MCP Server

An MCP server that provides enriched blockchain data from Codex. This server can be used with any MCP-compatible client like Claude Desktop.

Installation

# Clone the repository
git clone https://github.com/codex-data/codex-mcp.git
cd codex-mcp

# Install dependencies
pnpm install

# Build the project
pnpm build

Related MCP server: Codex Bridge MCP

Usage

To use the MCP Codex Server, you need to have a Codex API key. You can get your key from the Codex Dashboard.

Using npx (No Installation Required)

You can run the MCP Codex Server directly without installation using npx:

# Run the server in stdio mode (for CLI tools)
npx @codex-data/codex-mcp

Running the Server Locally

Start the server using stdio (for embedding in CLI tools):

pnpm start

For development with auto-reload:

pnpm dev

Integration with Claude Desktop

  1. Open Claude Desktop settings

  2. Go to the Developer tab and click "Edit Config"

  3. Add a new server configuration:

No installation:

{
  "mcpServers": {
    "codex-data": {
      "command": "npx",
      "args": ["-y", "@codex-data/codex-mcp"],
      "env": {
        "CODEX_API_KEY": "<your-codex-api-key>"
      }
    }
  }
}

Local installation:

{
  "mcpServers": {
    "codex-data": {
      "command": "node",
      "args": ["/path/to/codex-mcp/build/index.js"],
      "env": {
        "CODEX_API_KEY": "<your-codex-api-key>"
      }
    }
  }
}
  1. Replace /path/to/codex-mcp with the actual path to your installation

  2. Replace <your-codex-api-key> with your actual Codex API key

Connecting using Claude CLI

If you're using Claude CLI:

# Add the MCP server
claude mcp add codex-data -e CODEX_API_KEY=<your-codex-api-key> npx @codex-data/codex-mcp

# Start Claude with the MCP server enabled
claude

License

ISC

Available Tools

25 tools
filter_exchangesB

Get a list of exchanges based on various filters like volume, transactions, active users, etc.

Inputs: limit, offset, phrase, filters, +1 more.

filter_pairsC

Get a list of pairs based on various filters like volume, price, liquidity, etc.

Inputs: limit, pairs, offset, phrase, +3 more.

filter_tokensC

Filter tokens by various criteria

Inputs: limit, offset, phrase, tokens, +4 more.

get_detailed_pairs_statsB

Get bucketed stats for a given token within a list of pairs

Inputs: duration (required), networkId (required), pairAddresses (required), bucketCount.

get_detailed_pair_statsC

Get bucketed stats for a given token within a pair

Inputs: address (required), duration (required), networkId (required), statsType, +3 more.

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).

Inputs: networkFilter (required), limit, offset.

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)

Inputs: address (required), networkId (required), cursor.

get_liquidity_metadataB

Get liquidity metadata for a pair, including both unlocked and locked liquidity data

Inputs: address (required), networkId (required).

get_networksA

Get a list of all blockchain networks supported by Codex

Inputs: no named parameters.

get_network_statsC

Get metadata and statistics for a given network

Inputs: networkId (required).

get_network_statusC

Get the status of a specific blockchain network

Inputs: networkId (required).

get_pair_metadataB

Get metadata for a pair of tokens, including price, volume, and liquidity stats over various timeframes.

Inputs: address (required), networkId (required), statsType, quoteToken.

get_token_balancesB

Get token balances for a wallet (Codex Growth and Enterprise Plans only)

Inputs: networkId (required), walletAddress (required), cursor, filterToken, +1 more.

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.

Inputs: to (required), from (required), address (required), networkId (required), +8 more.

get_token_chart_urlsC

Chart images for token pairs (Codex Growth and Enterprise Plans only)

Inputs: networkId (required), pairAddress (required), quoteToken.

get_token_eventsC

Get transactions for a token pair

Inputs: query (required), limit, cursor, direction.

get_token_events_for_makerB

Get a list of token events for a given wallet address

Inputs: query (required), limit, cursor, direction.

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)

Inputs: address (required), networkId (required), sort, cursor.

get_token_infoC

Get detailed information about a specific token

Inputs: address (required), networkId (required).

get_token_pairsB

Get a list of pairs for a token

Inputs: address (required), networkId (required), limit.

get_token_pairs_with_metadataA

Get pairs with metadata for a specific token

Inputs: address (required), networkId (required), limit.

get_token_pricesB

Get real-time or historical prices for a list of tokens

Inputs: inputs (required).

get_tokensC

Get detailed information about multiple tokens

Inputs: ids (required).

get_token_sparklinesB

Get a list of token simple chart data (sparklines) for the given tokens

Inputs: addresses (required), networkId (required).

get_top_10_holders_percentC

Get the percentage of tokens held by top 10 holders

Inputs: address (required), networkId (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.2/5.0

    Scored across 25 tools

    Disambiguation4/5

    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.

    Naming Consistency5/5

    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.

    Tool Count4/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers