Skip to main content
Glama
zhaohaijun734-arch

smart-charts-mcp

by zhaohaijun734-arch
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to smart-charts-mcp

No user-submitted related servers found.

    Related Servers

    • Generate-Echarts

      xiaobenyang-com
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP ECharts is a dynamic chart generation and data analysis tool based on Apache ECharts, supporting multiple export formats and MinIO object storage integration.
      2
      Apache 2.0

    • search2chart-mcp

      iqingyoung
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to turn structured tabular data or CSV/XLSX files into interactive charts that render inline in conversations, with client-adaptive output modes and self-contained HTML.
      MIT

    • echart-mcp-view

      SpenserCai
      A
      license
      A
      quality
      D
      maintenance
      An MCP server for rendering common ECharts visualizations from structured tool arguments, exposing per-chart opener tools that map to independent HTML app resources.
      18
      17 npm
      2
      MIT
    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

    A3.9/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool occupies a clearly distinct slot in the workflow: profile_data analyzes data, list_chart_types is a static reference, render_chart produces output, and doctor checks the environment. There is no plausible case where an agent would mistake one for another.

    Naming Consistency4/5

    Three of four tools follow a clean verb_noun pattern (profile_data, list_chart_types, render_chart), with 'doctor' as the single stylistic deviation. That lone noun-style name is still conventional and unambiguous, so the break is minor.

    Tool Count4/5

    Four tools is lean but well-scoped for a charting server, with each earning its place in a profile-then-render pipeline. The heavy lifting is consolidated into one large render_chart tool, so the surface is slightly thin at the discovery/utility end but not problematic.

    Completeness4/5

    The core lifecycle (preflight, inspect data, choose chart, render HTML) is fully covered, and render_chart itself is extremely broad with 30+ chart types and many options. Minor gaps exist: no tool to persist/export the rendered HTML to a file or to list available datasets, but agents can work around these.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources