MCP
Connect your AI assistant to stock data and API documentation.
Connect to OHLC with MCP
Connect your AI assistant to OHLC with Model Context Protocol (MCP). Query stock data and get help with API endpoints, parameters, authentication, and errors in the same conversation.
Add OHLC to your assistant
In Claude, open Connectors (under Customize or Settings) and add a custom connector with this URL. Leave the OAuth Client ID and secret blank.
Server URLhttps://api.ohlc.io/mcpSign in and allow access
Click Connect, sign in to OHLC, and approve access to your workspace. You do not need to create or copy an API key. MCP is included on Developer, Pro, Commercial, and Scale. Manage your plan.
Verify the connection
Save the server and refresh your client’s tools. You should see tools such as
get_quotes,get_newsandget_api_documentation. Try: “Explain the OHLC quotes endpoint and its parameters.” Then ask: “Get the latest available quote for XNAS:AAPL.” Data access depends on your workspace’s plan and available coverage.
Connected applications
Disconnecting immediately removes this application’s access. You can connect again from your assistant.
Loading connections…
Connect with an API key instead
For clients that support custom bearer headers, create an API key and use this configuration. Replace the placeholder with your saved key in your client’s secure settings. Keep it out of shared files and source control.
{
"mcpServers": {
"ohlc": {
"type": "http",
"url": "https://api.ohlc.io/mcp",
"headers": {
"Authorization": "Bearer YOUR_OHLC_API_KEY"
}
}
}
}What your assistant can do
- One tool per data endpoint
- Quotes, prices and bars, fundamentals, filings, news, earnings, financial statements, estimates, ownership, options, economic data and more, each as its own tool such as
get_quotes,get_newsorget_earnings. Prices may be delayed; preserve the returned licensing notices. get_api_documentation- Discover REST endpoints, read parameter and response schemas, and explain authentication, pagination, errors, limits, and WebSocket behavior. Ask for a topic or an exact endpoint such as
/v1/quotes.
Troubleshooting
401: Reconnect your application, or check your API key. 403: Check your paid 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, including documentation calls.
Opening the URL in a browser is not a connection test. Use an MCP client to initialize the server and list its tools. This page provides configuration; connection status is shown in your client.