Get started
Integrations

Connect Claude
to stock market data.

The OHLC MCP server gives Claude one read-only tool per data endpoint plus a documentation tool. Add it as a custom connector, sign in to OHLC, and ask questions about stocks, ETFs and crypto in plain language.

Sign in, no key to copy

Claude connects with OAuth. You sign in to OHLC and approve access; there is no API key to paste.

One tool per endpoint

Prices, fundamentals, dividends, filings, news and more, each as its own tool such as get_eod_prices or get_dividends.

Docs in the same chat

get_api_documentation explains endpoints, parameters, errors and limits from the live OpenAPI contract, free of credits.

Same limits as REST

Tool calls cost what their REST endpoint costs and draw on the same daily credits and rate limits.

Add OHLC as a custom connector in Claude

  1. In Claude, open Customize → Connectors, choose + Add, then Add custom connector.
  2. Name it OHLC and enter the server URL https://api.ohlc.io/mcp. You do not need an OAuth client ID or secret; if Claude asks how to register the client, choose Register automatically, since OHLC supports dynamic client registration.
  3. Click Add, then Connect. Sign in to OHLC and approve access to your workspace.
  4. In a conversation, open the + menu, choose Connectors and make sure OHLC is enabled.
  5. Try: “Explain the OHLC quotes endpoint and its parameters.” Then: “Get the latest available quote for XNAS:AAPL.”

On Team and Enterprise plans an owner adds the connector under Organization settings → Connectors; members then find it under Customize → Connectors and click Connect. Claude Desktop uses the same connectors. You can review and disconnect connected applications on the MCP page of your OHLC account.

Claude Code and API-key connections

Claude Code connects over HTTP. Add the server, then run /mcp inside Claude Code to sign in with OAuth.

Claude Code with OAuth sign-incURL
claude mcp add --transport http ohlc https://api.ohlc.io/mcp

For a headless setup, create an API key and send it as a bearer header instead. In a shared .mcp.json, reference an environment variable so the key never lands in source control.

.mcp.json with a bearer headerJSON
{
  "mcpServers": {
    "ohlc": {
      "type": "http",
      "url": "https://api.ohlc.io/mcp",
      "headers": {
        "Authorization": "Bearer ${OHLC_API_KEY}"
      }
    }
  }
}

Prices delayed 15 minutes · Illustrative sample data

Tools Claude can call

A selection. Tools whose description starts with “Not yet available” have no connected source and return 501.
ToolAnswers
get_eod_pricesDaily OHLCV history and how a stock has traded
get_intraday_bars5-minute and hourly bars for the last 30 days or so (Pro and above)
get_quotes, get_snapshotLatest delayed price, and the change from the previous close
get_movers, screen_instrumentsBiggest gainers and losers; screens by valuation, price, sector or exchange
get_companies, search_symbolsCompany name or ticker prefix to an exchange-qualified symbol
get_financials_statements, get_financials_metricsStatements, ratios, market capitalization and dividend metrics
get_dividends, get_splits, get_earningsCorporate actions and earnings history
get_datasets_coverageHow far back a dataset goes for a symbol
get_api_documentationEndpoints, parameters, errors, limits and streaming, without spending credits

Example prompts

  • “Chart NVDA's split-adjusted daily closes for 2024 and mark the split.”
  • “Compare the dividend history of JNJ and PEP over the last five years.”
  • “Which large-cap stocks were the biggest decliners in the last session?”
  • “How far back do daily prices for XNYS:KO go?”
  • “Write a Python script that pages through /v1/eod for ten symbols and handles 429 errors.”

Plans, credits and troubleshooting

MCP is included on Developer, Pro, Commercial and Scale; a Free account receives 403 mcp-not-entitled. Your plan still decides which datasets and how much history Claude can read, so intraday bars need Pro. Each tool call costs what its REST endpoint costs, while setup, tool discovery and get_api_documentation are free. Prices are delayed at least 15 minutes, and Claude is told never to present them as live.

  • 401: reconnect the application, or check the API key in your header.
  • 403: check your plan and workspace access; API-key connections also enforce key scopes and IP allowlists.
  • 429: wait for the Retry-After interval. REST and MCP share account limits.
  • Opening https://api.ohlc.io/mcp in a browser is not a connection test. Use an MCP client to initialize the server and list its tools.

Questions, answered.

Can Claude access live stock prices?

Claude can read OHLC's delayed quotes, at least 15 minutes behind the market, and end-of-day bars. OHLC does not provide real-time data to Claude or any other client.

Do I need an API key to connect Claude?

No. The custom connector signs in with OAuth. An API key is only needed for clients that send a bearer header, such as a headless Claude Code setup.

Which OHLC plan do I need for the MCP server?

Developer or above. The Free plan can call the REST API but not the MCP server.

Does using OHLC in Claude cost extra?

No separate fee. Tool calls spend the same daily credits as REST requests, and documentation lookups are free.

Does the connector work with Claude's free plan?

Claude allows custom connectors on its Free, Pro, Max, Team and Enterprise plans; Claude's Free plan is limited to one custom connector. You still need an OHLC Developer plan or above.

A little JSON.
A lot of possibility.

Explore the API