Futures MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TRADINGVIEW_URL | No | URL of your saved TradingView layout, used in session capture mode. | |
| FUTURES_MCP_DATA_DIR | No | Absolute path to the data directory used by the server (e.g. for cached bars and captured charts). | |
| TRADINGVIEW_SESSION_ID | No | Your TradingView sessionid cookie, used in session capture mode with your saved layout. | |
| FUTURES_MCP_DEFAULT_MODE | No | Default capture mode: 'anonymous' or 'session'. If unset, uses session when a TradingView session cookie is configured and anonymous otherwise. | |
| FUTURES_MCP_DETECTOR_DIR | No | Directory containing the private range detector module (range_screener_v6.py). Defaults to ./private. | ./private |
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_futures_barsA | OHLCV bars for a trading-day window, with Relative Volume (volume/SMA14), its zone, the session each bar belongs to, and per-day summaries. |
| capture_chartA | Screenshot of the TradingView chart framed on exactly the trading-day window. Takes 20-40 seconds. |
| analyze_rangeA | Detect a range in the window. Verdict: COMPLETED (a range met every rule), NOT_COMPLETED (a range is forming but not yet confirmed), or NO_RANGE. Each structure lists support, resistance, its numbered rejections and, if price has left it, when it broke. |
| get_range_chartA | The TradingView chart for the window with the detected range drawn on it (support/resistance box, numbered rejections, caption), plus the report. Takes 30-50 seconds. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| range_check | Check a symbol for a range setup and show it on the chart. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| symbols | Symbols the tools accept |
| status | Capture mode, detector and OCR availability |
| chart_view | Inline chart view for MCP Apps hosts |
TDQS
Scored across 4 tools
Each tool has a clear primary purpose: retrieving bar data, performing range analysis, and capturing chart images. The only potential confusion is between capture_chart and get_range_chart, but the descriptions make clear that one is a raw screenshot while the other includes the detected range and report.
All tool names follow a consistent verb_noun pattern: get_futures_bars, analyze_range, capture_chart, get_range_chart. The naming style is uniform and predictable, with no mixing of conventions.
Four tools is somewhat lean, but appropriate for a focused futures charting and range-analysis workflow. Each tool fills a distinct step in the process, and the small count keeps the server manageable.
The server covers the core workflow of retrieving bars, detecting a range, and viewing charts. Minor gaps exist, such as no obvious tool for listing available futures instruments or configuring window parameters, but these do not severely block the intended use case.