Gate Dex

Name: Gate Dex
Author: gateio-dev

by gateio-devcommunityv1.0.0

Gate MCP server exposes Model Context Protocol endpoints for Gate exchange data and actions, including public market data, trading, account management, DEX wallet/swap, coin info, and crypto news. Some endpoints are unauthenticated, while trading and DEX endpoints require Gate OAuth or Google/Gate OAuth.

From the registry: Gate DEX MCP for wallet auth, transfers, swaps, token info, market data, and RPC access.

GitHub Repository

Install & configure

Prerequisites

required
MCP-compatible client
Use an MCP client that supports Streamable HTTP or HTTP MCP connections.
optional
Gate account for private endpoints
A Gate account is required only when using the private exchange endpoint `/mcp/exchange` with OAuth2 authentication.
optional
Google or Gate account for DEX endpoint
Authentication is required for `/mcp/dex` using Google OAuth or Gate OAuth.

Install in your client

Paste into the AI you're chatting with — it will figure out the rest

Please install the `gate-dex` MCP server into my current AI client (that's you).

Required prerequisites (do these first if not already done):
- **MCP-compatible client** — Use an MCP client that supports Streamable HTTP or HTTP MCP connections.

Optional prerequisites:
- Gate account for private endpoints — A Gate account is required only when using the private exchange endpoint `/mcp/exchange` with OAuth2 authentication.
- Google or Gate account for DEX endpoint — Authentication is required for `/mcp/dex` using Google OAuth or Gate OAuth.

Canonical MCP server config (HTTP transport):
- url: `https://api.gatemcp.ai/mcp/dex`
- headers:
  - `x-api-key`: `<your-x-api-key>`
  - `Authorization`: `Bearer <your-gate-mcp-token>`

Note: Gate MCP exposes multiple HTTP endpoints. Public market data: `https://api.gatemcp.ai/mcp` (no auth). Private exchange trading/account: `https://api.gatemcp.ai/mcp/exchange` (OAuth2 required). DEX wallet/swap: `https://api.gatemcp.ai/mcp/dex` (Google or Gate OAuth required; README example also includes `x-api-key` and Bearer token headers). Info: `https://api.gatemcp.ai/mcp/info` (no auth). News: `https://api.gatemcp.ai/mcp/news` (no auth). Transport is Streamable HTTP with SSE fallback. Because this extraction is for Gate Dex, the canonical config targets `/mcp/dex`. The README does not document how to obtain the DEX `x-api-key`; it only shows it in an example header. OAuth for `/mcp/exchange` is performed interactively by the client rather than via static env vars.

Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.

Note: Gate MCP exposes multiple HTTP endpoints. Public market data: `https://api.gatemcp.ai/mcp` (no auth). Private exchange trading/account: `https://api.gatemcp.ai/mcp/exchange` (OAuth2 required). DEX wallet/swap: `https://api.gatemcp.ai/mcp/dex` (Google or Gate OAuth required; README example also includes `x-api-key` and Bearer token headers). Info: `https://api.gatemcp.ai/mcp/info` (no auth). News: `https://api.gatemcp.ai/mcp/news` (no auth). Transport is Streamable HTTP with SSE fallback. Because this extraction is for Gate Dex, the canonical config targets `/mcp/dex`. The README does not document how to obtain the DEX `x-api-key`; it only shows it in an example header. OAuth for `/mcp/exchange` is performed interactively by the client rather than via static env vars.