TradingView MCP
Official server
- Quotes and price history
- Screeners and company research
- Watchlists and alerts
The official TradingView MCP server brings TradingView market data, research, watchlists, and alerts into your AI client. Pineify MCP adds Pine Script checks and specialist datasets such as options flow, dark-pool prints, and Congress disclosures. Connect both and route each question to the source built for it.
TradingView MCP requires an eligible TradingView plan. Pineify MCP access is included with Pineify Expert.
One client, two servers
The agent selects a server for each part of the task.
Official server
Companion server
Claude, ChatGPT, Codex, or another MCP client
Keep source names in the prompt so results stay auditable.
What the official server does
TradingView hosts the remote MCP endpoint and handles account authorization with OAuth 2.1. The assistant can call the documented tools instead of relying on scraped pages or model memory.
Current beta boundary
TradingView says the tool list is limited, market data is delayed, and request limits may apply. Check the official docs before depending on a specific tool or entitlement.
Quotes, historical OHLCV, and economic series
TradingView screeners, fundamentals, forecasts, and news
Filings, earnings calls, earnings, dividends, and economic calendars
TradingView watchlists and alerts, including documented write actions
Why add Pineify MCP
Pineify MCP currently registers 30 read-only tools. It is most useful after TradingView has supplied native market or account context and the next task needs code validation, specialist activity data, or a bounded research workflow.
Pine Script v6 syntax checks with normalized diagnostics
MQL4, MQL5, cTrader C#, and NinjaScript code checks
Options flow, exact-contract prints, dark-pool prints, and Congress disclosures
Bounded portfolio risk, market regime, stock screening, and historical model workflows
Inspect all Pineify MCP tools and their exact boundaries
Each tool page documents accepted inputs, returned evidence, and what the tool does not do.
TradingView MCP vs Pineify MCP
The official server owns TradingView-native context. Pineify extends the workflow where its registered tools have a clearer data or validation contract.
| Question | Official TradingView MCP | Pineify MCP |
|---|---|---|
| Best starting point | TradingView-native market data, research documents, watchlists, and alerts. | Trading-code checks and specialist research workflows that are not listed in the official TradingView tool catalog. |
| Account actions | OAuth 2.1 access can create or update watchlists and create, pause, resume, update, or delete alerts. | All 30 registered tools are read-only. They do not place trades or modify a portfolio. |
| Code validation | No Pine Script syntax checker is listed in the official tool catalog verified on September 17, 2026. | Checks Pine Script v6 plus MQL4, MQL5, cTrader C#, and NinjaScript source. |
| Specialist data | Market prices, screeners, company research, documents, news, and calendars. | Options flow alerts, option-contract prints, dark-pool prints, Congress disclosures, and market-tide snapshots. |
| Access boundary | Public beta for Essential and higher plans. Trial plans do not include MCP access. | Pineify Expert includes the remote MCP endpoint and a private setup token. |
| Current limitation | TradingView says the beta has a limited tool list, delayed market data, and request limits. | Tools use bounded inputs and explicit coverage limits. Results are research data, not investment advice. |
Connect both servers
Both servers use remote MCP connections. TradingView handles its own OAuth approval. Pineify gives eligible users a setup prompt with the endpoint and private token.
Official commands
claude mcp add --transport http mcp-tradingview https://mcp.tradingview.com/mcpcodex mcp add tradingview --url https://mcp.tradingview.com/mcpComplete TradingView authorization in the browser. Other clients may use a connector form instead of a terminal command.
STEP 01
Add the official Streamable HTTP endpoint to your MCP client, sign in to TradingView, and approve the requested access.
https://mcp.tradingview.com/mcp
STEP 02
Open Pineify MCP setup, copy your private setup prompt, and let the same client register the Pineify endpoint.
Keep the Pineify token private and out of repositories.
STEP 03
Ask for TradingView when you need TradingView account data or actions. Ask for Pineify when you need code checks or Pineify specialist datasets.
Your agent can combine the returned evidence in one conversation.
Prompts for the paired workflow
Explicit source names reduce accidental tool mixing and make it easier to inspect timestamps, missing coverage, and account actions before you rely on the answer.
Use TradingView to summarize NVDA price action, recent news, analyst consensus, and the next earnings date. Then use Pineify to check recent options-flow and dark-pool evidence. Keep each source and timestamp separate.
Use TradingView Screener to find US technology stocks near a 52-week high with rising volume. Then use Pineify to syntax-check this Pine Script v6 alert and explain every diagnostic without changing the source.
Use TradingView to read my active watchlist and recent alert log. Use Pineify to build a bounded risk snapshot for the supported US positions. Do not create alerts, change the watchlist, or suggest trades.
Turn a researched setup into reviewable Pine Script, then check the source with Pineify MCP.
Open productInspect Pineify options flow, dark-pool, market-tide, and related activity data in the product UI.
Open productContinue company and market research with Pineify workflows outside the MCP client.
Open productTradingView MCP FAQ
Yes. TradingView launched its own MCP server as a public beta. The official endpoint is https://mcp.tradingview.com/mcp, and authentication uses your TradingView account through OAuth 2.1.
No free or trial access is documented for the beta. TradingView says MCP access is included with Essential and higher plans, while trial plans are excluded.
Yes. An MCP client that supports multiple servers can connect to both. Use TradingView for its native data and account tools, then call Pineify for code validation and specialist datasets.
Pineify adds 30 read-only tools. The current registry includes Pine Script and multi-platform syntax checkers, options-flow and dark-pool data, Congress disclosures, stock research, market workflows, and bounded portfolio analysis.
No. Pineify MCP tools are read-only and cannot place orders, modify positions, or change TradingView watchlists and alerts. The official TradingView server documents separate write tools for watchlists and alerts.
Do not assume every result is live. TradingView describes market data in the public beta as delayed and says the available tool list and request limits may change.
Keep TradingView as the source for TradingView-native data and account context. Add Pineify when your agent needs source-code diagnostics or one of Pineify's specialist research tools.