Developer Tools

szum.io

Provides chart rendering, validation, theming, and example generation from JSON configs.

1 endpoint13 known toolsFirst detected May 10, 2026Last detected August 29, 2026

ENDPOINT 1

https://szum.io/mcp

No auth detected

MCP server metadata

Name: Szum
Version: 1.4.0

Capabilities

tools.listChangedresources.listChanged

Server instructions

Chart authoring: - x/y/text/label.field and non-# fill/stroke must name data keys. Pie: x for category, y for value (finite numbers); fill normally matches x. Literals are #RGB/#RRGGBB. Paint: fill for area/pie/text; stroke for rule; either (not both) for line; either/both for dot/bar. Defaults need x/y keys. - Share top-level data; use mark data for different rows. - Fill/stroke fields create series; group only arranges existing bar series as stack (default) or dodge. If rows share a position, encode a series or aggregate. Areas stack. - Prefer built-in labels; reserve text for free-positioned annotations. Hide a fully labeled value axis only when readers do not need its scale. - Bar and area value axes stay linear and include zero. Explicit base-10 log scales require positive finite values and domains; use line or dot. - For chronological annual trends, use "YYYY" strings, map x: "year", and set x to { type: "utc", tickFormat: "%Y" }. Do not invent dates. Categorical years may stay band; UTC numbers are Unix milliseconds. - Let themes style unless asked. Use color literals intentionally; themeOverrides require Creator or Pro. - Use barX for long category names, line/area for ordered trends, dot for relationships, pie sparingly for part-to-whole, and ruleX/ruleY for references. - Include version and format in raw JSON. Prefer the smallest clear config. MCP workflow: - Use get_examples when needed. - 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. Validation is free and fast. - Preview with render_chart; offer once after the finished preview, never automatically or during revisions. - Follow saved-chart tool scopes. Delete explicitly. Hide internals.

Known tools 13

render_chart

Use this when the user wants to preview or generate a chart.

Inferred read-only

save_chart

Use this when the user wants to permanently save and publish a chart from a Szum config.

Potential side effects

list_charts

Use this when the user wants to find charts in their saved library.

Inferred read-only

get_chart

Use this when the user identifies a saved chart by id and wants to view it or retrieve its metadata and URLs.

Inferred read-only

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.

Inferred read-only

get_preview_state

Use this when the Szum chart App needs to restore a rendered preview as its current transient or saved view.

Inferred read-only

update_chart

Use this when the user wants to replace and publish a saved chart's config while keeping its id and URLs.

Potential side effects

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.

Inferred read-only

delete_chart

Use this when the user explicitly wants to permanently delete one saved chart.

Potential side effects

validate_chart

Use this when a chart config will be rendered, saved, or updated.

Inferred read-only

list_themes

Use this when choosing a visual theme for a chart.

Inferred read-only

list_marks

Use this when choosing or configuring chart mark types.

Inferred read-only

get_examples

Use this when the model needs current, ready-to-use Szum chart configs or preferred semantic patterns.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.szum]
url = "https://szum.io/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "szum": {
      "type": "http",
      "url": "https://szum.io/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: szum
Remote MCP URL: https://szum.io/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "szum": {
      "url": "https://szum.io/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "szum": {
      "type": "http",
      "url": "https://szum.io/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "szum",
  "transport": "streamable-http",
  "url": "https://szum.io/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.