Gate DEX MCP

What Gate DEX MCP MCP server does

Gate DEX MCP MCP server exposes Gate’s decentralized exchange functions through the Model Context Protocol. It connects an MCP client to the remote https://api.gatemcp.ai/mcp/dex endpoint and provides authenticated wallet operations, transaction preparation, swap execution, token discovery, and DEX market data.

The service supports wallet addresses and balances for EVM and Solana chains. Agents can retrieve portfolio value, sign messages or raw transactions, estimate gas, preview transfers and token approvals, broadcast signed transactions, and review transaction or swap history.

How it works

The DEX endpoint uses Streamable HTTP, with SSE available as a fallback. Authentication is handled through either Google OAuth or Gate OAuth. The login tools can start an OAuth flow, poll for completion, exchange an authorization code for access, and revoke the current session.

Once authenticated, an agent can use the wallet and transaction tools against the connected session. Swap execution can be performed as a combined operation that obtains a quote, builds the transaction, signs it, and submits it. Separate tools expose the quote and swap-order status when an application needs more control over the workflow.

Setup and configuration

Configure an MCP client with the DEX URL:

{
  "mcpServers": {
    "Gate-Dex": {
      "url": "https://api.gatemcp.ai/mcp/dex",
      "headers": {
        "x-api-key": "MCP_AK_8W2N7Q",
        "Authorization": "Bearer ${GATE_MCP_TOKEN}"
      }
    }
  }
}

The repository also shows a mcporter configuration using the same endpoint. OAuth is required for the DEX surface, and the available login tools support Google and Gate authorization. The example configuration uses GATE_MCP_TOKEN for the bearer token after authorization. Cursor, Claude CLI, and other MCP-compatible clients can connect through their HTTP MCP configuration; the README specifically documents Cursor and Claude CLI setup.

Tools and capabilities

Gate DEX MCP MCP server groups its tools into several practical areas:

• Authentication: Start and complete Google or Gate OAuth login, then log out and revoke the session.
• Wallets: List EVM and Solana addresses, retrieve token balances with prices, calculate total assets and 24-hour change, and sign messages or raw transactions.
• Chains and transactions: Inspect chain IDs and capabilities, estimate gas, preview transfers and approvals, create an unsigned Solana SOL transfer, and broadcast signed transactions.
• Swaps: Request route and price-impact quotes, execute a one-click swap, and query an existing swap order by ID.
• History: Retrieve transaction, swap, and bridge records.
• Market and token data: Query candlestick data, trading statistics, liquidity-pool events, swap and bridge token lists, token fundamentals, gainers and losers, and tokens filtered by creation time.

Limitations and notes

This listing describes the DEX endpoint, not every Gate MCP surface. Gate also documents separate endpoints for public market data, centralized-exchange trading, coin information, news, and research; those functions are outside this DEX listing.

Authenticated wallet and transaction operations require OAuth. Signing and submission tools can act on-chain, so an integrating agent should distinguish read-only queries from operations that authorize or broadcast transactions. The available chain set, token availability, and transaction behavior depend on the supported Gate DEX networks and the selected chain.