All servers / Analytics / Flint MCP server
Flint MCP server
Model Context Protocol server for Flint — compile, validate, and render semantic chart specs across supported backends.
Tested by ConnectATDScore 90 out of 100. Tested 2026-11-18 on package version 1.1.1. Package: flint-chart-mcp · source
Score breakdown
| Runs | 18 / 20 | |
|---|---|---|
| Tool descriptions | 20 / 20 | |
| Package safety | 20 / 20 | |
| Maintenance | 20 / 20 | |
| Adoption | 12 / 20 |
What we saw
- Starts and answers the MCP handshake: yes (11.1 seconds including download)
- Tools offered: 9
- Last published: 2026-11-17
- Weekly downloads (npm): 2,840
- License: MIT · Direct dependencies: 11
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions. Under each name you can see how many of its parameters are explained.
render_chart11 of 11 parameters describedCompile a Flint chart spec for a backend and render it to a STATIC image (PNG) or vector (SVG), returned inline. Rendering is local/in-process. The chartjs backend supports PNG only. Prefer show instead when the host supports MCP App UIs; use render_chart for a static artifact or when no App UI is available.
compile_chart8 of 8 parameters describedCompile a Flint chart spec to a backend-native spec object (Vega-Lite / ECharts / Chart.js) without rendering. Returns the spec JSON, assembly warnings, and the computed layout size.
validate_chart9 of 9 parameters describedValidate a Flint chart spec for a backend without rendering. Every backend returns the validation result as JSON (also in structuredContent). For vegalite, a second block follows: the report of what to act on (errors, warnings, interaction_spec entries the chart drops, and update ops that will not apply, ✗), the same report show returns; "Nothing to fix" when it is clean. For a host with no card UI; with a card, call show directly, which runs the same check. Nothing is kept between calls.
list_chart_types2 of 2 parameters describedThe chart types, each with its channels and a one-line note on what it is for, for a backend (or all). Pass `chartType` for one type in full: its guidance (map keys, which bar chart), its chartProperties with values, defaults and effects, and the interaction presets it supports in interaction_spec (Vega-Lite).
list_interaction_presets2 of 2 parameters describedList the interaction presets for interaction_spec: what the reader does, what each needs from the chart, its reset gestures, and every option it accepts under `options`. Pass `chartType` for the presets a Vega-Lite chart type supports, or `type` for one preset. Which presets answer a request and how they combine is in get_flint_skill with skill "interaction", section "Add interactions".
get_flint_skill2 of 2 parameters describedReturn a bundled Flint skill as markdown. Read it once before you write the matching spec: `chart` for a ChartAssemblyInput, `theme` for a ThemeSpec, `interaction` for an interaction_spec or ChartUpdate layers (updates), `board` for a board spec, `app` for code that uses flint-chart in an application. Pass `section` with a heading to get only that part; an unknown section lists the headings. The same text is served as the flint://agent-skill, flint://theme-skill, flint://interaction-skill, flint://board-skill and flint://app-skill resources.
list_themes0 of 1 parameter describedList Flint visual theme presets for `theme_spec` (for example, `theme_spec: "economist"`). Pass an `id` for preset-specific authoring guidance. To customize a preset, use an object with `extends` and a small set of overrides.
validate_board9 of 9 parameters describedCheck a board of several Flint charts without drawing it, for a host with no card UI or a static image; with a card, call show directly, which runs the same check. The report gives the layout in one line, what to fix before it draws, and what it would draw with. Before the first board, call get_flint_skill with skill "board".
show2 of 2 parameters describedPut a chart or a board on screen: pass the full spec as chart or as board; there is no need to validate first. show checks the spec: one with errors, or with something it must not be drawn with (rows drawn as slices, a link that joins nothing), draws nothing and returns what to fix, so call show again with the fixed spec. Otherwise the card draws it live with an editing panel, and the result notes what it drew with; change nothing for those unless the user asks. Nothing is kept: to change what is on screen, change the spec and call show again; a new card shows it and earlier cards stay as they were.
Tested in a sandbox with an empty environment: no API keys, a throwaway folder, nothing from a real account. A passing test shows the server runs and responds. It is not a security audit.