ETF Flow MCP MCP Server

An MCP server that delivers crypto ETF flow data to power AI agents' decision-making. That is what the etf flow mcp mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

• Unified Tool — The get_etf_flow tool dynamically fetches historical ETF flow data for BTC or ETH
• Markdown Table Output — Leverages pivot tables to present data with ETF tickers as columns, dates as rows, and a total column for summed flows
• Prompt Guidance — Includes a prompt (etf_flow_prompt) to streamline LLM interactions for user-friendly queries

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

What it needs from you

Configuration is passed through the environment: COINGLASS_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

• Python: Version 3.10 or higher. - uv: A fast Python package and project manager (install instructions). - CoinGlass API Key: Obtain a key from CoinGlass. - Claude Desktop: Optional, for interactive querying. - Git: For cloning the repository.

Things to watch

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How it compares

Plenty of AI and media services servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. It is maintained by kukapay; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.