Skip to main content
Connect an MCP-compatible AI client to Polaris at:
The hosted server requires no local installation or API key. It provides anonymous access to public catalog metadata, standardized snapshot listings, and expiring download URLs.
The hosted MCP server does not provide authenticated datasets, raw venue files, or local file management. Use the Polaris CLI or an SDK when you need those workflows.

​
Connect your client

1

Add the server URL

Open your AI client’s MCP or connector settings and add https://mcp.polaris.supply as a remote HTTP server.Clients that use JSON configuration commonly accept an entry like this:
2

Confirm the tools

Reconnect the client and confirm that it lists get_catalog, list_snapshots, and get_public_download_urls.
3

Ask for public data

Start with a request such as: Find the exact Polaris market ID for Hyperliquid BTC, list its latest public snapshots, and return the public download URLs.
You can also connect directly to https://polaris.supply/mcp. Both URLs serve the same stateless MCP endpoint.

​
Discover the server

Clients can discover the hosted MCP server from the Polaris AI Catalog:
The catalog points to the MCP Server Card at https://mcp.polaris.supply/server-card. The Server Card describes the server identity, supported protocol versions, and canonical Streamable HTTP endpoint before a client connects. For compatibility with clients and automated discovery tools that probe /.well-known/mcp.json, Polaris serves the same Server Card at https://polaris.supply/.well-known/mcp.json. The AI Catalog and transport-relative Server Card remain the canonical discovery flow.

​
Hosted MCP and WebMCP

Hosted MCP works from any compatible client after you add the server URL. It does not require an open Polaris browser tab. The Polaris homepage also exposes the same three public, read-only tools to browser-resident agents through WebMCP when the browser supports the current draft API. WebMCP requires the homepage to remain open and is treated as a progressive enhancement, so the site continues to work normally in browsers without it. WebMCP does not expose sign-in, verification codes, API-key management, logout, clipboard access, authenticated datasets, or raw files.

​
Available tools

get_catalog returns the complete matching API response. Add source, market, or q when possible because the unfiltered catalog is large. list_snapshots supports from, to, limit, and cursor. When has_more is true, call the tool again with next_cursor. get_public_download_urls returns URLs and metadata. Download the .jsonl.zst files outside the MCP conversation so compressed data does not enter model context. URLs expire after the interval reported by expires_in_seconds.

​
Public access boundaries

The hosted server never reads or forwards an API key. The Polaris API evaluates every catalog, snapshot, and download request as an anonymous caller.
  • open datasets are publicly accessible.
  • preview datasets may expose only dates allowed by public_cutoff_date.
  • restricted datasets require authenticated tooling.
  • Venue-native raw snapshots are not available through hosted MCP.
If a requested date is gated, choose a public date or continue with the authentication quickstart and an SDK or CLI.

​
Next steps

  • Read Catalog for market discovery fields.
  • Read Snapshots for pagination and snapshot metadata.
  • Read Download for manifest and file behavior.