Model Context Protocol server for Flint — compile, validate, and render semantic chart specs across supported backends.
Flint MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Model Context Protocol server for Flint — compile, validate, and render semantic chart specs across supported backends.
See the changelog for complete release notes.
Once Flint is connected, these are the calls the assistant has available:
Agent — ready chart authoring.** The MCP server gives agents Flint tools andDocumentation — The Documentation tool exposed by this serverInstallation goes through your MCP client rather than a global install: point it at flint-chart-mcp on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
This sits in the knowledge and memory group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Flint's toolset — Agent, Documentation — is a fair guide to whether it matches your workflow. It is maintained by GitHub Actions; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Flint's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Agent | ready chart authoring.** The MCP server gives agents Flint tools and |
| Documentation | The Documentation tool exposed by this server. |
{
"mcpServers": {
"flint": {
"command": "npx",
"args": ["-y", "flint-chart-mcp"]
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.