Skip to main content
Glama

Chart-Output MCP Server

MIT License npm

Render charts as PNG, SVG, or WebP images directly from Claude, Cursor, Windsurf, or any MCP-compatible AI agent.

Ask your AI: "Generate a bar chart showing Q1–Q4 revenue" — it calls Chart-Output and returns the image inline.

What it produces

Ask your AI agent to generate a chart. This is what comes back.

MRR breakdown chart example

(If the image does not load in your viewer, open the file on GitHub.)

Related MCP server: Quick Chart MCP Server

Examples

Ready-to-use chart configs in /examples. Copy any file, swap in your data, POST to the API.

Install

Add to your mcp.json:

{
  "mcpServers": {
    "chart-output": {
      "command": "npx",
      "args": ["@chartoutput/mcp"],
      "env": {
        "CHART_OUTPUT_API_KEY": "pk_test_YOUR_KEY"
      }
    }
  }
}

Get a free API key at chart-output.com — no credit card required.

Tools

Tool

Description

list_chart_output_examples

Shipped example spec ids — use before hand-writing render_card JSON

get_chart_example

Return full examples/<id>.json text (valid API body shape)

render_chart

Chart.js-style labels/datasets → inline image (optional extensions for partial dashboard fields)

render_chart_url

Same as render_chart → CDN URL instead of bytes

render_card

Full card composition JSON → inline image (header, KPI strip, footer, theme, backgroundColor, etc.); spec is POSTed verbatim to /api/v1/render

render_card_url

Same full card composition as render_card → CDN URL instead of bytes

render_chart_ai

Natural language + data → image (Pro/Business key required)

MCP resources also expose the same files as application/json at chart-output://examples/<id> (e.g. mrr-breakdown). Prefer get_chart_example or a resource read over guessing the schema.

Example

Once installed, just ask your AI agent:

"Create a line chart showing monthly active users growing from 12k in January to 28k in December"

The agent calls render_chart, render_card, or render_chart_ai and returns the image directly in chat. No code required. Use render_card for branded dashboard layouts (dark theme, KPI row, footer), or render_card_url when you need an openable/shareable link.

API Key

  1. Sign up at chart-output.com

  2. Go to Dashboard → API Keys → Create key

  3. Add it to your mcp.json as shown above

Free trial includes 500 renders. No credit card required.

Glama

Registry listing and quality card:

chart-output-mcp MCP server

Available Tools

3 tools
render_chartC

Render a chart from a Chart.js JSON specification. Returns the chart as an inline image. Supports line, bar, pie, doughnut, radar, and polarArea chart types.

Inputs: type (required), labels (required), datasets (required), width, +3 more.

render_chart_aiB

Generate a chart from a natural language description and optional raw data. Chart-Output's AI layer builds the chart spec automatically. Requires a Pro or Business API key.

Inputs: description (required), data, width, height, +1 more.

render_chart_urlA

Render a chart and return a CDN URL instead of image bytes. Use this when you need a stable URL to embed in HTML, email, or pass to another tool. Same inputs as render_chart.

Inputs: type (required), labels (required), datasets (required), width, +3 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.6/5.0

    Scored across 3 tools

    Disambiguation4/5

    The three tools have clearly distinct purposes: render_chart for direct JSON specification rendering, render_chart_ai for AI-generated charts from natural language, and render_chart_url for URL-based output. However, render_chart and render_chart_url share the same input format, which could cause minor confusion about when to use each, though their different outputs (inline image vs. URL) help differentiate them.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with 'render_chart' as the base, extended with suffixes (_ai, _url) to indicate variations. This predictable naming makes it easy for an agent to understand the tool relationships and select the appropriate one based on the suffix.

    Tool Count5/5

    With only 3 tools, this server is well-scoped for its purpose of chart rendering. Each tool serves a distinct use case (direct rendering, AI generation, URL output), and there are no extraneous tools. The count is appropriate for covering the core functionalities without being overwhelming or insufficient.

    Completeness4/5

    The tool set covers the main chart rendering workflows: direct specification, AI-assisted generation, and URL-based output. A minor gap is the lack of tools for chart editing, deletion, or management (e.g., updating or deleting rendered charts), but for a rendering-focused server, the provided tools are sufficient for most agent tasks.

    Related MCP Connectors

    Related MCP Servers