ChartQuery MCP Server
Related Servers
Alternatives to ChartQuery MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables agents to manage templates and images, create and update image drafts, and render them to PNG, ZIP, or PDF exports via MCP.4 npmMIT
- AlicenseBqualityDmaintenanceEnables AI clients to generate over 26 chart types via MCP, automatically starting a private rendering service.271MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to render charts as SVG or PNG, validate chart specifications, and retrieve descriptions, schemas, types, and examples through seven tools over stdio or HTTP.104 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables clients to list supported chart methods and render chart images from data and configuration supplied with each call, with optional themes and resource limits.MIT
- AlicenseNot gradedqualityCmaintenanceEnables LLM clients to create hand-drawn study-notes style graphics, including charts, concept maps, mind maps, timelines, sketch notes, and 2×2 matrices, as PNG images via MCP.1MIT
- AlicenseAqualityBmaintenanceEnables MCP clients to inspect, convert, resize, compress, crop, rotate, watermark, background-remove, and batch-process images with secure path confinement and result verification.14MIT
TDQS
Scored across 19 tools
The tools are grouped by clear output domains (chart, diagram, label, barcode, QR code) and action suffixes such as render/view/compile/validate help distinguish most usage. Some pairs, especially chart_render vs chart_view and label_preview vs label_compile, could still be confused at a glance, but their descriptions clarify the difference.
Most names follow a predictable noun plus action pattern in snake_case, such as chart_render, diagram_view, label_compile, and label_validate. The main deviations are bare noun tools like barcode, chart, usage, qrcode, and stats, which are readable but less consistent than the suffixed variants.
At 19 tools the set is on the heavy side, and the repeated render/view/ai pattern across chart, diagram, and label contributes to bloat. Most tools are purposeful, but the surface is close to the borderline where a smaller unified abstraction would be easier to use.
The server covers generation, AI-assisted creation, saved rendering/viewing, and detailed label printer-command workflows, so core lifecycle needs are addressed. Minor gaps remain around explicitly listing, saving, deleting, or managing saved chart/diagram/label resources.