Skip to main content
Glama
ganapativs

microcharts

by ganapativs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Related Servers

Alternatives to microcharts

  • ECharts MCP

    apache
    A
    license
    Not graded
    quality
    B
    maintenance
    An MCP (Model Context Protocol) server that enables LLMs to generate ECharts visualizations by accepting chart type, data and parameters and returning cloud image URLs of the generated charts.
    5 npm
    82
    Apache 2.0

Related Servers

  • Flint MCP Server

    bbigger004
    F
    license
    Not graded
    quality
    B
    maintenance
    Enables agents to compile a semantic chart description (data, semantic types, chart intent) into native specs for five charting libraries and headlessly render three of them to SVG or PNG, delivered inline or as signed, expiring artifact URLs. It also exposes tools for validating charts, listing chart types and themes, plus resources and prompts that supply chart-authoring and theming conventions.
    -

  • Charta MCP

    mortenator
    A
    license
    Not graded
    quality
    Not graded
    maintenance
    Enables AI agents to generate beautiful, presentation-ready charts (SVG + PNG) with zero setup, supporting various chart types and styling options.
    25 npm
    MIT

  • provchart-mcp

    Figsh
    A
    license
    A
    quality
    B
    maintenance
    Generates pure CSS and SVG charts for web pages and markdown docs, eliminating the need for chart libraries, and provides injection guidance.
    3
    10 npm
    1
    MIT

  • mcp-dashboards

    KyuRish
    A
    license
    A
    quality
    A
    maintenance
    Renders 45+ interactive chart types, dashboards, and KPI widgets directly inside AI conversations. Supports drill-down, live API polling, 20 themes, and one-click export to PNG, PowerPoint, and A4 documents.
    40
    359 npm
    47
    Functional Source , Version 1.1, MIT Future
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.6/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a clearly distinct role: find discovers chart types, get retrieves implementation details, and render produces the final SVG. There is no meaningful overlap between querying, inspecting, and rendering.

Naming Consistency5/5

All tool names follow the same verb_noun pattern: find_microchart, get_microchart, render_microchart. The naming is predictable and makes the workflow easy to infer.

Tool Count5/5

Three tools is well-scoped for the server's purpose: discover a chart, understand its wiring, and render it. Each tool is necessary and the set is tight without unnecessary duplication.

Completeness5/5

The tools form a complete workflow: find_microchart returns candidates to identify the right chart, get_microchart provides the data shape and sample needed to render, and render_microchart produces the final SVG output. There are no dead ends or obvious missing operations.

Maintenance

ActivityActive
ResponsivenessSlow

Resources