vegalite-viewer
Related Servers
Alternatives to vegalite-viewer
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityFmaintenanceA Model Context Protocol (MCP) server implementation that provides the LLM an interface for visualizing data using Vega-Lite syntax.100-
- AlicenseAqualityDmaintenanceA MCP server for data visualization. It exposes tools to render charts (line, bar, pie, scatter, heatmap, etc.) from data and returns plots as either image/text/mermaid diagram.24MIT
- FlicenseAqualityDmaintenanceAn MCP server that allows AI models to create data visualizations using Vega-Lite syntax by providing tools to save data tables and generate visualizations from them.23-
- AlicenseNot gradedqualityBmaintenanceMCP server that turns coding agents into data analysts: attach CSV/Parquet/JSON/XLSX or databases, profile data, run read-only SQL, and render Vega-Lite charts as SVG files.1MIT
- FlicenseAqualityBmaintenanceData-visualization MCP server for ROOT Workspace. It enables creating and iterating on charts (Vega-Lite, Python plots) with a persistent kernel and vision loop.8-
- AlicenseNot gradedqualityDmaintenanceMCP server that renders interactive Chart.js charts (bar, line, pie, doughnut, etc.) inline in Claude's UI.1MIT
TDQS
Scored across 2 tools
Each tool has a clearly distinct purpose: upload_data registers datasets, while visualize_data renders them. The descriptions explicitly define when to use each, leaving no ambiguity.
Both tools follow the same verb_noun pattern (upload_data, visualize_data), which is consistent and predictable.
At 2 tools, the server is slightly under the typical 3-15 range, but the tools form a complete two-step workflow for the narrow purpose of Vega-Lite visualization, so the count is reasonable.
The upload-then-visualize flow covers the core workflow, but there are no management operations (e.g., listing or deleting datasets), which are minor gaps that agents can work around by re-uploading with a new name.