MCP Server - LLMQuant Data

@llmquant/data-mcp — one config gives every MCP-compatible agent access to 17+ financial data tools (wiki, papers, prices, ETFs, filings, macro). Source on LLMQuant/data-mcp.

Live npm · @llmquant/data-mcp

Why MCP

LLMQuant Data is built agent-first. The REST API exists as a fallback; the canonical interface is the Model Context Protocol — a standard that lets any agent runtime (Claude, Cursor, Codex, Gemini CLI, OpenClaw, ChatGPT custom GPTs…) call our data tools natively, with structured arguments and typed results, no glue code.

Configure once — every environment below picks it up.

Where it runs

Chatbots

ChatGPT · Claude · Cursor

Agent CLIs

Claude Code · Codex · Gemini CLI · OpenClaw

SDKs

LangGraph · Google ADK · Vercel AI SDK

If your runtime speaks MCP, LLMQuant Data is one config away.

Remote connectors

Claude web, Claude iOS, and other cloud-hosted agents cannot run a local npx stdio server. Use the hosted Streamable HTTP endpoint instead:

Generate a Remote MCP URL

https://mcp.llmquantdata.com/u/lqd_mcp_.../mcp

Paste it into Claude custom connectors

Choose Claude’s No Authentication connector mode and paste the full URL. The token lives in the URL path, is stored hashed by LLMQuant Data, and can be revoked from the Dashboard without rotating your API key.

Verify credit and revoke behavior

Run a paid search or read tool, confirm the Dashboard balance changes, then revoke a test URL and confirm it fails immediately.

Local desktop and CLI clients can keep using the stdio setup below. Remote URLs are for cloud clients and synced Claude connectors that need a public HTTPS MCP endpoint.

Quick setup

Get an API key

Add data-mcp to your client

Drop this prompt into your agent — it will read the canonical setup from GitHub:

Install the LLMQuant data-mcp server in this environment by following https://github.com/LLMQuant/data-mcp

Or install manually

Pick your runtime below. Each block is the canonical config — drop it in, save, restart the client.

claude mcp add llmquant-data \
  -e LLMQUANT_API_KEY=$LLMQUANT_API_KEY \
  -- npx -y @llmquant/data-mcp

Add to .cursor/mcp.json (project) or ~/.cursor/mcp.json (global): JSON config files usually do not expand shell variables, so paste your actual API key value.

.cursor/mcp.json

{
  "mcpServers": {
    "llmquant-data": {
      "command": "npx",
      "args": ["-y", "@llmquant/data-mcp"],
      "env": {
        "LLMQUANT_API_KEY": "your_api_key_here"
      }
    }
  }
}

codex mcp add llmquant-data \
  --env LLMQUANT_API_KEY=$LLMQUANT_API_KEY \
  -- npx -y @llmquant/data-mcp

gemini mcp add -s user \
  -e LLMQUANT_API_KEY=$LLMQUANT_API_KEY \
  llmquant-data \
  npx -y @llmquant/data-mcp

Edit claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/): JSON config files usually do not expand shell variables, so paste your actual API key value.

claude_desktop_config.json

{
  "mcpServers": {
    "llmquant-data": {
      "command": "npx",
      "args": ["-y", "@llmquant/data-mcp"],
      "env": {
        "LLMQUANT_API_KEY": "your_api_key_here"
      }
    }
  }
}

Any MCP client supporting stdio transport accepts this generic config: JSON config files usually do not expand shell variables, so paste your actual API key value.

{
  "mcpServers": {
    "llmquant-data": {
      "command": "npx",
      "args": ["-y", "@llmquant/data-mcp"],
      "env": {
        "LLMQUANT_API_KEY": "your_api_key_here"
      }
    }
  }
}

Don’t see your client? Open an issue and we’ll add it.

Ask the agent something it should now know

Restart the client. Then drop one of these into any chat / agent session — the agent will discover the new tools, pick the right one, and return structured results.

Wiki two-step lookup

Live crypto check

Research discovery

Available tools

Each tool is one MCP capability the agent can invoke. Pricing is per-call, billed in credits.

Tool	What it does	Credits
`wiki_search`	Semantic search over 50,000+ Quant Wiki entries	1
`wiki_read`	Load the full markdown body of a wiki item by ID	0
`paper_search`	Semantic search over 1,200+ research paper summaries	1
`paper_read`	Read specific sections of a paper (intro, methods, conclusion…)	0
`crypto_historical_klines`	Crypto OHLCV candles with configurable interval	1
`crypto_snapshot`	Latest spot price + 24h stats for a crypto pair	1
`equity_historical_prices`	US equity daily OHLCV + dividend / split adjustments. Also serves ETF price history.	1
`etf_lookup`	ETF basic info + top holdings summary + sector / country / asset-type exposure	0
`etf_holdings`	Full ETF holdings (latest available SEC regulatory disclosure snapshot, sorted by weight). Tickers outside coverage still return `200`, no credit charge.	1
`macro_indicator_search`	Browse 50+ curated macro indicators	0
`macro_indicator_history`	Historical observations for a macro series	1
`macro_indicator_snapshot`	Latest value for a macro indicator	1
`sec_filing_browse`	Browse SEC 10-K / 10-Q / 8-K filing metadata	0
`sec_filing_read`	Read specific sections of a SEC filing	1
`sec_13f_list_manager_holdings`	A manager’s 13F holdings (Top 1,000 × at least the last 4 quarters)	1
`sec_13f_list_ticker_holders`	Institutional holders of a ticker (Top 1,000 × at least the last 4 quarters)	1
`sec_13f_list_top_managers`	Top N smart-money managers ranked by 13F reportable value	1

More data products (news, fundamentals, earnings transcripts) are on the roadmap.

Environment variables

LLMQUANT_API_KEY

string

required

Your LLMQuant Data API key. Generate at Dashboard → API Keys.

LLMQUANT_BASE_URL

string

default:"https://api.llmquantdata.com"

Override the API base URL. Useful for self-hosted proxies or testing against staging.

LLMQUANT_API_TIMEOUT_MS

number

default:15000

Request timeout in milliseconds. Max 120000.

What’s next

Browse the data tools

Each tool maps 1:1 to an endpoint page with Agent flow diagram + response schema.

Source on GitHub

Read the source, file an issue, and follow the roadmap.

​Why MCP

​Where it runs

Chatbots

Agent CLIs

SDKs

​Remote connectors

​Quick setup

​Available tools

​Environment variables

​What’s next

Browse the data tools

Source on GitHub

Why MCP

Where it runs

Remote connectors

Quick setup

Available tools

Environment variables

What’s next