-MCP calls let agents embed rows directly as `data.values`, or read configured
-local JSON, CSV, or TSV files by `data.url`. For agent workflows without MCP,
+MCP calls let agents embed rows directly as `data.values`, or read local JSON,
+CSV, or TSV files by `data.url`. For agent workflows without MCP,
use the standalone [agent skill](agent-skills/flint-chart-author/SKILL.md).
## Repository overview
diff --git a/agent-skills/flint-chart-author/SKILL.md b/agent-skills/flint-chart-author/SKILL.md
index 1786f23..216d0d4 100644
--- a/agent-skills/flint-chart-author/SKILL.md
+++ b/agent-skills/flint-chart-author/SKILL.md
@@ -104,13 +104,15 @@ Use the binding mode that matches the runtime. Do not mix them.
data is small or already transformed by another tool, pass it as
`data: { values: [...] }`. Do not pass runtime variable names in
MCP tool calls — the MCP server cannot see your local variables.
-2. **Direct MCP rendering: reference a local file only when configured.**
+2. **Direct MCP rendering: reference a local file.**
The `flint-chart-mcp` server can load `data: { url: "..." }` from local
- `.json`, `.csv`, or `.tsv` files, but only under directories that the host
- explicitly allowed with `--data-roots`, `--data-root`, or
- `FLINT_MCP_DATA_ROOTS`. Remote URL fetching is disabled. If the data must be
- transformed first, use a coding/data tool to write a small prepared file
- under an allowed root, then reference that file.
+ `.json`, `.csv`, or `.tsv` files. By default any local file the agent can
+ name is readable (relative paths resolve against the working directory); a
+ hardened deployment may reject local file references entirely via
+ `--disable-file-reference` (or `FLINT_MCP_DISABLE_FILE_REFERENCE`), in which
+ case pass rows inline with `data.values`. Remote URL
+ fetching is disabled. If the data must be transformed first, use a
+ coding/data tool to write a small prepared file, then reference that file.
3. **Generated application or notebook code: bind runtime variables.** If the
user asks you to add Flint to code, write normal data-loading code first and
pass a real runtime value, e.g. `data: { values: rows }`, to
@@ -262,7 +264,7 @@ string shorthand, expanded to `{ field: "Use Flint as a MCP server for your agent
+Use Flint as an MCP server for your agent
Install flint-chart-mcp as a{' '}
Model Context Protocol
{' '}
- server and your agent can create charts from the same conversation
- where the question starts. By default it opens an interactive Flint
+ server and your agent can create charts as an interactive MCP app. By default it opens an interactive Flint
chart view; when you need artifacts, it can also return static images
or backend-native specs.
- $ npx -y flint-chart-mcp
-
-
- View on GitHub →
+ + + Quick start: + {' '} + paste this setup request into your agent and let it configure Flint for the current project. For manual setup, + see{' '} + {' '} + or the{' '} + + GitHub README -
The experience
Using Flint through MCP is a simple loop: connect the server, ask - for the chart you want, and work with the rendered result in the - same chat. + for the chart you want, and work with a visualization with dynamic widgets provided by the MCP server.
+ + +- Connect Flint MCP server. Add the stdio server to your - MCP client. If the agent should chart local CSV, TSV, or JSON - files, grant a data root explicitly. + MCP client. The agent can chart local CSV, TSV, or JSON + files by default.
- Ask for a chart. The agent turns your request @@ -66,17 +83,6 @@ export function McpServer() {
- The embedded chart is genuinely Flint-rendered, using the same path
- as the MCP App. The frame and toolbar mirror the real{' '}
- create_chart_view UI: a live
- preview with chart options and a Copy spec to chat action.
-
What it provides
@@ -133,32 +139,29 @@ export function McpServer() { {/* ---- Install ---------------------------------------------- */}Install & configure
+Install & configure
- The server speaks stdio and runs zero-install with{' '}
- npx. If your MCP client can
- edit its own configuration, you can ask your agent to set it up:
+ For manual setup, the server speaks stdio and runs zero-install with{' '}
+ npx. Point your MCP client at the package:
Or point your MCP client at the package manually:
-
Tool calls can embed rows directly with{' '}
- data.values. If you want the
- agent to chart a local CSV, TSV, or JSON file instead, grant an
- explicit data root. Remote URLs are never fetched:
+ data.values. The agent can
+ also chart a local CSV, TSV, or JSON file by{' '}
+ data.url out of the box.
+ Remote URLs are never fetched. For an untrusted deployment, pass{' '}
+ --disable-file-reference to
+ reject local file references and accept only inline{' '}
+ data.values:
{children}
+ {copyable ? (
+
+ ) : null}
+ {children}