Data Visualization MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is Data Visualization MCP Server?

The Data Visualization MCP Server is a Model Context Protocol (MCP) server implementation that provides an interface for visualizing data using Vega-Lite syntax, enabling users to create rich visual representations of their data.

how to use Data Visualization MCP Server?

To use the server, integrate it with your application by adding it to your configuration file. You can save data tables and visualize them using Vega-Lite specifications through the provided tools.

key features of Data Visualization MCP Server?

  • Save data tables for later visualization.
  • Visualize data using Vega-Lite syntax.
  • Supports output in both text and PNG formats.

use cases of Data Visualization MCP Server?

  1. Creating interactive data visualizations for reports.
  2. Analyzing and visualizing large datasets efficiently.
  3. Integrating with applications that require dynamic data representation.

FAQ from Data Visualization MCP Server?

  • What is Vega-Lite?

Vega-Lite is a high-level grammar for visual analysis that enables users to create visualizations easily.

  • Can I save multiple data tables?

Yes! You can save multiple tables and visualize them as needed.

  • What output formats are supported?

The server supports both text and PNG output formats for visualizations.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago