Skip to main content
The Parallax MCP server exposes Chicago Global’s investment research as a set of tools any Model Context Protocol client can call — Claude, Cursor, VS Code, ChatGPT, and more. Instead of wiring up the REST API yourself, you connect once and your AI assistant can score stocks, analyze portfolios, pull financials, read macro and market telemetry, synthesize news, and generate research reports on your behalf.

Connect a client

Add Parallax to Claude, Cursor, VS Code, or ChatGPT in a couple of minutes.

Authentication

How OAuth sign-in and programmatic bearer tokens work.

Tool reference

Every tool the server exposes, grouped by what it does.

REST API

Prefer raw HTTP? The same intelligence is available over the REST API.

​
Endpoint

The server speaks Streamable HTTP (the current MCP transport). Point your client at:
A legacy SSE endpoint is also available for older clients:
When connecting with an OAuth-capable client, sign in through your browser to link your Parallax account. The client then manages the access token — see Authentication.

​
What you can do

See the full tool reference for the complete list, including which tools are free vs. paid and which run asynchronously.

​
Symbol format

Tools accept symbols in RIC format (ticker + exchange suffix, e.g. AAPL.O, JPM.N, 2330.TW). Many tools also accept a plain ticker (AAPL) and resolve it for you; when in doubt, use the search_stocks tool to find the exact symbol first.

​
Relationship to the REST API

The MCP server is a thin, auth-aware layer over the same api.chicago.global backend. Tool outputs mirror the REST responses. Long-running tools normally poll their background jobs internally and return the completed result. Use check_job_status only if a tool returns a job ID without a completed result. If you’re building an application, use the REST API directly; if you’re working inside an AI client, use MCP.
Last modified on September 21, 2026