TradingView MCP
Official server
- Quotes and price history
- Screeners and company research
- Watchlists and alerts
Official public beta, verified October 16, 2026
Pine Script MCP: syntax checks, setup and permissions
Pineify MCP accepts Pine Script source and returns syntax diagnostics to your AI client. TradingView's separate official MCP server provides market data and account tools. A successful code check does not run your script, prove its trading logic, or authorize account changes.
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.
Pineify MCP
Companion server
- Pine Script diagnostics
- Options and dark-pool data
- Bounded research workflows
Claude, ChatGPT, Codex, or another MCP client
Keep source names in the prompt so results stay auditable.
Pine Script MCP tool inputs and outputs
After connecting Pineify, refresh the client's tool list and confirm the exact tool name. These are registered Pineify tools; their linked references describe the accepted inputs and output fields.
| Tool | Input | Output | Boundary |
|---|---|---|---|
| pine-script-syntax-checker | One complete, nonempty code string. | hasError, errors with row/column/message, isTimeout, and isSystemError. | Returns diagnostics without modifying source. Does not run a chart, backtest, or broker order. |
| find-options-flow-alerts | Up to 10 ticker symbols, optionType, premium/DTE filters, and limit from 1 to 50. | Filtered activity records with observation times, contract IDs, premiums, and coverage metadata. | Financial evidence for research. It neither validates Pine code nor grants TradingView account access. |
| get-option-contract-flow | A non-null contractId returned by options-flow discovery; use the linked schema for filters. | Observed prints for that contract, with timestamps and available trade fields. | Copy the returned ID. Do not construct an identifier from a ticker or infer missing trades. |
Submit a complete Pine Script
Ask the agent to call pine-script-syntax-checker with this source as the code string, then report the returned diagnostics. This indicator plots a moving average; it contains no orders.
//@version=6
indicator("MCP syntax check example", overlay=true)
length = input.int(20, "SMA length", minval=1)
plot(ta.sma(close, length), title="SMA")
Read every status field
The example returned this result in a Pineify MCP check on October 16, 2026. This is a syntax result, not a TradingView chart or backtest result.
{
"hasError": false,
"errors": [],
"isTimeout": false,
"isSystemError": false
}A timeout or system error means the check is incomplete even when hasError is false. For reported errors, inspect the row, column, and message, edit the source, and check the full script again. Then review chart behavior in TradingView.
Connection and permission checks
- If authentication fails, verify the endpoint, plan entitlement, and the configured Bearer header. Keep tokens out of screenshots, shared chats, and repositories.
- If a tool is missing, reconnect or refresh discovery and check which server owns it. Client configuration formats differ; use Pineify's setup prompt and your client's remote MCP settings.
- Connecting a server grants only its documented tools. Browser control, publishing a script, and broker execution require separate capabilities and authorization. Review any account-changing call before allowing it.
- TradingView's get_active_watchlist can activate a watchlist or create a default one despite its read-only label. Use list_watchlists and get_watchlist when you only need an existing list.
Continue with the Pine Script coding guides or full syntax-checker contract. TradingView account-tool behavior is documented in the official MCP catalog.
What the official server does
TradingView MCP connects your account to an AI assistant
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
Add the data and diagnostics that the official catalog does not list
Pineify MCP currently registers 40 tools, including nine Journal 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
Choose by task, not by brand
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. | 35 tools are read-only; five write to your own Journal. They do not send broker orders or transfer money. |
| Code validation | No Pine Script syntax checker is listed in the official tool catalog verified on October 16, 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. |
Official TradingView capabilities and beta limits were verified against TradingView's public beta announcement and MCP documentation on October 16, 2026. Pineify capabilities were verified against the current MCP tool registry in this repository.
Connect both servers
Keep one AI conversation and two clear sources
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
Connect the official TradingView server
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
Connect Pineify MCP beside it
Open Pineify MCP setup with an Expert account. Add the endpoint to a client that supports Streamable HTTP and an Authorization Bearer header, using your private token.
https://agents.pineify.app/mcp | Authorization: Bearer <YOUR_PRIVATE_TOKEN>
STEP 03
Name the source in your prompt
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
Tell the agent which server owns each fact
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.
Research, then inspect specialist activity
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.
Screen, then validate the implementation
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 account context without mixing permissions
Use TradingView list_watchlists, then get_watchlist for the ID I select, and read my 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.
Market and model outputs are informational. Check source times, coverage gaps, and calculation boundaries before making a trading or investment decision.
Pine Script AI coding agent
Turn a researched setup into reviewable Pine Script, then check the source with Pineify MCP.
Open productMarket Insights
Inspect Pineify options flow, dark-pool, market-tide, and related activity data in the product UI.
Open productFinance Agent
Continue company and market research with Pineify workflows outside the MCP client.
Open productTradingView MCP FAQ
Setup and capability questions
What does a Pine Script MCP syntax check prove?
It reports syntax diagnostics for the supplied source. It does not prove that signals avoid repainting, that alerts match your rules, or that a strategy is profitable. Review the code and run it on the intended TradingView chart after the syntax check completes.
Do I need both MCP servers to check Pine Script?
No. Pineify can check the source you provide without a TradingView MCP connection. Add TradingView MCP when the task needs its market data or documented account tools. Each connection has separate authentication and permissions.
Is the TradingView MCP server official?
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.
Is TradingView MCP free?
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.
Can I use TradingView MCP and Pineify MCP together?
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.
What does Pineify MCP add to the workflow?
Pineify adds 40 tools, including nine Journal tools. The current registry includes Pine Script and multi-platform syntax checkers, options-flow and dark-pool data, option-candidate screening, Congress disclosures, stock research, market workflows, and bounded portfolio analysis.
Can Pineify MCP place trades or change my TradingView account?
Pineify can record and edit Journal data. It cannot send broker orders, transfer money, or change TradingView watchlists and alerts. The official TradingView server documents separate write tools for watchlists and alerts.
Does TradingView MCP provide live market data?
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.
Add Pineify to your TradingView MCP workflow
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.