AntV MCP Server Chart can generate visual outputs from provided data, so review charts before using them in reports, dashboards, or customer-facing material., Geographic visualization tools may depend on external map services and have regional limitations described by the upstream project., Disable unsupported or unwanted chart tools with `DISABLED_TOOLS` when an MCP client has compatibility issues or a workflow should expose fewer visualization actions., Use private rendering infrastructure through `VIS_REQUEST_SERVER` when sensitive datasets should not be sent to the default chart generation service.
Privacy notes
Chart data, labels, prompts, generated images, service identifiers, and rendering requests may contain business metrics, personal data, locations, or customer information., Default chart rendering can involve AntV-hosted services; review data sensitivity before sending private datasets., Protect custom rendering endpoints, service identifiers, and any generated record links in client configs, logs, screenshots, and shared prompts.
Author
AntV
Submitted by
oktofeesh1
Claim status
unclaimed
Last verified
2026-06-05
Decision playbook
Review trust signals before you adopt
Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.
Compare context
Selected
0
Current score
63
Baseline
—
Delta
No baseline selected
No major trust-signal divergence detected in the current selection.
Source and provenance checks
Needs review
Confirm ownership and provenance before trusting install instructions.
Source link availableRequired
Open the canonical repository and verify ownership.
Done
Source provenance statusRequired
Marked as source-backed.
Done
Metadata reviewed
No reviewed flag detected in metadata.
Pending
Safety and privacy checks
Complete
Validate risk disclosures before installation or API wiring.
Safety notes presentRequired
Review the listed safety guidance before running commands.
Done
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
Done
Trust level risk gateRequired
Trust level does not block evaluation.
Done
Package and install checks
Needs review
Check package metadata and artifact integrity signals.
Install payload available
Install or copy payload is available for review.
Done
Package verification flag
No package verification flag provided.
Pending
Checksum metadata
No checksum provided for downloaded artifact.
Pending
Compare-driven decision checks
Needs review
Use compare context to validate trade-offs before adoption.
Compare tray has multiple entries
Add at least one more entry to compare trust differences.
4 safety and 3 privacy notes across 2 risk areas. Review closely: network access.
2 areas
SafetyGeneralAntV MCP Server Chart can generate visual outputs from provided data, so review charts before using them in reports, dashboards, or customer-facing material.
SafetyGeneralGeographic visualization tools may depend on external map services and have regional limitations described by the upstream project.
SafetyGeneralDisable unsupported or unwanted chart tools with `DISABLED_TOOLS` when an MCP client has compatibility issues or a workflow should expose fewer visualization actions.
SafetyNetwork accessUse private rendering infrastructure through `VIS_REQUEST_SERVER` when sensitive datasets should not be sent to the default chart generation service.
PrivacyNetwork accessChart data, labels, prompts, generated images, service identifiers, and rendering requests may contain business metrics, personal data, locations, or customer information.
PrivacyGeneralDefault chart rendering can involve AntV-hosted services; review data sensitivity before sending private datasets.
PrivacyNetwork accessProtect custom rendering endpoints, service identifiers, and any generated record links in client configs, logs, screenshots, and shared prompts.
Safety notes
AntV MCP Server Chart can generate visual outputs from provided data, so review charts before using them in reports, dashboards, or customer-facing material.
Geographic visualization tools may depend on external map services and have regional limitations described by the upstream project.
Disable unsupported or unwanted chart tools with `DISABLED_TOOLS` when an MCP client has compatibility issues or a workflow should expose fewer visualization actions.
Use private rendering infrastructure through `VIS_REQUEST_SERVER` when sensitive datasets should not be sent to the default chart generation service.
Privacy notes
Chart data, labels, prompts, generated images, service identifiers, and rendering requests may contain business metrics, personal data, locations, or customer information.
Default chart rendering can involve AntV-hosted services; review data sensitivity before sending private datasets.
Protect custom rendering endpoints, service identifiers, and any generated record links in client configs, logs, screenshots, and shared prompts.
Prerequisites
Node.js and npm available to the MCP client runtime.
Structured data or a clear visualization request.
Optional private chart rendering service if default remote rendering is not appropriate for the data.
Optional tool filtering plan for chart types that should not be exposed to a given agent workflow.
AntV MCP Server Chart gives MCP clients chart and diagram generation tools
powered by AntV. It supports common statistical charts, flow diagrams, mind
maps, organization charts, network graphs, geographic maps, word clouds,
spreadsheets, and pivot-style tabular views.
The upstream README describes stdio usage through the @antv/mcp-server-chart
npm package, plus SSE and Streamable HTTP transports for remote deployments. It
also documents tool filtering, optional record generation, and private rendering
through a custom visualization request server.
These sources were reviewed on 2026-06-05. Prefer the live repository and
registry metadata for current chart tools, package version, transport options,
environment variables, and private deployment guidance.
Features
Stdio MCP server through the @antv/mcp-server-chart npm package.
SSE and Streamable HTTP transport options for deployed MCP endpoints.
Area, bar, boxplot, column, dual-axis, funnel, histogram, line, liquid, pie,
radar, sankey, scatter, treemap, venn, violin, and word-cloud charts.
Flowchart, fishbone, mind-map, network, and organization diagrams.
District, path, and pin map generation with the upstream regional limitation.
Spreadsheet and pivot-table style output.
Tool filtering through DISABLED_TOOLS.
Optional private rendering service through VIS_REQUEST_SERVER.
For remote deployments, run the server with SSE or Streamable HTTP transport and
configure the MCP client with your deployed HTTPS endpoint. Keep the endpoint
behind the same access controls you would use for any service that receives
private chart data.
Use Cases
Turn tabular data into a quick line, bar, pie, scatter, or radar chart.
Generate flowcharts, mind maps, fishbone diagrams, or organization charts from
structured prompts.
Create visual drafts for reports, notebooks, and dashboards.
Use tool filtering to expose only approved chart types to a given agent.
Route sensitive chart rendering to a private visualization service.
Safety and Privacy
Generated charts can make data look more certain than it is. Review chart type,
axis labels, units, aggregation, outliers, and source data before using outputs
in decisions or public materials.
Treat chart inputs and generated visuals as sensitive when they include business
metrics, personal data, customer records, locations, or unreleased plans. Use a
private rendering service when default remote rendering is not appropriate for
the dataset.
Duplicate Check
No antvis/mcp-server-chart entry, @antv/mcp-server-chart package entry, or
matching source URL was found in content/mcp. This is distinct from browser,
database, and research MCP servers because it focuses specifically on chart and
diagram generation.
Show that AntV MCP Server Chart is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/mcp/antv-mcp-server-chart)
How it compares
AntV MCP Server Chart side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
MCP server for controlling Draw.io and diagrams.net diagrams from Claude, including document discovery, page management, layers, shapes, edges, Mermaid import, diagram import/export, and a built-in editor mode.
MCP server and CLI for AI image and video generation with gallery search, prompt enhancement, model listing, local preferences, ComfyUI workflows, MeiGen Cloud, and OpenAI-compatible provider support.
✓AntV MCP Server Chart can generate visual outputs from provided data, so review charts before using them in reports, dashboards, or customer-facing material.
Geographic visualization tools may depend on external map services and have regional limitations described by the upstream project.
Disable unsupported or unwanted chart tools with `DISABLED_TOOLS` when an MCP client has compatibility issues or a workflow should expose fewer visualization actions.
Use private rendering infrastructure through `VIS_REQUEST_SERVER` when sensitive datasets should not be sent to the default chart generation service.
✓Draw.io MCP Server can create, edit, delete, import, export, rename, copy, and reorganize diagram pages, layers, shapes, edges, labels, metadata, and Mermaid-derived content.
Live operations target connected Draw.io browser tabs or the built-in editor; verify the selected document and page before allowing destructive edits.
The server can run local HTTP and WebSocket endpoints, optionally with TLS or auto-generated self-signed certificates; avoid binding it to untrusted network interfaces.
Browser-extension mode links a browser tab to the MCP server, so only connect tabs containing diagrams that the agent is allowed to inspect or modify.
Export tools can write or return XML, SVG, and PNG files with embedded diagram data; review outputs before sharing them externally.
Use trusted package sources, pin versions for repeatable workflows, and review generated diagrams before committing architectural or security documentation.
✓The canvas server has no built-in authentication; keep it bound to localhost unless network access controls are in place.
MCP tools can create, update, duplicate, group, delete, clear, import, export, snapshot, and restore diagram content.
File import and export should stay inside an approved export directory; review `EXCALIDRAW_EXPORT_DIR` before enabling file workflows.
The URL export tool can upload a scene to Excalidraw hosted sharing, so review the scene before sharing.
In-memory canvas state can be lost on restart unless diagrams are exported or snapshots are preserved.
✓MeiGen can submit image and video generation jobs to external providers or a local ComfyUI backend.
Image and video generation may spend credits, use paid APIs, or consume local GPU resources depending on the configured provider.
Local reference images can be compressed and uploaded through the configured upload gateway before being sent to API providers.
Video generation can take minutes, may time out at the MCP client, and should not be retried blindly because jobs or credits may already be in progress.
ComfyUI workflow import and modification can run local workflows; review workflow JSON and custom nodes before use.
Privacy notes
✓Chart data, labels, prompts, generated images, service identifiers, and rendering requests may contain business metrics, personal data, locations, or customer information.
Default chart rendering can involve AntV-hosted services; review data sensitivity before sending private datasets.
Protect custom rendering endpoints, service identifiers, and any generated record links in client configs, logs, screenshots, and shared prompts.
✓Diagrams can include private architecture, network topology, cloud account names, customer systems, credentials embedded in labels, incident details, internal process maps, or product plans.
The MCP client can receive diagram XML, SVG, PNG exports, page names, layer names, selected-cell data, shape metadata, browser tab document metadata, and imported Mermaid content.
Local editor and browser-extension workflows may leave diagrams, exported files, browser state, TLS material, and logs on disk.
Treat exported SVG or PNG files with embedded XML as source files, because they can contain full editable diagram data beyond the visible image.
Clear temporary files, generated certificates, and MCP logs when they are no longer needed for the diagram workflow.
✓Diagrams may reveal infrastructure topology, unreleased product plans, customer names, credentials accidentally included as labels, or incident context.
Screenshots, exported images, Excalidraw JSON files, snapshots, and share URLs may be visible to the MCP client, browser, logs, and model provider.
Avoid exposing the local REST/WebSocket canvas API to shared networks without authentication or a trusted network boundary.
Treat imported diagrams from untrusted sources as prompt-injection and data-exposure risks before asking a model to summarize them.
✓API tokens, OpenAI-compatible credentials, provider base URLs, upload gateway URLs, ComfyUI URLs, preferences, recent generations, prompts, model IDs, and output paths can reveal private creative workflows.
Uploaded reference images may become public URLs through the configured upload gateway before generation.
Prompts, reference images, generated image URLs, generated video URLs, saved outputs, and favorite prompts can contain client work, brand plans, product images, personal likenesses, or unreleased campaigns.
Keep secrets in MCP client environment configuration, review generated media before sharing, and remove local outputs when retention is no longer needed.
Prerequisites
Node.js and npm available to the MCP client runtime.
Structured data or a clear visualization request.
Optional private chart rendering service if default remote rendering is not appropriate for the data.
Optional tool filtering plan for chart types that should not be exposed to a given agent workflow.
Node.js 22 or newer for the published npm package.
An MCP client such as Claude Desktop or Claude Code.
A browser for the built-in editor, or the Draw.io MCP browser extension when controlling an existing diagrams.net tab.
Review of which diagrams, browser tabs, pages, and export locations Claude is allowed to modify.
Node.js 18 or newer and npm for local setup, or Docker for the container path.
A running canvas server, started locally with `PORT=3000 npm run canvas` or through the canvas container image.
The MCP server configured with `EXPRESS_SERVER_URL` pointing to the canvas server.
Browser access to the canvas UI when using screenshot, viewport, or image export workflows.
Node.js 18 or newer.
MCP client that can launch a local Node stdio server.
Optional MeiGen API token, OpenAI-compatible API key, or local ComfyUI workflow configuration for generation tools.
Provider pricing, credits, model limits, and content policy reviewed before image or video generation.
Install
npx -y @antv/mcp-server-chart
npx -y drawio-mcp-server --editor
npm ci && npm run build
Run `npx -y meigen` from an MCP client, or use the upstream plugin/init commands after reviewing provider credentials and generated-media costs.