chartlink

io.github.oscarleooPublished by GitHub account oscarleoov0.1.2Updated Oct 24, 2026

Charts and tables for AI agents with live-updating embed links. No account: signup returns a key.

VerifiedStreamable HTTPWeb executableData & AnalyticsMedia & Design

Overview

AI-generated overview

Lets an assistant build charts, maps and tables from data and publish them as live-updating embed links, via a remote endpoint or a local npm bridge.

What you can do
  • Find a chart, map or table template that fits a stated need and read its contract
  • Dry-run supplied data against a template before creating anything
  • Create a visualization from a template with your data and a few settings, then publish it
  • Hand back embed links that update live as the underlying data changes
  • Optionally expose the full engine (all chart types, settings schema, brands, data sources) through a full-mode endpoint
When to use it
Useful when an assistant needs to turn data into a shareable chart, map or table and keep it updating, rather than just describing numbers in text. Also handy for clients that only launch local stdio servers and cannot connect to a remote HTTP MCP endpoint directly.
Requirements
A chartlink API key (viz_...) supplied as CHARTLINK_API_KEY for the npm bridge or as an Authorization Bearer header for the remote endpoint; a key can be obtained from the signup endpoint without an account. The npm package runs under Node.js via npx; the remote endpoint needs network access. Without a key the bridge still starts and lists tools, but calls return the signup step.
Before you install
The API key is a secret and is shown only once at signup, so store it carefully. Publishing creates publicly reachable embed links that update live, so check what data ends up in them. The full-engine mode exposes more settings and data-source options than the default template path.

Installation

In SourceWeft

  1. Open chartlink in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.oscarleoo%2Fchartlink/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "chartlink": {
      "type": "http",
      "url": "https://chartlink.app/mcp"
    }
  }
}

README

chartlink-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

json
{  "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.

Source: packages/chartlink-mcp/README.md at commit cff9e95

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.1.2LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts