tradingview-chip
Enables interaction with TradingView charts through a local browser session, including chart state and symbol/timeframe controls, indicators, saved layouts, alerts, Pine scripts, strategy reports, market data, watchlists, drawings, replay, screenshots, and research/simulation tools.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
tradingview-chip
An agent skill plus a local Model Context Protocol server that lets an MCP client work with TradingView charts in Chrome, Chromium, Microsoft Edge, or opt-in Windows TradingView Desktop. It brings saved layouts, alerts, Pine scripts, strategy reports, market data, watchlists, drawings, replay, and research tools into one local integration.
189 implemented tools · 184 enabled by default · 105 available in read-only mode · zero npm dependencies. Five generic UI mutation tools are separately enabled. Browse every tool or inspect its exact input schema.
This is an independent, MIT-licensed project. It is not affiliated with or endorsed by TradingView. It uses undocumented TradingView interfaces, so account features and future TradingView changes can affect compatibility.
Validation status
The project has automated unit, security, integration, real stdio-process, and real loopback-HTTP tests. A separate live check exercises read operations through Chrome and TradingView's public market endpoints. Current evidence, scope, and remaining limitations are recorded in validation, test results, and the security review of this release.
A successful API-presence check or read does not prove that every mutation works. Review the validation records before relying on a particular workflow. Webhook configuration verification does not prove delivery.
Current live limitations: alert creation returned invalid_request; the combined copy-and-alert workflow remains unverified live. Desktop rejected opening a new copy tab with CDP HTTP 500. Saved-copy receipts preserve the created ID for reconciliation, and full multi-pane copy fidelity remains unverified. These are separate from the verified chart, Pine, replay, template-list and screenshot operations. See Desktop results and browser results.
Related MCP server: tradingview
What it can do
Area | Examples | Notes |
Browser and diagnostics |
| Restricts targets to HTTPS TradingView chart pages. Screenshots go to your MCP client. |
Charts and indicators |
| Changes require the exact browser target and saved-layout ID. |
Saved layouts |
| Copy verifies an independent saved ID and compares observable chart contents. |
Alerts |
| Price thresholds, attached Pine strategy order fills, and discovered indicator conditions. Requests paused creation by default. |
Combined workflow |
| Copy, configure, save, create a JSON webhook alert, and independently read it back. Durable recovery keys. |
Chart data |
| Loaded chart history, rather than a promise of unlimited historical data. |
Strategy Tester |
| Requires exact strategy identity; reports freshness evidence separately. |
Pine |
| Editor/library operations use native interfaces and source/version preconditions. Table reads require the exact attached study ID. No external AI provider. |
Community Pine |
| Credential-free public topic feeds and exact public open-source versions. Returned content is untrusted; topic feeds are not full-text search. |
Market data |
| Public scanner calls use no TradingView account credentials. |
Watchlists |
| Ordered edits use explicit IDs and recovery checkpoints. Guide. |
Panes, templates, drawings, replay |
| Fidelity and availability depend on the native interface. |
Research and simulation |
| Local calculations and a supplied-price simulator; no real broker execution. |
Jobs and controls |
| Bounded jobs/polling. Emergency stop cannot undo an already submitted action. |
Requirements
Node.js 24 or later, with
nodeavailable to your MCP client. Check withnode --version.A local Chrome, Chromium, or Edge installation, or opt-in TradingView Desktop on Windows MSIX. Desktop support is verified for the installed 3.5.1 build; other versions require their own live check.
A TradingView account and the plan/data entitlements needed for your chosen account features.
An MCP client that can launch a local stdio server. Optional authenticated local HTTP is also available.
There is no npm install step, no install script, and no third-party runtime or development dependency tree. This repository is distributed as source; the README does not assume an npm-published package.
Quick start
git clone https://github.com/evgyur/tradingview-chip.git
cd tradingview-chip
node --version
npm run check
npm run audit:source
npm testStart the dedicated browser:
node src/cli.mjs launchSign in to TradingView in that new window, open a saved Superchart, and wait for it to finish loading. Then run:
npm run doctorThe launcher uses a dedicated profile at ~/.tradingview-unified-mcp/browser-profile, disables extensions for that launch, and exposes Chrome's debugger at http://127.0.0.1:9222. It accepts an empty directory or a profile previously created by this launcher. Chrome's remote-debugging feature requires a nondefault profile; see Chrome's documentation.
For another executable or profile:
node src/cli.mjs launch --browser "/path/to/chrome" --profile "/path/to/new-profile"You can also pass --url https://www.tradingview.com/chart/. On macOS, normal Google Chrome and Edge installation paths are detected. On Linux, common Chrome/Chromium executable paths are checked. On Windows, standard Chrome/Edge paths are checked; pass --browser explicitly for other installations. Windows Desktop 3.5.1 was live-tested within the scope recorded in the Desktop qualification.
Close the dedicated browser when you have finished using it. Its profile contains your browser-managed login session. Anyone who can access its debugger may control that browser session; keep the debugger on loopback and use a trusted local machine.
For the installed Windows MSIX Desktop app, node src/cli.mjs launch-desktop starts or reuses a verified TradingView Desktop debugger at http://127.0.0.1:9223. Set TV_CDP_ENDPOINT to that address for a separate MCP connection. It does not stop a running non-debug app, copy profiles, or bypass save prompts; close the app normally before launching if requested. The debugger gives local processes control over that session, so use a trusted computer. The Desktop 3.5.1 pilot verified chart controls, indicator/drawing changes, Pine save/open/compile, light validation, replay controls, template listing and screenshots with the window restored. This does not qualify every registered tool or another Desktop build.
Install the agent skill
The tradingview-chip skill tells an assistant how to select the exact chart, use MCP tools, and reconcile uncertain changes. The server supplies those tools; installing the skill alone does not start or connect the server.
For Codex, copy the complete skills/tradingview-chip directory into ~/.codex/skills/tradingview-chip (Windows: the same directory under your user home), or use your client's local skill installer. Refresh skill discovery as supported by that client. Keep the skill's support directories together with SKILL.md.
Then configure the MCP server below and start in read-only mode. A useful first prompt is: “Use tradingview-chip to list my chart tabs and read the selected layout without changing it.” See agent handoff for the first files and verification commands.
Connect your MCP client
Use your client's MCP configuration mechanism and replace both absolute paths below. Start in read-only mode:
{
"mcpServers": {
"tradingview-chip": {
"command": "node",
"args": ["/absolute/path/tradingview-chip/src/server.mjs"],
"env": {
"TV_CDP_ENDPOINT": "http://127.0.0.1:9222",
"TV_DATA_DIR": "/absolute/path/tradingview-chip/runtime",
"TV_READONLY": "1"
}
}
}
}If your client cannot find Node, replace command with the full path to your Node 24+ executable. Restart the client connection after configuration changes. Set TV_READONLY to "0" to expose mutation tools when you are ready to use them.
The client launches src/server.mjs as a child process; you normally do not run a second stdio server manually. For a protocol harness, node src/server.mjs accepts newline-delimited JSON-RPC on stdin and reserves stdout for protocol responses.
The server supports MCP protocol versions 2025-11-25, 2025-06-18, 2025-03-26, and 2024-11-05. Tool listing is paginated, with up to 100 tools per page; clients must follow nextCursor. Four Markdown resources and two workflow/security prompts are also discoverable through MCP.
Configuration
Setting | Default | Purpose |
|
| Literal HTTP loopback Chrome debugger. |
|
| Audit metadata, checkpoints, exports, backups, and local simulation data. Prefer an absolute path. |
| Unset | Set |
| Unset | Set |
| Dedicated profile under | Profile used by the launcher; |
|
| Port for |
| Unset | Required bearer secret of at least 32 characters for the HTTP transport. Use a randomly generated value. |
Settings come from the process environment. The server does not automatically load .env files. No TradingView password, cookie export, AI API key, or webhook credential is required in the server configuration.
Optional local HTTP
export TV_HTTP_TOKEN="$(node -e 'process.stdout.write(require("node:crypto").randomBytes(32).toString("hex"))')"
export TV_READONLY=1
node src/server.mjs --httpConfigure your HTTP-capable MCP client to use http://127.0.0.1:3811/mcp and supply Authorization: Bearer <the value of TV_HTTP_TOKEN> as a header. Keep that value in your client's secret configuration; never put it in a URL or commit it.
This transport accepts authenticated JSON POST /mcp. It checks Host, rejects browser Origin headers by default, bounds request sizes, and rejects redirects. GET/SSE, remote hosting, OAuth distribution, and browser-based login gateways are not implemented. Some HTTP clients insist on GET/SSE and will require stdio instead.
First calls
In your connected assistant, ask:
List my TradingView chart tabs. Read the selected chart's native layout ID and capabilities. Make no changes.
The assistant should call browser_list_tabs, choose an explicit target_id, and then call layout_get, chart_get_state, and browser_capabilities. Use tools_catalog with a prefix such as "alert_" to inspect exact schemas.
Example tool arguments:
{"target_id":"TARGET_FROM_BROWSER_LIST_TABS"}For mutations, supply the observed native ID as well:
{
"target_id":"TARGET_FROM_BROWSER_LIST_TABS",
"expected_layout_id":"NATIVE_ID_FROM_LAYOUT_GET",
"symbol":"NASDAQ:AAPL"
}Those are arguments for chart_set_symbol, not a standalone JSON-RPC request. Re-read the chart afterward. A changed target/layout identity stops a guarded mutation. A chart URL or title alone is insufficient identity.
Copy a chart and create a webhook alert
Inspect
browser_list_tabs,layout_get, andchart_get_state. Choose a saved source with the intended studies and inputs.Inspect
alert_sourcesfor the attached study identity and supported alert conditions. Price alerts require an explicit comparison and price.Validate the exact message with
alert_validate_messageand inspectalert_preparebefore submission.Run
workflow_copy_chart_create_alertwith one durableidempotency_key, an unused layout name, an HTTPS webhook URL, andmessage_format: "json".Check the returned independent layout ID, chart/save verification, alert ID, exact configuration checks, and active state. Re-read with
alert_getoralert_verify.Resume a paused alert only when its destination, message, and trigger are the intended configuration.
examples/copy-alert.json contains a complete argument shape for an attached strategy order-fill alert. Replace every placeholder and choose your own endpoint. The example requests active: false; the server never sends a webhook test request.
TradingView can momentarily activate an alert even when paused creation was requested; receipts report that possibility. Updating an already paused alert may re-arm it and requires explicit allow_temporary_activation when relevant. TradingView also applies account and webhook requirements, including two-factor authentication; see its webhook instructions.
Recover an uncertain operation
If you see UNCERTAIN_MUTATION, a timeout, cancellation, or disconnect after submission, preserve the exact request and idempotency key. Use workflow_status, the relevant read tools, and returned IDs to reconcile what exists before retrying. A new key can create another object.
Checkpoints prevent several classes of duplicate submission; they do not roll back server-side changes. Keep your runtime directory between reconnects. Jobs and polling streams are in memory and do not automatically resume after a process restart.
Strategy research
Read strategy_list and select an exact entity_id. For changes to symbol, timeframe, session, or inputs, capture a probe with strategy_capture, perform the intended change, then use strategy_wait with the expected context. Stable metric values alone do not establish recalculation freshness.
strategy_get_report and the paginated trade/order readers expose the native available report. Deep Backtesting and every historical equity sample are not guaranteed. strategy_scan and strategy_sweep run bounded research sequences with restoration attempts; review restoration results and remaining live-test limits.
Market data and exports
{"symbols":["NASDAQ:AAPL","BITSTAMP:BTCUSD"]}Use these arguments for quote_batch; no chart change or login is needed for the public scanner adapter. Exchange delays and quote timestamps are reported as limitations. See market data documentation for scanner filters, technical summaries, depth, and missing-data behavior.
Export tools return paths under TV_DATA_DIR/exports. JSON exports use hashed filenames; CSV exports use sanitized names and neutralize spreadsheet formula prefixes. Exported data and Pine backups can still be sensitive. Protect or delete them according to your own retention needs.
Data handling and security boundaries
The reviewed runtime has no telemetry, analytics SDK, cloud synchronization, automatic updater, external AI integration, cookie getter/exporter, arbitrary JavaScript tool, shell tool, or general-purpose HTTP proxy. The launcher passes a small allowlist of platform settings to Chrome and omits unrelated environment credentials and injection flags.
Data path | What travels | Destination |
Local CDP | Fixed page functions, typed arguments, chart data and results | Your loopback Chrome debugger. Discovery and debugger URLs are validated. |
Browser-managed account requests | Requested account reads/changes, Pine source for requested save/compile actions | Explicit first-party TradingView services. Login cookies remain managed by Chrome. |
Public scanner | Requested symbols, selected fields and filters | Fixed |
Public Pine community | Topic, type, page, public script ID and version | Fixed |
MCP output | Requested results, screenshots, source, and selected alert configuration | Your MCP client and any model/service that client uses. |
Local storage | Operation metadata, recovery state, requested exports/backups, simulation records |
|
Configured webhook | Alert message when TradingView fires it | The endpoint you deliberately configure in TradingView. This server does not send test deliveries. |
Browser fetch hosts are restricted to tradingview.com, www.tradingview.com, pricealerts.tradingview.com, pine-facade.tradingview.com, symbol-search.tradingview.com, and scanner.tradingview.com. Operations use fixed authored functions. Their source checks are defense in depth, not a sandbox for untrusted server code.
Audit logs store metadata such as tool name, outcome, duration, and object bindings, rather than raw tool arguments or webhook/message bodies. Recovery records and explicitly requested backups can contain chart, watchlist, and script information. Known secret fields and text patterns are redacted; arbitrary secrets inside screenshots, source, titles, or user content cannot be universally recognized. Trust your MCP client and model provider before requesting private content.
TradingView and Chrome perform their own network activity. This server does not act as a firewall for them. The security review is scoped to this source revision and tested paths, not a guarantee that no data can ever leave your computer. See SECURITY.md and the release security findings.
Troubleshooting
Symptom | Action |
| Start |
| Inspect |
| Re-read |
| Review and save the intended source configuration before copying. |
| Choose an empty profile directory or the launcher's existing dedicated profile. |
| Wait for Supercharts to load, inspect |
| Open Strategy Tester, confirm the exact attached strategy and context, and wait for computation. Review freshness evidence. |
Symbol change returns | Read the observed symbol and resolved instrument. TradingView can substitute another venue; exact-symbol guards refuse to call that a verified match. Use an explicitly intended available venue. |
Missing mutation tools | Set |
HTTP 401 / 403 | Supply the matching bearer header, connect using the literal configured loopback Host, and use a local MCP client without a browser Origin header. |
| Reconcile submitted writes, then call |
Logging warning after success | Preserve the returned receipt and repair storage permissions/disk space. The warning alone is not a reason to repeat a mutation. |
Development and verification
npm run check # Parse source/scripts/tests; validate runtime and tool schemas
npm run audit:source # Narrow static source/supply-chain gate
npm test # Full tests, including real local HTTP and stdio processes
npm run test:security # Security and protocol regression tests
npm run catalog # Regenerate tools, schemas, and counts
npm run test:live # Explicit live reads; requires the dedicated browser
npm run audit:release # Scan Git-tracked release files for secrets/private artifacts
npm run manifest # Regenerate release hashes after final validationTests use synthetic fixtures and local temporary directories. The ordinary test suite does not contact TradingView or start Chrome. test:live deliberately contacts the configured browser and public TradingView scanner; it saves an anonymized summary, with no raw account response, to docs/LIVE_VALIDATION.json. If multiple chart tabs are open, run node scripts/live-check.mjs TARGET_ID.
The CI workflow is configured for Linux and macOS with Node 24. Hosted jobs did not start during this release review, so the published passing test evidence comes from the local run. To contribute, add regression coverage for security-sensitive behavior, preserve exact-target and uncertainty guards, and update the generated catalog when changing tools. Do not commit browser profiles, cookies, session exports, credentials, runtime state, or account screenshots.
Documentation map
The specification includes design goals and acceptance requirements; the generated catalog and validation records describe what is implemented and tested.
Credits
tradingview-chip is separately implemented and draws on API research, workflow patterns, and feature ideas from these projects. Their upstream servers and dependency trees are not imported into this runtime.
Project | Contribution acknowledged |
TradingView browser API and workflow patterns. | |
Strategy report and metadata patterns; inherited original-project attribution. | |
Native saved-layout copying and internal service research. | |
Original CDP/native-interface research underlying several forks. | |
Feature and report-aggregation ideas. Its notices also credit LewisWJackson/tradingview-mcp-jackson. | |
Public scanner and hotlist API patterns. | |
Alert payload-construction concepts. | |
Surveyed feature/workflow reference. No source reuse because license provenance was unresolved in the reviewed revision. |
Pinned revisions and reuse decisions are recorded in SOURCES.md. Full retained MIT notices, original copyright statements, and inherited fork credits are in THIRD_PARTY_NOTICES.md.
License
MIT, with retained third-party notices. TradingView services, data, trademarks, account entitlements, and platform terms remain separate from this source-code license.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
ChartGaze is a service that connects AI assistants to live and historical market data and, with your authorization, to trading-account information and trading actions. It works with MCP-compatible AI tools and supports platforms such as MT5, MT4, cTrader, and crypto exchanges.
Read-only market charts, OHLC, backtests and a view of your connected broker accounts
Graded stock setups, options flow, and multi-window trend research over a hosted OAuth MCP endpoint.
Create and manage trading strategies, bots, webhooks and signals from any MCP client.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to control a local TradingView Desktop instance, providing tools to read chart state, change symbols and timeframes, and fetch OHLCV data.88 npm134MIT
- FlicenseNot gradedqualityDmaintenanceEnables automated control of TradingView Desktop via MCP, supporting morning briefs, chart analysis, Pine Script development, replay practice, and alert management.-
- FlicenseNot gradedqualityCmaintenanceProvides unified TradingView capabilities through one MCP server, including market data, screening, technical analysis, backtesting, sentiment, chart control via browser automation, Pine script transpilation and compilation, and alert webhooks.-
- AlicenseAqualityCmaintenanceEnables MCP clients to access market data from TradingView with automatic fallback to licensed providers, including symbol search, quotes, OHLCV history, technical indicators, and health checks.588 npmMIT