chart-img-mcp

A Model Context Protocol (stdio) server for CHART-IMG — TradingView chart snapshots via https://api.chart-img.com. API reference: doc.chart-img.com.

Existing MCPs?

Public MCP listings include TradingView chart servers that drive a browser (e.g. Selenium) or QuickChart / ECharts — they are not the official CHART-IMG REST API. This package wraps chart-img.com similarly to how binance-mcp wraps the Binance SDK.

Related MCP server: Quick Chart MCP Server

Prerequisites

• Node.js 20+

• pnpm

Install

cd chart-img-mcp
pnpm install
cp .env.example .env
# Set CHART_IMG_API_KEY in .env (from chart-img.com)
pnpm run build

Run (stdio)

pnpm start
# or
node dist/index.js

Cursor / IDE

Add a server entry (do not commit real keys):

{
  "mcpServers": {
    "chart-img": {
      "command": "node",
      "args": ["/absolute/path/to/auto_trade/chart-img-mcp/dist/index.js"],
      "env": {
        "CHART_IMG_API_KEY": "your-api-key"
      }
    }
  }
}

Dev without building:

"command": "pnpm",
"args": ["exec", "tsx", "src/index.ts"],
"cwd": "/absolute/path/to/auto_trade/chart-img-mcp"

MCP resources

Static snippets stay accurate for common bumps; the live manual remains the source of truth for full parameter lists and indicator/drawing schemas.

Tools

Resolution: v2 chart requests use CHART_IMG_MAX_WIDTH / CHART_IMG_MAX_HEIGHT (default 800×600) to clamp width/height before calling the API, avoiding HTTP 403 when the plan’s max resolution is exceeded. When clamping happens, the JSON response includes _chartimgMcp.dimensionClamps.

Optional v2 headers: tradingviewSessionId + tradingviewSessionIdSign for TradingView subscription data (see CHART-IMG docs).

If CHART_IMG_API_KEY is unset, only chartimg_tools_disabled is registered with a short hint.

Auth (per CHART-IMG)

• v1: Authorization: Bearer <key> (this server uses the header).

• v2 / v3: x-api-key: <key>.

Limits

Rate limits, max image dimensions, and storage TTL depend on your CHART-IMG plan — see Request limits in the official docs.

License

MIT