mcp-coinglass
MCP server for coinglass platform
claude mcp add --transport stdio gpsxtreme-mcp-coinglass pnpm dlx mcp-coinglass \ --env COINGLASS_API_KEY="your_api_key_here"
How to use
This MCP server exposes a set of tools that let MCP-compatible clients query CoinGlass v4 futures data. Tools include open interest by symbol and exchange, historical liquidations (pair and aggregated by coin), global long/short ratio, current funding rates across exchanges, and real-time Hyperliquid whale alerts and positions. Clients send a tool name such as COINGLASS_OPEN_INTEREST or COINGLASS_LIQUIDATIONS_PAIR along with a JSON-structured params object, and receive a structured response (or the raw API response in case of an error, since tool responses always indicate success or include the raw API payload in error scenarios). The server requires a CoinGlass API key to access the v4 endpoints, passed via the COINGLASS_API_KEY environment variable.
To run the server via a MCP-enabled client, configure the client to start the server process using the provided command. For example, using pnpm dlx to launch the server, or using a globally installed package if you prefer. Once started, you can invoke tools by sending JSON payloads that specify the tool name and parameters. Example tool invocations include requesting open interest with a specific symbol and history window, or querying liquidations for a given exchange/symbol with a chosen interval. The tooling supports both real-time data and historical windows, and is designed to integrate into AI assistants, IDE extensions, or custom dashboards.
How to install
Prerequisites:
- Node.js v20+ (CI uses Node 22)
- pnpm package manager
Install and run:
- Using pnpm dlx (recommended for MCP client setups)
pnpm dlx mcp-coinglass
- Global installation from npm (via pnpm)
pnpm add -g mcp-coinglass
- Building from source (development)
pnpm install pnpm run build pnpm run start
- For testing and development purposes use mcp inspector
in the project root run,
pnpm run build npx @modelcontextprotocol/inspector node dist/index.js
Configuration (Environment Variables):
This server requires a CoinGlass API key. All CoinGlass v4 endpoints require the CG-API-KEY header. Generate your key from your account dashboard and supply it via environment variables. Create a .env file (or configure env in your MCP client) with:
COINGLASS_API_KEY=your_api_key_here
An .env.sample file is included for reference; copy it to .env and fill in your key.
Additional notes
Notes and tips:
- You must provide a valid CoinGlass API key by setting COINGLASS_API_KEY in the environment for the server to access v4 endpoints.
- Some tools require an upgraded CoinGlass API plan to function.
- Endpoints referenced include open-interest, liquidation history (pair and aggregated by coin), global long/short ratio history, and funding rate history. The server returns a standardized success payload; in case of API errors, the raw API response is included.
- If you run locally with pnpm, you can test using the MCP inspector tool to observe tool invocations and responses during development.
Related MCP Servers
obsidian -tools
Add Obsidian integrations like semantic search and custom Templater prompts to Claude or any MCP client.
mcp
Octopus Deploy Official MCP Server
furi
CLI & API for MCP management
capacities
Capacities×MCP
mcp-bundler
Is the MCP configuration too complicated? You can easily share your own simplified setup!
CodeRAG
Advanced graph-based code analysis for AI-assisted software development