mcpbeat Sign in

Charts by Szum MCP Server

answering

Charts by Szum is answering right now. Last checked moments ago. It exposes 13 tools.

Create, inspect, manage, and render charts and data visualizations as SVG/PNG or interactive embeds.

Uptime history 47 days of history
47 days agonow
100.0%
Uptime 24h
92 of 92 checks
13
Tools
read from the server
1100 ms
Response time
average over 24h
open, no key
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Charts by Szum every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 0 min ago.

run in your terminal
claude mcp add charts --transport http https://szum.io/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "charts": {
      "url": "https://szum.io/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.charts]
url = "https://szum.io/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "charts": {
      "url": "https://szum.io/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "charts": {
      "url": "https://szum.io/mcp"
    }
  }
}

Available tools 13

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

chart
delete_chart
Use this when the user explicitly wants to permanently delete one saved chart. Deletion cannot be undone, and retrying an already completed deletion succeeds; requires authentication.
get_chart
Use this when the user identifies a saved chart by id and wants to view it or retrieve its metadata and URLs. Displays the published chart when available and does not return its config; requires authentication.
get_chart_config
Use this when the user identifies a saved chart by id and needs its complete published Szum config for inspection or reuse. Does not return a newer editor draft; requires authentication.
update_chart
Use this when the user wants to replace and publish a saved chart's config while keeping its id and URLs. Validate each generated or changed config once before rendering, saving, or updating. Do not revalidate unchanged input; a successful render preflights it for later saves or updates. Errors block; warnings require explicit user approval for the exact config. Suggestions do not block. Replace the complete config with suggestedConfig and revalidate before repair. Refuses charts with unpublished editor changes; requires authentication and saved-chart storage.
charts
list_charts
Use this when the user wants to find charts in their saved library. Returns paginated metadata and URLs, not chart configs; requires authentication. Draft-only editor charts have publishedAt null, hasDraft true, and sizeBytes 0 because sizeBytes measures only the stored published config, not draft storage.
examples
get_examples
Use this when the model needs current, ready-to-use Szum chart configs or preferred semantic patterns. Optionally filters examples by mark type.
marks
list_marks
Use this when choosing or configuring chart mark types. Returns every available mark with its properties and defaults.
preview
get_preview_state
Use this when the Szum chart App needs to restore a rendered preview as its current transient or saved view. It is read-only, owner-scoped when authenticated, and hidden from the model.
rename
rename_chart
Use this when the user wants to change a saved chart's library title without changing its config, publication state, or public URLs; requires authentication.
render
render_chart
Use this when the user wants to preview or generate a chart. Validate each generated or changed config once before rendering, saving, or updating. Do not revalidate unchanged input; a successful render preflights it for later saves or updates. Errors block; warnings require explicit user approval for the exact config. Suggestions do not block. Replace the complete config with suggestedConfig and revalidate before repair. Stores a 1 hour preview and returns public image URLs. Authenticated previews use the account's render allowance, and each image produced from a returned URL is another render. Anonymous previews are complimentary; their images use the anonymous image allowance.
save
save_chart
Use this when the user wants to permanently save and publish a chart from a Szum config. Validate each generated or changed config once before rendering, saving, or updating. Do not revalidate unchanged input; a successful render preflights it for later saves or updates. Errors block; warnings require explicit user approval for the exact config. Suggestions do not block. Replace the complete config with suggestedConfig and revalidate before repair. Supply one idempotencyKey per intended chart and reuse it for retries. Returns permanent public Image and Embed URLs plus Edit and Studio links; requires authentication and saved-chart storage.
themes
list_themes
Use this when choosing a visual theme for a chart. Returns every available theme and guidance on where each works best.
validate
validate_chart
Use this when a chart config will be rendered, saved, or updated. Validate each generated or changed config once before rendering, saving, or updating. Do not revalidate unchanged input; a successful render preflights it for later saves or updates. Errors block; warnings require explicit user approval for the exact config. Suggestions do not block. Replace the complete config with suggestedConfig and revalidate before repair. Read-only, free, and fast.

Endpoints

URLTransportStateLatencyChecked
https://szum.io/mcp streamable-http answering 1094 ms 0 min ago

Alternatives to Charts by Szum

same job, measured the same way
Chart Canvas
by gluip

Create interactive visualizations and query data sources (SQLite, CSV, Parquet, JSON)

41 installs/wk local only
ChartPane
by ahmadsl

Renders interactive Chart.js charts and dashboards inline in AI conversations.

answering
Semiotic
by nteract

Verified React chart generation: select, validate, repair, render, and inspect charts through MCP.

5 777 installs/wk 5 tools answering
Plots MCP
by mr901

MCP server for data visualization with Mermaid charts.

124 installs/wk local only
MCP Plots
by mr901

MCP server for data visualization with Mermaid charts.

local only
Apivideo
by usefulapi

Manage videos and live streams, inspect captions, players and webhooks, and read play analytics.

15 tools answering
Blueprint Chart
by blueprint-chart

The open chart format an LLM writes and the browser renders — to interactive, accessible SVG.

48 installs/wk local only
MCP Dashboards
by kyurish

45+ interactive charts, dashboards, flowcharts, and KPIs inside any AI conversation

425 installs/wk local only

Charts by Szum — questions

Answers built from our own checks of this server.

What can Charts by Szum do?
It exposes 13 tools, read directly from the server on our last check. Among them: delete_chart, get_chart, get_chart_config, get_examples, get_preview_state, list_charts and 7 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Charts by Szum working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 1100 ms. The bar chart above shows every period we have measured.
How do I connect Charts by Szum?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Charts by Szum need an API key?
No. Charts by Szum completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 13 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Charts by Szum?
It answers our handshake in 1100 ms on average, which is faster than 7% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.