szum
About
Render chart images from JSON configs with six themes, ten marks, PNG/SVG output.
Details
- Author
- Unknown
- Categories
- Developer Tools, Knowledge Base, Other, Design
Jump to
Connect ChatGPT, Claude, Cursor, VS Code, and other AI agents to the Szum chart design system.
The Szum MCP server gives AI agents the shared chart grammar, curated themes, current examples, validation, and rendering tools they need to produce considered charts reliably.
After connecting, ask for a chart in ordinary language:
Show quarterly revenue by region as an editorial bar chart. Cite the source and save the finished chart.
The agent can discover the available marks and themes, build and validate the definition, render an interactive temporary preview in compatible clients, or save permanent image and embed links.
These steps use the ChatGPT Desktop plugin flow. Plugin availability can depend on your ChatGPT plan, workspace permissions, and rollout.
OpenCharts by Szum in Claude's Connectors Directoryand chooseConnect.
Claude may ask you to authorize Szum when you use tools that access your saved charts. Anonymous previews work without a Szum account.
- Choose a server name, replaceSERVER_NAMEin the command below, and run it in your terminal.
- Open Claude Code and enter/mcp.
- Select the server you added and complete the browser authentication flow.
claude mcp add --transport http SERVER_NAME https://szum.io/mcp
- Open your global~/.cursor/mcp.json, or a project's.cursor/mcp.json.
- ReplaceSERVER_NAMEwith your chosen server name, add the configuration below, and save the file.
- Reload Cursor if needed, then complete authentication when Cursor requests it.
{ "mcpServers": { "SERVER_NAME": { "type": "http", "url": "https://szum.io/mcp" } } }
- Open the Command Palette and runMCP: Add Server.
- ChooseHTTP, paste the endpoint, and set the server name.
- Choose whether to install it globally or in the current workspace.
- Start the server, confirm that you trust it, and complete authorization when prompted.
{ "servers": { "SERVER_NAME": { "type": "http", "url": "https://szum.io/mcp" } } }
save_chart,list_charts,get_chart,get_chart_config,update_chart,rename_chart, anddelete_chartrequire OAuth or an API key.get_chartaccepts an id returned bylist_charts; it does not expose the config in its model-visible result. For published charts, the server may load that config privately so clients with MCP Apps can display the chart inline.get_chart_configreturns the same complete published config as the SDK'scharts.getConfig(id). It does not substitute a newer editor draft, and a draft-only chart has no published config.update_chartvalidates and republishes a replacement config while keeping the chart id and public URLs stable. It refuses the update when unpublished editor changes exist, so it cannot silently discard a newer draft.rename_chartchanges only the library title; it does not alter the rendered title inside the config.delete_chartpermanently removes one chart and is retry-safe when that chart is already gone. Draft-only and unpublished charts remain available throughget_chartas metadata but have no public chart to display.
save_chartreturns the saved chart id. For an agent-initiated save, send one stableidempotencyKeyfor the intended chart and reuse it on retries; the same key and config return the same chart, while the same key with a different config returns a conflict. Saved MCP charts appear inStudio, where you can preview, edit, rename, share, or delete them. Their image and embed URLs follow the same behavior as othersaved charts.
In clients that support MCP Apps, a transient preview includesPNG,SVG, andSave permanentlyactions. The format actions use/r/{id}.pngand/r/{id}.svgURLs that remain available for 1 hour; each produced image may be cached for 1 hour. Saving reuses the exact previewed config and may ask you to connect your Szum account. In other clients, ask the agent to save the chart once you are happy with it.
Validate each generated or changed config once before its next render, save, or update. Validation applies to that exact config, so it should not be repeated while the config remains unchanged.render_chart,save_chart, andupdate_chartalso return the complete validation result alongside success. If one returnsstatus: "review_required", show the warnings to the user and continue withacknowledgeWarnings: trueonly after they approve that exact config; no render is charged and no chart is written before approval. A successful render preflights that exact config for a later save or update.
validate_chartreturns each issue separately with apatharray and message so clients can identify the exact field without parsing the text fallback. Fixability is independent from severity: a blocking error or non-blocking suggestion may includesuggestedConfig. That field is the complete verified next definition, not an internal patch. Replace the current config with it and callvalidate_chartagain before rendering, saving, or updating. The replacement may retain unrelated errors, and nothing is applied automatically.
Tool failures use a stable JSON text envelope withstatusand anerrorcontainingcode,message, andretryable. Error results omitstructuredContentso they cannot violate each tool's advertised success schema; validation failures and warning review responses include the fullvalidationobject in that JSON.
SeeValidation and Reviewfor error, warning, and suggestion semantics across every Szum workflow.
No credentials are needed to connect, inspect the design system, validate definitions, or render interactive previews in compatible clients. OAuth-capable clients can authorize access through your Szum account when saving, listing, opening, reading, updating, renaming, or deleting charts from your library.
If a client does not support OAuth, create an API key and send it as a Bearer token:
{ "mcpServers": { "SERVER_NAME": { "type": "http", "url": "https://szum.io/mcp", "headers": { "Authorization": "Bearer YOUR_API_KEY" } } } }
SeeAuthenticationfor the complete model.
An OAuth or API-keyrender_chartpreview counts against the signed-in user’splan limit. Each image subsequently produced from its temporary URL is another render against that account. Anonymous interactive previews are complimentary; their temporary image URLs use a separate IP-based allowance of 250 images per month, only when the URL is fetched and the image is produced.
A chart design system built around one shared definition, curated themes, and consistent output across images, Figma, and interactive embeds.
Create, customize, export, and publish a Szum chart in your browser. No signup required to start.
This is a web browser that enables your coding agent, such as Claude Code, to visit websites on your behalf and assist you in identifying bugs or creating UI test cases.
AI-powered SVG animation generator that transforms static files into animated SVG components using the Allyson platform
Get access to MCP server SVG and MCP server PNG icons in your vibe-coding projects
745+ CSS3 animations and 9,000+ real SVG icons for AI coding agents. 10 MCP tools. Zero-clone setup via npx.
Create, validate, and render diagrams from D2 (Declarative Diagramming) code into SVG and PNG formats.
Extract and download usable website favicons and return direct icon URLs and metadata through an MCP server.
Provides access to the Lucide icon library for use in LLM and agentic applications.
Renders Mermaid diagram syntax to PNG or SVG images with configurable themes and backgrounds.
Quickly retrieve SVGs using the Iconify API, with no external data files required.
A MCP server that exposes SVGR functionality to convert SVG content into React components
Create, edit, and export SVGator animations (SVG, Lottie, GIF, video) from your AI assistant, and keep an editable project you can open in the editor anytime.
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.





