Market data tools for
any MCP client.
TickerAPI exposes pre-computed financial data as MCP tools. Connect to Claude Desktop, Cursor, Windsurf, or any MCP-compatible client — your AI assistant pulls live market context directly from the chat.
Connect in two minutes.
Three ways to connect. Pick whichever fits your setup.
Connect directly from Claude.ai with one click. No API key management — sign in with your TickerAPI account and Claude handles the rest via OAuth 2.1.
// Add as a Connector in Claude.ai MCP server URL: https://mcp.tickerapi.ai // Authentication is handled automatically via OAuth // No API key needed — sign in when prompted
Uses OAuth 2.1 with PKCE. Your TickerAPI session handles auth automatically.
Point any MCP client at the remote endpoint. No install needed. Pass your API key as a Bearer token in the authorization header.
// MCP server URL https://mcp.tickerapi.ai/mcp // Authorization header Authorization: Bearer tapi_your_api_key
Works with any client that supports remote MCP servers over HTTP.
Run the MCP server locally via npx. Add this to your Claude Desktop config (or equivalent for your client):
{ "mcpServers": { "tickerapi": { "command": "npx", "args": ["tickerapi-mcp-server"], "env": { "TICKERAPI_KEY": "tapi_your_api_key" } } } }
Runs locally over stdio. No network dependency beyond the TickerAPI HTTP calls.
Chain tools in one conversation.
Your MCP client can chain multiple tool calls in a single conversation. Scan for opportunities, drill into details, then compare — each call returns categorical data the model understands without extra prompting.
The MCP client discovers all available tools at connection time. It picks the right tool for each step automatically.
Track state changes effortlessly.
Most market data APIs return point-in-time snapshots. TickerAPI tracks state transitions — your AI assistant sees what changed, not just what is.
{ "ticker": "AAPL", "changes": [ { "field": "rsi_zone", "from": "neutral", "to": "oversold" }, { "field": "trend", "from": "uptrend", "to": "downtrend" } ] }
What your assistant sees.
Every tool returns categorical facts — not raw OHLCV data. Your assistant can branch on "oversold" without needing to know what RSI > 70 means.
{ "ticker": "NVDA", "trend": "strong_uptrend", "momentum": { "rsi_zone": "overbought", "macd_signal": "bullish" }, "volatility": "high", "fundamentals": { "pe_zone": "above_historical_avg", "earnings_surprise": "positive" } }
What your assistant can call.
Every tool returns categorical, pre-computed data. Your assistant gets facts it can reason about immediately.
Full factual snapshot for a single asset — trend, momentum, fundamentals, support/resistance.
Side-by-side technical and fundamental comparison of two or more tickers.
Browse all supported tickers with filtering and search.
List all valid sector values with asset counts for scan filtering.
Live summary data for all tickers in your saved watchlist.
Field-level diffs for your watchlist since the last pipeline run.
Add tickers to your persistent watchlist.
Remove tickers from your watchlist.
Assets in confirmed oversold conditions across multiple indicators.
Assets in overbought RSI conditions with severity rankings.
Momentum breakouts with volume confirmation.
Volume anomalies and accumulation patterns.
Historically undervalued or overvalued assets based on fundamental metrics.
Notable insider buying and selling activity.
Your plan tier, rate limits, and current API usage.
Register a webhook URL for watchlist change notifications.
List your registered webhook URLs.
Remove a registered webhook.
Built for how assistants consume data.
Works with any MCP client
Claude Desktop, Cursor, Windsurf, VS Code, custom agents — any client that speaks MCP gets the full tool set automatically.
Compact responses
Tool-call context windows are limited. TickerAPI responses are a fraction of the tokens you'd need to pass raw OHLCV data.
Pre-computed daily
No infrastructure to maintain. No cron jobs, no indicator math, no data pipelines. TickerAPI handles computation and syncing.