chart-img-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CHART_IMG_API_KEY | Yes | Your API key from chart-img.com. Required for authentication. | |
| CHART_IMG_MAX_WIDTH | No | Maximum width for v2 chart images (default 800). | 800 |
| CHART_IMG_MAX_HEIGHT | No | Maximum height for v2 chart images (default 600). | 600 |
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
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| chartimg_v1_mini_chart_storageB | CHART-IMG v1: save a TradingView mini chart to public storage; returns JSON with |
| chartimg_v1_advanced_chart_storageC | CHART-IMG v1: save an advanced chart to public storage; returns JSON with |
| chartimg_snapshotA | Preferred for agents: one-call TradingView snapshot (v2 advanced → storage). Supply a full |
| chartimg_v2_advanced_chart_storageA | CHART-IMG v2: POST advanced chart to storage; returns JSON with hosted image URL (POST /v2/tradingview/advanced-chart/storage). Prefer |
| chartimg_v2_advanced_chart_imageA | CHART-IMG v2: POST advanced chart and return base64 image data (POST /v2/tradingview/advanced-chart). Responses can be large; prefer storage tools. Width/height in |
| chartimg_v2_layout_chart_storageA | CHART-IMG v2: render a shared TradingView layout to storage (POST /v2/tradingview/layout-chart/storage/{layoutId}). Layout must be shared unless session cookies are provided. Width/height in |
| chartimg_v2_layout_chart_imageA | CHART-IMG v2: POST shared layout chart image as base64 (POST /v2/tradingview/layout-chart/{layoutId}). Prefer storage variant. Width/height in |
| chartimg_v3_exchange_listA | CHART-IMG v3: list TradingView exchange ids (GET /v3/tradingview/exchange/list). |
| chartimg_v3_exchange_symbolsA | CHART-IMG v3: symbols for an exchange (GET /v3/tradingview/exchange/{exchangeId}). Note: |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| chart_img_docs_quick_reference | Curated CHART-IMG notes for AI agents: auth, resolution/storage limits, symbols, v3 caveats, common errors. Full manual: https://doc.chart-img.com/#introduction |
TDQS
Scored across 9 tools
The exchange and layout tools are reasonably distinct, but v1_advanced_chart_storage, v2_advanced_chart_storage, and chartimg_snapshot all cover saving advanced charts to storage, creating real overlap. Versioning and 'prefer snapshot' guidance help, but agents may still misselect among them.
Most tools follow a predictable chartimg_{vX}_{feature}_{output} pattern, which makes versions and storage/image output modes easy to identify. chartimg_snapshot breaks the pattern, but it is the only notable deviation.
Nine tools is a reasonable size for a chart-image service, covering snapshots, storage, image output, and exchange metadata. The count is slightly padded by redundant v1/v2/snapshot storage variants, but still within an appropriate range.
Core workflows are covered: one-call snapshot, advanced and layout charts, storage URLs, base64 output, and exchange lookup. Minor gaps exist such as no direct mini-chart image output and the exchange-symbols payload being unreliable, but agents can work around these.