Vizro MCP vs Semiotic

A side-by-side look at the Vizro MCP and Semiotic MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Vizro MCP logoVizro MCPData VisualizationTools and templates to create validated and maintainable data charts and dashboards.45FairAuth: no auth requiredSemiotic logoSemioticData Visualization · Local subprocess (stdio)React data visualization MCP server with 30+ chart types. 5 tools: suggest charts for a dataset, render validated React configs to SVG, diagnose configuration anti-patterns, get component schemas, and report issues.71GreatAuth: no auth required

Verdict: choose Vizro MCP for data visualization work; choose Semiotic for data visualization as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Vizro MCP logoChoose Vizro MCP when

  • You need dedicated capabilities in the Data Visualization domain.
  • Its auth model fits you: No auth required.
Explore Vizro MCP

Semiotic logoChoose Semiotic when

  • You need dedicated capabilities in the Data Visualization domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
  • You want tools like renderChart, renderInteractiveChart, getSchema.
Explore Semiotic

Feature & specification comparison

Rows where the two servers differ are marked.

SpecVizro MCP logoVizro MCPSemiotic logoSemiotic
CategoryData VisualizationData Visualization
Quality signal45/100 · Fair71/100 · Great
Install commandNot confirmed yetConfirmed
Transport—Local subprocess (stdio)
AuthNo auth requiredNo auth required
PricingFreeFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars3,8102,716
Directory activity 6 views 0 installs 0 upvotes 6 views 0 installs 0 upvotes
ToolsNot listed18

Tools & capabilities

Vizro MCP tools

No tool names declared yet. Check the project README from the listing page.

Semiotic tools 18

  • renderChartRender a Semiotic chart to static SVG. Supports the components returned by `getSchema` that are marked `[renderable]`. Pass `{ component: "LineChart", props: { data: [...], xAccessor: "x", yAccessor: "y" } }`. Returns SVG string plus a "Render evidence" JSON block (mark counts by scene type, resolv…
  • renderInteractiveChartRender a static-data chart as a ChatGPT Apps widget. Uses the same Semiotic server render path as `renderChart`, then hydrates an iframe UI with fit, zoom, data, hover, and render-evidence controls.
  • getSchemaReturn the prop schema for a specific component. Pass `{ component: "LineChart" }` to get its props, or omit `component` to list the complete schema-backed catalog. Components marked `[renderable]` are available through `renderChart`; realtime charts require a browser/live environment.
  • suggestChartSample-row recommender. Pass `{ data: [{...}, ...] }` with 1–5 sample objects plus optional broad intent/capability filters.
  • suggestChartsCapability-based recommender for bounded row data. Returns ranked chart suggestions with scores, reasons, caveats, import paths, and ready-to-use props.
  • suggestStreamChartsRecommend streaming charts from a schema (shape, key, throughput). Returns `{ suggestions, excluded, stretchSuggestions }`.
  • suggestStreamDashboardCompose a multi-panel dashboard from stream schemas and an audience layout policy.
  • suggestDashboardBuild a multi-panel dashboard suggestion that covers distinct analytical intents.
  • suggestStretchChartsRecommend audience-literacy stretch picks from an `AudienceProfile`.
  • repairChartConfigCheck whether a requested chart fits a dataset and return ranked alternatives when it does not.
  • interrogateChartReturn a statistical summary and chart-aware context for answering natural-language questions with optional annotations.
  • diagnoseConfigCheck a chart configuration for common problems — empty data, bad dimensions, missing accessors, wrong data shape, and more. Returns a human-readable diagnostic report with actionable fixes.
  • +6 more on the listing page

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Vizro MCP

No confirmed install command for Vizro MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.

Semiotic

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "nteract-semiotic": {
      "command": "npx",
      "args": [
        "-y",
        "-p",
        "semiotic",
        "semiotic-mcp"
      ]
    }
  }
}

Frequently asked questions

Vizro MCP is categorized under Data Visualization and uses an install path we have not confirmed yet. Semiotic belongs to Data Visualization and uses a local stdio subprocess. Pick Vizro MCP for data visualization work and Semiotic for data visualization.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Vizro MCP has no confirmed install command yet — follow its own setup instructions.

Vizro MCP is listed as free. Auth: no auth required. Semiotic is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add mckinsey-vizro-mcp and nteract-semiotic as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Vizro MCP has a quality signal of 45/100 (Fair) with 6 views, 0 installs and 3,810 GitHub stars. Semiotic has 71/100 (Great) with 6 views, 0 installs and 2,716 GitHub stars.