Hosted MCP

TradingView data, inside your LLM

A hosted Model Context Protocol server that lets Claude, Cursor, OpenClaw, Hermes Agent, and any other MCP client pull quotes, screener results, OHLCV bars, and deep structure analysis straight from TradingView — no browser, no chart, no paste-and-pray prompts.

https://tvremix.xyz/api/mcp/v1

Headless by design

No TradingView tab. No Chrome extension. Just an HTTPS endpoint.

Batteries included

Quotes, technicals, screener, OHLCV, SMC/swing analyzers, news, calendars, and web search — all in one server.

Real bar data

OHLCV comes from TradingView's own WebSocket feed — same data the chart uses.

Works with the agents you already use

tvremix speaks standard Model Context Protocol over Streamable HTTP, so any MCP-compatible client can talk to it out of the box — no plugin, no custom SDK, no bridge.

Claude Desktop & Claude.ai

Anthropic's desktop app and the web UI both support tvremix as a remote Custom Connector — add the URL, click Allow, done.

Cursor

The AI-native IDE. Drop tvremix into ~/.cursor/mcp.json and every chat thread can pull live market data into your code.

OpenClaw

The viral self-hosted personal AI assistant (formerly Clawdbot). Wire tvremix into openclaw.json and chat with it via Telegram, WhatsApp, or Slack.

Hermes Agent

Nous Research's terminal-native agent. Add tvremix to ~/.hermes/config.yaml and call every tool as mcp__tvremix__*.

MCP Inspector

Anthropic's official debugging UI. Paste the URL, paste your key, click Connect — a 10-second sanity check for any new setup.

Anything else MCP-native

Windsurf, Cline, Zed, Continue, Codex, VS Code Copilot, Goose… if it speaks MCP over HTTP, it works.

Two ways to sign in

Pick whichever matches your client. You can use both on the same account.

Agents· Claude Desktop, Claude.ai web

OAuth 2.1

Paste the URL into your agent's Custom Connector dialog. The app registers itself automatically, bounces you through tvremix.xyz to approve, and receives short-lived access plus refresh tokens. Nothing to copy, nothing to rotate.

CLI & IDEs· Cursor, OpenClaw, Hermes, Inspector

API key

Generate a tvr_… token on your account page, then add it as an Authorization: Bearer … header in your client config.

Ready-made workflows

We ship a prompt library alongside the MCP — 8 battle-tested TradingView workflows you can run from day one, whether you're in Claude Code or pasting into any other MCP-capable agent.

Claude Code· plugin

tvremix/claude-plugin

One command installs the whole library as /tvremix:smc, /tvremix:swing, /tvremix:options, and more. Auto-wires the MCP server via OAuth — nothing to copy.

claude plugin marketplace add tvremix/claude-plugin
claude plugin install tvremix
View all 8 commands →
Any MCP agent· copy & paste

Prompt catalog

Using Cursor, Claude Desktop, OpenClaw, Hermes, Cline, or anything else? Browse the same 8 workflows as copy-paste prompts. Each card includes the full prompt body and the tool sequence it runs.

Open the prompt catalog →

Connect in 60 seconds

Pick your client below and follow the snippet.

Claude Desktop and Claude.ai web both sign in to tvremix over OAuth — there's no JSON file, no API key, and no mcp-remote proxy involved.

Paste this URL:
https://tvremix.xyz/api/mcp/v1
  1. Open Settings → Connectors (Claude.ai web) or Settings → Connectors → Add custom connector (Claude Desktop).
  2. Paste the URL above and click Add.
  3. Your browser opens tvremix.xyz/oauth/authorize — sign in (if you aren't already) and click Allow.
  4. Claude stores a short-lived access token plus a refresh token. That's it — call any tvremix tool straight from chat.

Revoke access any time from your account page. Tokens refresh automatically; you'll never need to re-enter credentials.

What you can do with it

A headless wrapper around TradingView's public APIs plus our own bar-based analyzers.

Quotes & fundamentals

Real-time snapshot pricing, P/E and valuation metrics, analyst price targets, and recent SEC filings (10-K, 10-Q, 8-K) with full-text access.

Technicals

Per-interval indicators (RSI, MACD, moving averages, Bollinger), aggregated buy/sell ratings, and multi-timeframe trend alignment with a confluence score.

Bars & market structure

Historical OHLCV from TradingView's own feed, Smart Money Concepts analysis (BOS, CHoCH, order blocks, FVGs), swing structure, and real log-return correlation between symbols.

Screener & scanning

The full TradingView screener, plus higher-level tools that rank symbols by setup type, compare instruments side-by-side, and analyse sectors or industries.

News & calendars

Symbol news with full story text, the macro economic calendar with importance filtering, and earnings and dividend calendars.

Options & web

Options expirations and full chains with IV, Greeks, OI, and volume — plus a general-purpose web search for news, research, and macro context.

Connect a client to browse the full tool schema — names, parameters, and JSON-Schema types are discoverable via the MCP tools/list method.

Limits & pricing

PriceFree during Public Beta
Rate limit60 requests / minute / key
Active keys per account5
OHLCV max bars per call5,000
Data freshnessLive (5m–1h cache, varies by bar size)

FAQ

How is this different from the Chrome extension?

The extension runs alongside a real TradingView tab and can drive the chart (draw, place alerts, watchlists, execute paper trades). The MCP is headless and focused on data — great for agents, Claude/Cursor, and anything server-side that doesn't want a browser in the loop.

OAuth or API key — which should I use?

If your client has a Custom Connector / remote-MCP dialog (Claude Desktop, Claude.ai web), use OAuth — tokens rotate automatically and there's nothing to copy. If you're wiring tvremix into a CLI tool, IDE, or JSON-configured agent (Cursor, OpenClaw, Hermes, Inspector, home-rolled scripts), use an API key. They authenticate against the same account.

Does it work with OpenClaw, Hermes Agent, Windsurf, Cline, or other MCP clients?

Yes. tvremix is a vanilla MCP server over Streamable HTTP, so every MCP-compatible agent can use it. We keep copy-paste snippets above for Claude, Cursor, OpenClaw, and Hermes Agent; other clients (Windsurf, Cline, Zed, Continue, Goose, Codex, VS Code Copilot) use the same URL plus either OAuth or an Authorization header.

Where does OHLCV data come from?

Directly from TradingView's own WebSocket feed — the same data the chart renders. No third-party aggregators, no delayed / stale mirrors. Bars are cached briefly (30s–6h depending on interval) to keep latency and TV's backend happy.

Can I call authenticated endpoints like my alerts or watchlists?

Not today — the hosted MCP only covers public TradingView data. For now, alerts, watchlists, and paper trading are handled through the Chrome extension. We're exploring ways to bring more of that surface to the MCP in the future.

Is my API key safe?

We store only a SHA-256 hash of your key, never the raw value. The secret is shown once at creation and never again; rotate it from the account page at any time. Every request is authenticated and rate-limited per-key.

How do I handle rate-limit responses?

Rate-limited requests return HTTP 429 with a Retry-After header (seconds). Back off for that window and retry. Most MCP clients (Claude, Cursor) handle this automatically.