Gate MCP Server
Officialby gate
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GATE_API_KEY | No | Gate API key used by the local stdio server (gate-local-mcp / npm package `gate-mcp`) for authenticated access. Optional for public market data only. Example config: "env": { "GATE_API_KEY": "your-api-key", "GATE_API_SECRET": "your-api-secret" }. | |
| GATE_MODULES | No | Comma-separated list of modules to register on the local stdio server, e.g. "spot,futures". By default 384 tools across 22 modules are registered. Can also be given as --modules=spot,futures. | |
| GATE_BASE_URL | No | Optional override of the Gate API base URL for the local stdio server; add inside the `env` block as needed. | |
| GATE_READONLY | No | Enable read-only mode on the local stdio server, e.g. GATE_READONLY=true. Can also be given as --readonly. | |
| GATE_MCP_TOKEN | No | Bearer token used as the Authorization header ("Authorization": "Bearer ${GATE_MCP_TOKEN}") when connecting to the remote DEX MCP endpoint https://api.gatemcp.ai/mcp/dex. | |
| GATE_API_SECRET | No | Gate API secret used by the local stdio server (gate-local-mcp / npm package `gate-mcp`) for authenticated access. Optional for public market data only. |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
This server cannot be deployed
Maintenance
ActivityMaintained
ResponsivenessUnresponsive