trading-crew-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TV_DEBUG_HOST | No | Host for TradingView Desktop's Chromium debug port. | 127.0.0.1 |
| TV_DEBUG_PORT | No | Port for TradingView Desktop's Chromium debug port. | 9222 |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| chart_healthB | Symbol, timeframe, layout name and how many bars are loaded on the open chart. |
| get_quoteB | Latest candle (open, high, low, close, volume, time) of the open chart. |
| get_candlesA | Last N candles (up to 500) as a compact table {fields, rows}, oldest first, with unix times. For more than 500, use save_candles. Pass resolution (e.g. 60, 240, D) to read another timeframe; the chart is switched and then restored. |
| save_candlesB | Save up to 20000 candles of a timeframe to a JSON file and return its path, so analysis scripts can read exact data. Loads the full history if needed (M15 reaches back about 4 months). |
| find_pivotsC | Swing highs and lows with exact candle times and prices, from the last N candles of a timeframe. |
| suggest_chainB | Find a connected chain of swing points that no candle cuts through, on the chart's current timeframe. side "above" = falling chain over highs (red), "below" = rising chain under lows (green). Returns points to pass straight to draw_chain, with the same tolerance. |
| set_timeframeA | Change the chart timeframe (1, 5, 15, 60, 240, D, W). Set it back afterwards. |
| set_visible_rangeB | Scroll and zoom the chart to a time range (unix seconds). |
| list_drawingsC | Ids and names of all drawings on the chart. |
| draw_trend_lineC | Draw a straight line between two points (exact candle time and price). |
| draw_chainA | Draw a connected chain of straight lines through pivot points (each line starts where the last ended). side "above" = red chain over swing highs, "below" = green chain under swing lows. Refuses and reports the candles if any line would cut through a candle, unless force is true. |
| get_drawingC | Points, colour and width of one drawing by id. |
| draw_horizontal_lineC | Draw a horizontal line at a price. |
| remove_drawingC | Remove one drawing by id. |
| clear_drawingsA | Remove all drawings from the chart. |
| list_alertsA | All price alerts on the account: id, symbol, level, active, message, last fired. |
| create_alertA | Create a price alert that fires when price crosses a level. Refuses a level on the wrong side of live price, and reads the alert back to confirm the stored level. |
| modify_alertA | Change an alert's message and/or level in place (same id). Changing the level needs direction. Reads it back to confirm. |
| list_firesB | Alerts that have fired, newest first, with fire time and message. |
| screenshotB | Save a PNG of the TradingView window and return the file path. |
| delete_alertB | Delete one alert by id and confirm it is gone. |
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 21 tools
Most tools target a distinct resource+action (draw_* vs list/get/remove/clear_drawings, alerts CRUD, chart control, data reads). A few pairs are close: draw_trend_line vs draw_chain (single line vs connected pivot chain), and find_pivots vs suggest_chain (raw swings vs a validated chain), but the descriptions clearly separate these by input/output and purpose (suggest_chain explicitly hands off points to draw_chain). get_candles vs save_candles is well delineated by the 500-candle cap and file-export intent.
Almost all names follow a verb_noun or verb_noun_noun pattern (draw_trend_line, set_timeframe, list_alerts, create_alert, delete_alert, save_candles). The only deviations are the noun-style chart_health and screenshot, which break the verb-first convention but remain unambiguous. Minor deviation overall, not confusing.
At 21 tools the surface is at the upper end of what an agent can hold comfortably; the rubric's 16-25 band is borderline heavy. Each tool does earn a place (7 drawing, 5 data, 5 alerts, 4 chart/screenshot), so it is justified by breadth of functionality rather than padding. Still, some consolidation (e.g. a single draw tool with a type parameter, or merging get_drawing into list_drawings) could trim the set.
Drawings have full lifecycle (multiple create types, list, get, remove, clear) and alerts have near-complete CRUD plus fired-history, with data reads, pivots, screenshots, and chart state all covered. Notable gaps: no way to edit/move an existing drawing (only delete and redraw), no alert enable/disable toggle despite 'active' being listed, and no tool to change the chart symbol (only timeframe), which agents might expect on a trading server. These are workable around but real.