Generates charts, maps, and tables with live-updating embed links for AI agents.
Also known as oscarleoo/chartlink-agents, chartlink-mcp
- Stars
- 0
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 0.1.2
- Last commit
- Oct 8, 2026
- License
- MIT
What is chartlink MCP?
chartlink generates charts, maps, and tables with live-updating embed links for AI agents.
Summary generated from the project's README
About chartlink MCP server
Generating live-updating charts, maps, and tables through embed links is what this server enables for AI agents. It acts as a stdio bridge for clients that require local server execution, though users with HTTP MCP-compatible clients can connect directly to the remote endpoint using a bearer token. Developers set it up via npx by providing a CHARTLINK_API_KEY in their environment configuration.
The server provides nine default tools that follow a specific workflow: finding a template, reading its contract, performing a dry-run with data, creating the visualization, publishing it, and receiving the final links. While the basic tools are available immediately, accessing the full engine—including every chart type, brand, and data source—requires setting the CHARTLINK_MCP_URL environment variable to the full engine URL. Users can obtain a workspace and API key via a simple curl command without creating a traditional account.
What you can do with it
- 1Create data visualizationsAsk your AI agent to generate a specific chart or map using a template and your provided data.
- 2Verify data before publishingHave the agent perform a dry-run to ensure your data matches the template requirements before finalizing the chart.
- 3Discover visualization templatesInstruct the agent to search for an appropriate template based on your specific data needs.
- 4Obtain live embed linksRequest the final URLs for your published charts to use in other applications.
Written from the project's README. Every use case is checked against a quote from it.
How to install chartlink MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall chartlink MCP in Claude Code
$ claude mcp add --env 'CHARTLINK_API_KEY=<YOUR_CHARTLINK_API_KEY>' chartlink -- npx -y chartlink-mcpInstall chartlink MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"chartlink": {
"command": "npx",
"args": [
"-y",
"chartlink-mcp"
],
"env": {
"CHARTLINK_API_KEY": "<YOUR_CHARTLINK_API_KEY>"
}
}
}
}Install chartlink MCP in VS Code
.vscode/mcp.json
{
"servers": {
"chartlink": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"chartlink-mcp"
],
"env": {
"CHARTLINK_API_KEY": "<YOUR_CHARTLINK_API_KEY>"
}
}
}
}Install chartlink MCP in VS Code CLI
$ code --add-mcp '{"name":"chartlink","type":"stdio","command":"npx","args":["-y","chartlink-mcp"],"env":{"CHARTLINK_API_KEY":"<YOUR_CHARTLINK_API_KEY>"}}'Install chartlink MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"chartlink": {
"command": "npx",
"args": [
"-y",
"chartlink-mcp"
],
"env": {
"CHARTLINK_API_KEY": "<YOUR_CHARTLINK_API_KEY>"
}
}
}
}Install chartlink MCP in Codex
$ codex mcp add chartlink --env 'CHARTLINK_API_KEY=<YOUR_CHARTLINK_API_KEY>' -- npx -y chartlink-mcpInstall chartlink MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.chartlink] command = "npx" args = ["-y", "chartlink-mcp"] [mcp_servers.chartlink.env] CHARTLINK_API_KEY = "<YOUR_CHARTLINK_API_KEY>"
Install chartlink MCP in Gemini CLI
$ gemini mcp add -s user -e 'CHARTLINK_API_KEY=<YOUR_CHARTLINK_API_KEY>' chartlink npx -- -y chartlink-mcpInstall chartlink MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"chartlink": {
"command": "npx",
"args": [
"-y",
"chartlink-mcp"
],
"env": {
"CHARTLINK_API_KEY": "<YOUR_CHARTLINK_API_KEY>"
}
}
}
}Configuration
CHARTLINK_API_KEYSecretchartlink API key (viz_...). POST https://chartlink.app/api/signup returns one, no account needed. Optional for listing tools; required for calling them.
| Name | Description | |
|---|---|---|
| CHARTLINK_API_KEY | chartlink API key (viz_...). POST https://chartlink.app/api/signup returns one, no account needed. Optional for listing tools; required for calling them. | Secret |
Automated checks
Ran Nov 15, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachableoscarleoo/chartlink-agents is public and reachablegithub.com/oscarleoo/chartlink-agents ↗Pass
- Package names this repository as its sourcechartlink-mcp names oscarleoo/chartlink-agents as sourcenpmjs.com/package/chartlink-mcp ↗Pass
- Build provenance (Sigstore attestation)No build attestation published for this releaseNot checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-10-08github.com/oscarleoo/chartlink-agents ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNo popular package one edit away from chartlink-mcpPass
- No critical advisory in the package or its dependencies99 resolved dependencies checked; no critical advisoryosv.dev ↗Pass
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeHTTPS endpoint answered 401 (sign-in required)Pass
README
View on GitHubchartlink-mcp
A stdio bridge to the chartlink MCP server, for clients that only launch local stdio servers. Charts, maps and tables with live-updating embed links: https://chartlink.app
{
"mcpServers": {
"chartlink": {
"command": "npx",
"args": ["-y", "chartlink-mcp"],
"env": { "CHARTLINK_API_KEY": "viz_..." }
}
}
}
No key yet? curl -X POST https://chartlink.app/api/signup returns a workspace and its key — no account. The key is shown once.
Without a key the bridge still starts and lists every tool, so you can look before you sign up; each tool call then answers with the signup step instead of running.
If your client speaks HTTP MCP, skip this package and connect directly: https://chartlink.app/mcp with Authorization: Bearer viz_....
By default the server exposes the template path — nine tools: find a template by need, read its contract, dry-run your data, create from it with your data and a few knobs, publish, hand back the links. The whole engine (every chart type, the full settings schema, brands, data sources) is behind CHARTLINK_MCP_URL=https://chartlink.app/mcp?full=1.
The manual your agent should read first: https://chartlink.app/llms.txt (the templates and the four-step loop); the full engine manual is https://chartlink.app/llms-full.txt.
chartlink MCP questions
How do I add chartlink MCP to Claude Code?
Run claude mcp add --env 'CHARTLINK_API_KEY=<YOUR_CHARTLINK_API_KEY>' chartlink -- npx -y chartlink-mcp in your terminal. Add --scope user to make it available in every project.
How do I add chartlink MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
How do I get an API key?
You can obtain a workspace and key without creating an account by using a curl command to the signup endpoint.
Can I use the server without an API key?
Yes, the bridge will start and list all available tools without a key, though tool calls will prompt you to sign up instead of executing.
How can I access the full engine including all chart types?
You can access the full engine by setting the CHARTLINK_MCP_URL environment variable to the full engine URL.