Skip to main content
POST
LinqAlpha MCP

Overview

LinqAlpha MCP gives AI assistants direct access to institutional-grade financial data for fundamental research. Through the Model Context Protocol, your AI (Claude, Cursor, etc.) can query company fundamentals, earnings estimates, stock prices, economic indicators, SEC filings, and earnings transcripts — all from a single endpoint.

Quick Start

If you already have an existing API key, you must request a new key with MCP permissions enabled. Existing keys issued before the MCP endpoint release do not have MCP access. Contact support@linqalpha.com to request a new key.
Add the following to your MCP client configuration:

Use via Completion API

You can use LinqAlpha MCP tools directly from any LLM completion API (OpenAI, Anthropic, etc.) by making standard HTTP requests to our MCP endpoint. This lets you integrate LinqAlpha’s financial data tools into your own AI workflows and applications.

Step 1: List Available Tools

First, fetch the tool definitions to get their names and input schemas:
Python

Step 2: Convert to OpenAI Tool Format

Transform MCP tool definitions into the format expected by OpenAI’s API:
Python

Step 3: Chat with Tool Calling

Use the converted tools in your OpenAI completion request, then execute any tool calls against LinqAlpha MCP:
Python
This pattern works with any LLM that supports function/tool calling — including Anthropic Claude API, Google Gemini, and open-source models. Just adapt the tool format conversion for your provider.

Available Tools

LinqAlpha returns an organization-specific tool contract through tools/list. The base contract currently contains 22 tools; approved organization capabilities can add tools such as RMS search and citation. Treat the live tools/list response as authoritative. Before planning a multi-tool workflow, call read_guide with orchestration/current. This guide is rendered from the authenticated organization’s current tool entitlement and routing policy.

Fundamentals & Estimates

Economic Data

Market Data

Research & Citations

Organization-specific RMS

These tools appear only when RMS access is included in the authenticated organization’s effective contract.

Platform

Expanded data tools

The tables above are the core surface. An organization’s contract can also include further canonical tools — for example S&P Capital IQ (snp_query, snp_docs, snp_prices), LSEG (lseg_query), filings (filing_*, create_filing_reference), event transcripts (aiera_*), Korean market data (kr_*, kis_bond_*, koscom_etf_*, ecos_*, nice_*), prediction markets (kalshi_*, polymarket_*), and social or news sources (x_*, reddit_*, news_rss_search, search_naver_news). These tools keep their canonical names, and each tool’s description names the guide to read first; read that guide once before the first call. tools/list is the only authoritative inventory for your organization, and read_guide('orchestration/current') explains how the granted tools fit together. Tools that render inside the Linq web client or depend on customer-specific upstream credentials are never exposed here.

Protocol

This endpoint implements JSON-RPC 2.0 over HTTP, following the MCP specification.

Supported Methods

Example: List Tools

Request
Response

Example: Call a Tool

Request
Response

Rate Limits

  • 60 requests per minute per user
  • Exceeding the limit returns a JSON-RPC error with code -32000

Error Codes

Authorizations

X-API-KEY
string
header
required

Body

application/json
jsonrpc
enum<string>
required

JSON-RPC version

Available options:
2.0
method
enum<string>
required

MCP method to invoke

Available options:
initialize,
ping,
notifications/initialized,
tools/list,
tools/call
id
integer

Request identifier

params
object

Method-specific parameters. For tools/call: { name: string, arguments: object }

Response

JSON-RPC 2.0 response

jsonrpc
enum<string>
Available options:
2.0
id
integer | null

Request identifier (null for error responses)

result
object

Method result (present on success)

error
object

Error object (present on failure)