candlestick-chart-mcp

An MCP server that renders OHLCV data as a candlestick chart PNG and returns it as inline image content, so the model can actually look at the chart it asked for.

It is a pure renderer: no network access, no API keys, no market-data provider. You pass the bars in; it draws them.

Install

npm install
npm run build

Verify it end to end (spawns the server over stdio and calls the tool for real):

npm run check

Render sample charts to out/ to eyeball the output:

npm run smoke

Related MCP server: KLinePic MCP Server

Register with a client

Claude Code:

claude mcp add candlestick-chart -- node /absolute/path/to/candlestick-chart-mcp/dist/index.js

Or in a config file (.mcp.json, claude_desktop_config.json, …):

{
  "mcpServers": {
    "candlestick-chart": {
      "command": "node",
      "args": ["/absolute/path/to/candlestick-chart-mcp/dist/index.js"]
    }
  }
}

The tool

render_candlestick_chart

Returns two content blocks: a short text summary (bar count, date range, OHLC, percent change, plus any notes about inputs that were adjusted) and the PNG.

Bars. candles accepts either form per bar, and mixing them is fine:

{ "time": "2026-01-05", "open": 100, "high": 103.2, "low": 99.4, "close": 102.8, "volume": 1200000 }

[1767571200, 100, 103.2, 99.4, 102.8, 1200000]

The tuple form is [time, open, high, low, close, volume?] and costs far fewer tokens — prefer it for anything longer than a handful of bars. time takes epoch seconds, epoch milliseconds, or any string Date.parse understands. Bars are sorted by time; a high/low that contradicts the body is clamped rather than rejected.

Everything else is optional:

Example call:

{
  "candles": [[1767571200, 100, 103.2, 99.4, 102.8, 1200000], "…"],
  "title": "BTCUSD · 1D",
  "sma": [20, 50],
  "bollinger": { "period": 20, "stdDev": 2 },
  "priceLines": [{ "price": 61941.5, "label": "resistance" }],
  "markers": [{ "time": "2026-02-14", "side": "buy", "label": "entry" }],
  "yScale": "log",
  "timeZone": "Europe/Riga"
}

Inputs that cannot be honoured do not fail the call — an SMA period longer than the series, a missing volume column, a log scale with non-positive prices, an unknown time zone are each dropped or downgraded and reported in the text block.

Colour

Up/down is a polarity encoding, so the default diverging scheme uses the blue ↔ red diverging pair. That pair clears the all-pairs colourblind gate in both themes (CVD ΔE 21.6 light / 19.2 dark against a ≥ 8 target). The traditional green/red pair fails it at ΔE 4.1 for deuteranopia, so classic ships with hollow up-bodies: shape carries the direction and hue only reinforces it. mono drops hue entirely — ink, hollow versus filled — for print and forced-colours contexts.

With the up/down pair already on screen there is no room left for a palette of overlay hues: every candidate measured below the normal-vision floor against one of the poles. So all overlays share one validated accent per scheme, and their identity comes from dash pattern + legend + a direct label at the end of each line. Four overlays are distinguishable; a fifth reuses a dash pattern and the response says so.

Volume bars inherit the bar's direction at half strength so the panel stays recessive, and it is a separate panel — never a second y-axis on the price plot.

Layout notes

• Bars sit on an ordinal x-axis (one slot per bar), so weekends and market holidays leave no gaps. Time labels appear where the label actually changes; intraday charts substitute the date wherever the day rolls over.

• Below ~3.5 px per bar, bodies are dropped and each bar becomes a single high-low hairline — a 1200-bar chart stays readable.

• Bodies cap at 26 px wide so a seven-bar chart still looks like candles.

• The PNG is capped near 4.5 MB; a request that would exceed it is re-rendered at scale: 1 and, failing that, returns an error asking for smaller dimensions.

Layout of the source

Adding an indicator panel (RSI, MACD) means adding a panel band to the layout block in renderChart and a series function in indicators.ts.

License

MIT