Uniswap Pools MCP Server

Uniswap Pools MCP MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. An MCP server for querying Uniswap pools/pairs by token address, delivering clean, structured results for easy integration and analysis.

What you get

• Query Uniswap Pools/Pairs —
• Fetch V2, V3, and V4 pools/pairs for a given token address
• Retrieve specific pool/pair details by version (v2, v3, v4) and ID
• Formatted Output —
• Returns data in markdown tables for combined pool queries
• Provides markdown text summaries for specific pool/pair queries, including token addresses

Setting it up

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

What the assistant can call

Once Uniswap Pools MCP is connected, these are the calls the assistant has available:

• Description — Queries all Uniswap V2, V3, and V4 pools/pairs for a given token address
• Parameters — - token_address (str): Ethereum address of the token (e.g., 0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48 for USDC)
• Output — Markdown table with columns: Version, ID, Pair, Fee Tier, Volume USD, Liquidity/ReserveUSD, Fees USD
• Example — Prompt:
• Version — v2
• Pair — USDC/WETH
• Prerequisites — The Prerequisites tool exposed by this server
• Setup — 1. Clone the Repository: bash git clone https://github.com/kukapay/uniswap-pools-mcp.git cd uniswap-pools-mcp
• Tools — 1. Get All Pools/Pairs for a Token: python def get_token_pools(token_address: str) -> str: - Description: Queries all Uniswap V2, V3, and V4

Configuration and credentials

You will need one environment variable: THEGRAPH_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• Python: Version 3.10 or higher. - uv: A Python package manager (recommended for dependency management). - The Graph API Key: Required for querying Subgraphs. Obtain one from The Graph.

Before you rely on it

• 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.
• With 9 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Uniswap Pools MCP.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the uniswap pools mcp mcp server does with a few real requests.

Choosing this one

Plenty of developer tooling 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. Uniswap Pools MCP's toolset — Description, Parameters, Output and 6 more — is a fair guide to whether it matches your workflow. It is maintained by kukapay; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.