Flint Chart MCP Server

<h1><img src="assets/flint-logo.svg" alt="" width="42" align="absmiddle"> Flint: A Visualization Language for the AI Era</h1>

Project site · 中文主页 · MCP server

<p align="center"> <img src="docs/figs/chartwall.png" alt="A wall of charts produced by Flint across its supported visualization backends." width="100%"> </p>

Flint is a visualization language that lets AI agents reliably create expressive, good-looking and interactive charts from simple, human-editable chart specs. It is available as an MCP server for everyday use with your agent, and as an npm library for building interactive applications.

Flint supports 52 chart types across 5 rendering backends — Vega-Lite, ECharts, Chart.js, Plotly, and native Excel charts — through one unified interface, with 14 themes and 23 interaction presets. To create bespoke visualizations, design custom themes in the Theme Lab and build advanced interactions with the Flint API.

https://github.com/user-attachments/assets/c1cda0fa-3ea7-41af-b3fd-a127bc83d641

<p align="center"> _{🔊 Click the speaker icon for sound} &nbsp; <a href="https://youtu.be/JAJy7ToczMs"><img src="https://img.shields.io/badge/Watch%20on-YouTube-FF0000?logo=youtube&logoColor=white" alt="Watch on YouTube" align="absmiddle"></a> </p>

Updates

• October 19, 2026 — Flint 1.0 introduces Flint Interactive: interaction presets, semantic events, and an interaction API that connects charts to your app. (changelog)
• August 12, 2026 — Flint 0.5.1 extends visual themes to the Plotly backend and adds Vega-Lite Calendar Heatmap.
• August 5, 2026 — Flint 0.5.0 introduces formal visual themes with preset themes, custom ThemeSpec authoring, and preset inheritance. (v0.5.0)
• July 24, 2026 — Flint 0.4.0 adds 38 Plotly chart types and 18 native, editable Excel chart templates. (v0.4.0)

See the changelog for every release.

Get started

In your agent app (MCP server)

Chart right in the conversation with any MCP client, such as GitHub Copilot in VS Code, Claude, Claude Code, Codex, or Cursor.

⚡ Quick start: paste this setup request into your agent and let it configure Flint for the current project. For manual setup, see the MCP server guide.

Help me set up Flint as an MCP server named "flint"!

1. Add it to my client config, using whichever option my client supports:
   - a local (stdio) server: npx -y flint-chart-mcp
   - the hosted server over HTTP: https://flint.data-formulator.ai/mcp
2. Verify the setup by listing the available Flint chart types.
3. Show me a fun first chart: how many moons each planet has, in a Flint theme you like.

Then ask your agent for a chart, for example:

Go to Yahoo Finance, find today's percentage change for the Magnificent Seven
tech stocks, and compare their performance with Flint in Economist style.
Let me hover to read each stock's change.

The agent can open an interactive chart right in the conversation, return a static PNG or SVG, or produce a backend-native spec.

<p align="center"> <img src="docs/figs/flint-mcp-chat.png" alt="An agent chat where the user asks for global temperatures since 1880 in a newspaper style with brushing, and Flint answers with a live, interactive line chart." width="520"> </p>

Build with your coding agent

Are you a developer building agent apps? Use flint-chart, Flint's npm library, to bring charts into your apps, dashboards, and data stories:

npm install flint-chart

The library compiles Flint specs into backend-native chart specs and provides React and vanilla JavaScript APIs for embedding interactive charts.

A Flint spec describes the data, semantic types, and field mappings, with optional theme and interaction settings. In React, pass it to <FlintChart> to embed an interactive chart:

import type { ChartAssemblyInput } from 'flint-chart';
import { FlintChart } from 'flint-chart/react';

const spec: ChartAssemblyInput = {
  data: { values: [
    { Month: '2026-01', Users: 1200 },
    { Month: '2026-02', Users: 1800 },
  ] },
  semantic_types: { Month: 'YearMonth', Users: 'Quantity' },
  chart_spec: {
    chartType: 'Line Chart',
    encodings: { x: 'Month', y: 'Users' },
  },
  theme_spec: 'economist',
  interaction_spec: { interactions: [{ type: 'inspect-index' }] },
};

<FlintChart spec={spec} />

You can copy the following instruction to your coding agent to build a chart with Flint, then adapt it to your data and app:

Read Flint's chart authoring and interaction skills:
https://github.com/microsoft/flint-chart/blob/main/agent-skills/flint-chart-author/SKILL.md
https://github.com/microsoft/flint-chart/blob/main/agent-skills/flint-interaction-author/SKILL.md

Use these skills to add a chart to this app.
Install flint-chart and the renderer dependencies needed for this project.
Plot monthly users by region from our data in Economist style.
Let readers hover to compare regions at each month, and add a region selector
that updates the chart.
Integrate it with the app's existing layout and verify it works.

The agent can also generate backend-native specs or editable Excel charts for reports and documents. See the API reference, interaction API, and live editor for the underlying APIs and examples.

How it works

A Flint spec consists of the data, semantic types, the chart spec, and optional theme and interaction specs. Instead of relying on complex user-side logic to glue them together, the compiler resolves each part against the others and composes a complete backend-native spec.

1. Describe data with semantic types

Fields are described with semantic types such as Rank, YearMonth, Delta, or Temperature, along with their domains and units. The compiler uses them to infer parsing, scales, axes, formatting, and colors — a short Flint spec becomes a complete backend spec.

<p align="center"> <img src="docs/figs/flint-compilation-pipeline.png" alt="A Flint spec with semantic types, theme and interaction compiled into a Vega-Lite spec and rendered as a temperature heatmap." width="100%"> </p>

2. Build charts once, render on any backend

Charts are defined with high-level chart types and encodings. The compiler adapts sizing, spacing, labels, and legends to the data, for example as it gets denser, and the same spec renders across Vega-Lite, ECharts, Chart.js, and Plotly, or as native Excel charts. See the API reference and the gallery.

3. Unify the look with a theme spec

Geometry, typography, and color are reusable formal specs that apply across a whole chart library, independent of the data and chart type. Pick one of 14 preset themes, such as the New York Times, the Economist, Swiss, or McKinsey, or inherit one and override only what belongs to your brand:

theme_spec: { extends: 'economist', id: 'our-brand', ink: { series: { single: '#6b3fa0' } } }

Compare every preset in the theme explorer, design your own in the Theme Lab, and see the theme guide for the full reference.

<p align="center"> <a href="https://microsoft.github.io/flint-chart/#/themes?theme=economist&amp;layout=banner"> <img src="docs/figs/flint-theme-economist.png" alt="Twelve charts rendered with Flint's Economist theme." width="100%"> </a> </p>

4. Add interactions with an interaction spec

Flint provides 23 interaction presets and a programming API for building interactive charts into applications. The compiler resolves user interaction events into semantic information, so your app only answers with high-level chart updates:

import { FlintChart } from 'flint-chart/react';

<FlintChart
  spec={{ ...input, interaction_spec: { interactions: [{ type: 'brush-x' }] } }}
  onChange={({ phase, state }) => {
    if (phase === 'commit') table.filter(state.selected);
  }}
/>

<p align="center"> <a href="https://microsoft.github.io/flint-chart/#/interactions"> <img src="docs/figs/flint-interactive-warming-globe.png" alt="A Flint choropleth spec rendered as a draggable globe of warming by country, with the focused country's warming stripes read out beside it." width="100%"> </a> </p>

Try the presets in the interaction gallery, see bespoke ones in advanced interactions, and read the interaction spec and programming API.

Documentation

• Project site — gallery, live editor, themes, and interactions
• API reference and backend references for Vega-Lite, ECharts, Chart.js, Plotly, and Excel
• Theme guide, interaction spec, and interaction programming API
• MCP server guide and agent skills
• Paper on arXiv

A Python port is in preview as source in packages/flint-py; its package is not yet released.

Contributing

Contributions are welcome — especially new chart templates and rendering backends. See CONTRIBUTING and the development guide.

git clone https://github.com/microsoft/flint-chart
cd flint-chart
npm install         # workspaces: packages/flint-js, packages/flint-mcp, site

npm run typecheck   # typecheck flint-chart and flint-chart-mcp
npm run test        # Vitest for both packages
npm run build       # build both packages
npm run site        # project site, gallery, and editor at http://localhost:5274/

Node 18+ is required. The site aliases flint-chart to packages/flint-js/src, so library edits hot-reload without rebuilding.

<details> <summary>Repository layout</summary>

flint-chart/
├── packages/
│   ├── flint-js/       npm package `flint-chart` (TypeScript)
│   │   └── src/
│   │       ├── core/         semantics, themes, layout, decisions, shared types
│   │       ├── chart-types/  shared chart definitions and template metadata
│   │       ├── interactive/  interaction presets and runtime
│   │       ├── react/        the `<FlintChart>` React component
│   │       ├── vegalite/     Vega-Lite backend
│   │       ├── echarts/      ECharts backend
│   │       ├── chartjs/      Chart.js backend
│   │       ├── plotly/       Plotly backend
│   │       ├── excel/        native Excel backend
│   │       └── test-data/    fixtures and stress-test generators
│   ├── flint-mcp/      MCP server `flint-chart-mcp`, MCP App UI, and tests
│   └── flint-py/       Python port preview
├── site/               Vite + React project site, gallery, editor, and docs
├── agent-skills/       chart, theme, and interaction authoring skills for agents
├── docs/               user, API, backend, and architecture documentation
└── design-docs/        design proposals and implementation research

</details>

This project has adopted the Microsoft Open Source Code of Conduct. See SECURITY.md to report vulnerabilities.

Community

<table> <tr> <td align="center" width="50%"> <strong>Join the Flint Discord</strong><br> Ask questions, share your charts, and follow releases with Flint users everywhere.<br><br> <a href="https://discord.gg/hnm4Y8YX8">Join Discord</a> </td> <td align="center" width="50%"> <strong>Join the Flint WeChat group</strong><br> Scan the QR code to join the Flint user WeChat group.<br><br> <img src="docs/figs/QR-code.png" alt="Flint WeChat user group QR code" width="160"> </td> </tr> </table>

Contributors

<p align="center"> <a href="https://github.com/Chenglong-MS" title="Chenglong-MS"><img src="https://github.com/Chenglong-MS.png?size=80" width="40" height="40" alt="Chenglong-MS"></a> <a href="https://github.com/xavier-shaw" title="xavier-shaw"><img src="https://github.com/xavier-shaw.png?size=80" width="40" height="40" alt="xavier-shaw"></a> <a href="https://github.com/IAMkecheng" title="IAMkecheng"><img src="https://github.com/IAMkecheng.png?size=80" width="40" height="40" alt="IAMkecheng"></a> <a href="https://github.com/zl190" title="zl190"><img src="https://github.com/zl190.png?size=80" width="40" height="40" alt="zl190"></a> <a href="https://github.com/lx9days" title="lx9days"><img src="https://github.com/lx9days.png?size=80" width="40" height="40" alt="lx9days"></a> <a href="https://github.com/spboyer" title="spboyer"><img src="https://github.com/spboyer.png?size=80" width="40" height="40" alt="spboyer"></a> <a href="https://github.com/taoche" title="taoche"><img src="https://github.com/taoche.png?size=80" width="40" height="40" alt="taoche"></a> <a href="https://github.com/zhb-y-agent" title="zhb-y-agent"><img src="https://github.com/zhb-y-agent.png?size=80" width="40" height="40" alt="zhb-y-agent"></a> <a href="https://github.com/zhnd" title="zhnd"><img src="https://github.com/zhnd.png?size=80" width="40" height="40" alt="zhnd"></a> <a href="https://github.com/yelper" title="yelper"><img src="https://github.com/yelper.png?size=80" width="40" height="40" alt="yelper"></a> <a href="https://github.com/chen1plus" title="chen1plus"><img src="https://github.com/chen1plus.png?size=80" width="40" height="40" alt="chen1plus"></a> <a href="https://github.com/FGRibreau" title="FGRibreau"><img src="https://github.com/FGRibreau.png?size=80" width="40" height="40" alt="FGRibreau"></a> <a href="https://github.com/Hughhhhcoder" title="Hughhhhcoder"><img src="https://github.com/Hughhhhcoder.png?size=80" width="40" height="40" alt="Hughhhhcoder"></a> <a href="https://github.com/joshpoll" title="joshpoll"><img src="https://github.com/joshpoll.png?size=80" width="40" height="40" alt="joshpoll"></a> <a href="https://github.com/nyxst4ck" title="nyxst4ck"><img src="https://github.com/nyxst4ck.png?size=80" width="40" height="40" alt="nyxst4ck"></a> <a href="https://github.com/fix2015" title="fix2015"><img src="https://github.com/fix2015.png?size=80" width="40" height="40" alt="fix2015"></a> </p> <p align="center"> <strong>We'd love to have <em>you</em> join us!</strong> Pick up an <a href="https://github.com/microsoft/flint-chart/issues">issue</a>, add a chart template or a theme, or share what you build in the community. See <a href="#contributing">Contributing</a> to get started, and everyone on the <a href="https://github.com/microsoft/flint-chart/graphs/contributors">contributors graph</a>. </p>

Trademarks

This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos is subject to those third parties' policies.

License

MIT © Microsoft Corporation