MCP TradingView Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| tv_get_historical_dataA | Fetch historical OHLCV (Open, High, Low, Close, Volume) bars for any symbol from TradingView. Supports stocks, crypto, forex, futures. |
| tv_get_quoteA | Get the latest price quote for a symbol: last OHLCV bar plus percentage change from the previous bar. |
| tv_get_indicatorsA | Compute technical indicators for any symbol. Includes RSI, MACD, Bollinger Bands (+ squeeze detection), EMA, SMA, ATR (+ stop levels), Stochastic, ADX (+DI/-DI), OBV, volume MA20/ratio, RSI divergence flags. Optional: weekly multi-timeframe context (include_weekly=true), relative strength vs benchmark (benchmark_symbol), composite technical score [-1,+1] (include_score=true). |
| tv_screenerA | Screen stocks, crypto or forex symbols by market, volume, RSI range. Markets include 'france' (Euronext Paris — PEA) and 'america' (Nasdaq / NYSE). Returns top matches with price, volume and RSI data. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool targets a distinct data need: historical bars, latest quote, indicator calculation, and symbol screening. The only potential overlap is RSI appearing in indicators and screener, but the intended use (computing vs scanning) is clear.
Three tools follow the `tv_get_*` verb-object pattern and all use consistent snake_case with a `tv_` prefix. `tv_screener` is the outlier because it uses a noun instead of an action verb, but it is still recognizable within the family.
Four tools is a reasonable, focused size for a market-data server, and each tool provides broad functionality (multi-symbol historical data, quotes, many indicators, and a screener). None feels redundant or unnecessary.
The server covers the core market-data workflow: retrieving history, checking current prices, computing technical analysis, and discovering symbols via screening. Minor gaps such as no dedicated symbol-search or fundamental data endpoint exist, but they are workable around for typical technical-analysis use cases.