MCP Server

dex-skills includes a built-in MCP (Model Context Protocol) server that exposes all SDK functionality as tools. This lets AI assistants like Claude Code and Cursor interact with DEX launchpads through natural language.

Running the Server

Development

Terminal

npx tsx src/mcp-server.ts

Production

Terminal

node dist/mcp-server.js

Client Configuration

Add the following to your .mcp.json file to register the dex-skills MCP server with your client:

.mcp.json

{
  "mcpServers": {
    "dex-skills": {
      "command": "node",
      "args": ["dist/mcp-server.js"],
      "cwd": "/path/to/dex-skills",
      "env": {
        "SOLANA_RPC_URL": "https://api.mainnet-beta.solana.com",
        "BASE_RPC_URL": "https://mainnet.base.org",
        "BNB_RPC_URL": "https://bsc-dataseed.binance.org",
        "TRON_RPC_URL": "https://api.trongrid.io"
      }
    }
  }
}

Exposed Tools

The MCP server exposes eleven tools:

Tool	Description
dex_platforms	List all supported platforms and their capabilities.
dex_launch	Launch a new token on a specified platform. Requires a private key passed as a parameter.
dex_get_token	Get detailed information about a specific token by address.
dex_list_tokens	List tokens from a platform with optional sorting and pagination.
dex_buy	Buy tokens on a specified platform. Requires a private key and token address.
dex_sell	Sell tokens on a specified platform. Requires a private key and token address.
dex_trending	Get trending tokens from a platform with optional category filter.
dex_trade_history	Get trade history for a specific token on a platform.
dex_holders	Get token holder information. Currently Zora only.
dex_estimate_price	Get a price estimate for a potential trade. Currently Four.meme only.

Security Model

Private key handling

Private keys are passed as per-request parameters to the dex_launch, dex_buy, and dex_sell tools. They are never stored on the server, never written to disk, and never logged. Keys exist only in memory for the duration of the transaction signing.

RPC endpoint URLs are configured through environment variables set in the .mcp.json configuration. Read-only tools (dex_get_token, dex_list_tokens, dex_trending, dex_trade_history, dex_holders, and dex_estimate_price) do not require any credentials.

Compatible Clients

Claude Code -- Add to your project or global .mcp.json
Cursor -- Configure in Cursor Settings under MCP Servers
Other MCP clients -- Any client implementing the MCP specification can connect to this server