← MCP servers

SDK

Polygate: choose research or account tools for your MCP client

Polygate exposes Polymarket research, prices and configured account operations as MCP tools. A wallet-free setup supports public reads; account inspection and order tools use the funding wallet and signer you configure.

Available on
CLI · MCP

Screenshots and interface

What is Polygate?

Research tools search events, read resolution rules and query books, midpoint, spread, last trade and supported history. When account access is configured, the toolset also reads positions, balances, activity and working orders and can expose order placement or cancellation.

Desktop clients can run the server locally through uvx. The web path runs a connect process, a temporary Cloudflare tunnel and an OAuth-protected MCP URL for a compatible client. The process must keep running; stopping it ends the tunnel. This uses your configured Polymarket account rather than creating a new one.

Who it is for

  • Users of MCP research assistants.
  • Developers wanting a compact Polymarket server.
  • Technical users connecting local account workflows.

Features and coverage

  • Market research

    Search events and inspect questions and resolution rules.

  • Live market reads

    Read books, midpoint, spread, last trade and supported history.

  • Account inspection

    Read configured positions, balance, activity and working orders.

  • Order tools

    Place and cancel orders through enabled execution.

  • Local MCP

    Run uvx in a desktop MCP configuration.

  • Temporary web connector

    Use connect, cloudflared and generated OAuth credentials.

  • Research and execution modes

    Start with research or explicitly enable trading on the web connector.

Workflows with Polygate

Add public research

Configure local MCP without a wallet and request market details and current books.

Connect a web client

The web connection lasts only while the local connect process runs. Start that process, take its printed MCP URL and OAuth credentials into a supported client, and leave it running for the session.

Add intended account tools

Set funding address and signer, inspect the account identity and expose the order methods needed.

Pricing and total cost

MIT-licensed code with no listed server subscription. Model-client charges, infrastructure and venue costs are separate.

Getting started

Before you start: The tunnel needs its connect process running.

  1. Install uv/uvx and choose local MCP or the web connector.
  2. Start research-only and inspect tools.
  3. For web, install cloudflared, configure generated credentials and keep connect running.
  4. Add wallet settings for account operations.

Stopping connect closes the temporary tunnel.

Useful links

What to check

  • The tunnel needs its connect process running.
  • Web clients must support remote MCP and the required OAuth flow.
  • Local wallet credentials reside in the host configuration environment.
  • Execution credentials enable account actions beyond public research.
  • The funding address can differ from the signer.

A closer look

Ratings & reviews

Editorial rating
3.5/ 5
0 user reviews

Our take on Polygate

Public and credentialed modes help define an assistant integration. Tunnel lifetime, client compatibility and host-stored credentials add setup responsibilities.

Based on documented features, setup and access terms. How we rate

User reviews 0

The main score switches to user ratings after 5 published reviews.

Be the first to share your experience

A specific example helps the next person choose the right tool.

Related tools

Browse category

Frequently asked questions about Polygate

Can I research without an account?

Public research and prices need no wallet credentials.

Do I need a public server?

Local MCP does not; web uses a temporary tunnel.

Why did the connector stop?

Its process and tunnel must remain running.

Does it create another trading account?

It uses the account identified by your configured funding wallet and signer.