One click
Cursor
Opens Cursor and adds the hosted server. Sign in with Console when prompted.
Add to CursorConnect the TradingView MCP server to Cursor, VS Code, Claude, Codex, and Gemini so AI assistants can query market search, quotes, candles, technical analysis, news, and screeners across stocks, crypto, and forex — without building a custom tool layer.
Install with one click or one command, then sign in with Console. Keep a JWT, or a local RapidAPI OpenAPI MCP, only when the client cannot complete OAuth.
Let Claude and Cursor call stock, crypto, and forex tools over MCP
Real-time streaming with Server-Sent Events (SSE) for efficient data delivery
Access 27 tools for market data, analysis, screeners, ideas, and research
One-click for Cursor and VS Code, one command for Claude Code / Codex / Gemini, then sign in with Console. No token in your config file.
Works seamlessly with popular AI assistants and MCP clients
Access data from 353+ exchanges across all major asset classes
Optimized for speed and reliability with enterprise-grade infrastructure
27 tools covering quotes, candles, options, ETFs, screeners, fundamentals, ideas, and world economy
Search for symbols across 353+ exchanges
Get markets, tabs, columnsets, languages, and exchanges
Get a real-time quote for a single symbol
Get real-time quotes for up to 10 symbols
Get the option chain for an underlying symbol
Get ETF AUM, NAV, expense ratio, and top holdings
Get OHLCV candles (Japanese, Heikin-Ashi, or Range)
Get OHLCV candles for up to 10 symbols
Get standard Japanese OHLCV for backtests and indicators
Get standard Japanese OHLCV for up to 10 symbols
Get chart event markers such as earnings, dividends, and splits
Get technical analysis signals and optional indicator detail
Get financial news filtered by symbol, market, language, or region
Get full article content by news ID
Get economic, earnings, dividend, and IPO calendars
Get gainers, losers, and other ranked lists by asset type
Get company, financials, forecasts, dividends, and analyst data
Run a configurable screener for stocks, crypto, ETFs, bonds, CEX, or DEX
List screener preset field groups for an asset type
List valid screener filter IDs, operations, and enum values
Get trending TradingView community ideas
Get editor-picked trading ideas
Get community ideas for a specific symbol
Get the full write-up for a community idea
Get short community opinions (minds) for a symbol
List world-economy indicator slugs and categories
Get GDP, unemployment, and other country indicator rankings
Use a Console account on a plan that includes MCP (Basic for testing, Ultra or Mega for production). Pro does not include MCP.
Skip the config file unless your client is listed under Other clients. After install, the first connection opens Console in the browser.
One click
Opens Cursor and adds the hosted server. Sign in with Console when prompted.
Add to CursorOne click
Opens VS Code and adds the server. Use Copilot Agent mode after sign-in.
Paste URL
Customize → Connectors → Add custom connector. Paste the hosted URL, then sign in.
Open Claude Connectors →https://mcp.tradingviewapi.com/mcp Copy the command, then complete Console sign-in in the client.
claude mcp add --transport http tradingview https://mcp.tradingviewapi.com/mcp Then run /mcp in the session and finish the browser login.
codex mcp add tradingview --url https://mcp.tradingviewapi.com/mcp
codex mcp login tradingview The second line opens Console in the browser.
gemini mcp add --transport http tradingview https://mcp.tradingviewapi.com/mcp If Gemini asks to authenticate, run /mcp auth tradingview.
Use these when the client has no install link or CLI. Older clients may use streamable-http instead of http. The URL is the same.
{
"mcpServers": {
"tradingview": {
"type": "http",
"url": "https://mcp.tradingviewapi.com/mcp"
}
}
} Cursor: ~/.cursor/mcp.json. Claude Desktop: ~/Library/Application Support/Claude/claude_desktop_config.json.
{
"servers": {
"tradingview": {
"type": "http",
"url": "https://mcp.tradingviewapi.com/mcp"
}
}
} Workspace: .vscode/mcp.json. VS Code uses servers, not mcpServers.
code --add-mcp '{"name":"tradingview","type":"http","url":"https://mcp.tradingviewapi.com/mcp"}' {
"mcpServers": {
"tradingview": {
"serverUrl": "https://mcp.tradingviewapi.com/mcp"
}
}
} Windsurf: ~/.codeium/windsurf/mcp_config.json. The remote field is serverUrl, not url.
The first connection opens Console in the browser. Sign in and allow access. The client stores refresh credentials, so you do not paste a JWT into a config file.
POST /api/mcp/generate — see JWT token setup.After sign-in, restart is usually unnecessary. Ask the assistant to use TradingView tools:
"Search for Apple stock symbol"
"Get real-time quote for AAPL"
"Show me technical analysis for BTC/USDT"
"Get latest news for Tesla"
"Show upcoming earnings calendar"
"Get market leaderboards and top gainers"
"Use the TradingView MCP server to compare BTCUSDT and ETHUSDT trend signals"
Use this when the client cannot complete OAuth, when you are testing in the browser MCP tester, or when you subscribe on RapidAPI and want the official hosted tools. Generate a token, then put it in the client headers.
curl -X POST https://tradingview-data1.p.rapidapi.com/api/mcp/generate \
-H "x-rapidapi-host: tradingview-data1.p.rapidapi.com" \
-H "x-rapidapi-key: YOUR_RAPIDAPI_KEY" token — JWT for Authorization: BearermcpUrl — hosted MCP endpointexpiresIn — Basic 30 minutes, Ultra 15 days, Mega 30 daysAdd the token to the same hosted URL. Console API keys can call POST https://api.tradingviewapi.com/api/mcp/generate with Authorization: Bearer YOUR_API_KEY instead of RapidAPI headers.
{
"mcpServers": {
"tradingview": {
"type": "http",
"url": "https://mcp.tradingviewapi.com/mcp",
"headers": {
"Authorization": "Bearer YOUR_TOKEN_HERE",
"Accept": "application/json, text/event-stream"
}
}
}
} This local npx server is for RapidAPI subscribers. It runs on your machine, uses your RapidAPI quota directly, and exposes the OpenAPI spec as tools. It is not the hosted TradingView MCP and does not use Console OAuth.
Add under mcpServers in a command-based MCP client, then replace YOUR_RAPIDAPI_KEY
{
"mcpServers": {
"tradingview-data": {
"command": "npx",
"args": ["-y", "@ivotoby/openapi-mcp-server"],
"env": {
"API_BASE_URL": "https://tradingview-data1.p.rapidapi.com",
"OPENAPI_SPEC_PATH": "https://www.tradingviewapi.com/openapi.json",
"API_HEADERS": "x-rapidapi-host:tradingview-data1.p.rapidapi.com,x-rapidapi-key: YOUR_RAPIDAPI_KEY"
}
}
}
} tradingview_* listhttps://mcp.tradingviewapi.com/mcp The hosted MCP URL accepts:
Authorization: Bearer MCP JWT from POST /api/mcp/generateRapidAPI keys mint a JWT, or run the local OpenAPI MCP. They are not headers on the hosted URL.
OAuth clients set these for you. Use them only with a manual MCP JWT:
Content-Type: application/json
Accept: application/json, text/event-stream
mcp-protocol-version: 2025-03-26
Authorization: Bearer YOUR_TOKEN JWT lifetime follows your Console plan. OpenAPI: token lifetime follows your plan.
OAuth refresh renews the JWT. Manual JWTs must be regenerated before expiresAt.
MCP messages are JSON-RPC 2.0 over Streamable HTTP:
result with tool outputerror with code and messageid matches the client requestPOST /api/mcp/generate is capped (OAuth mint uses the same endpoint). Tool calls are not billed as REST quota.
REST monthly quotas apply to HTTP API calls, not hosted MCP tools.
Start accessing professional market data through your AI assistant today.