Output Charts

● Active

com.outputcharts/mcp

Dashboards from JSON with a stable public link; sign up, build and keep fresh, all as tools.

Connect this server

One click to install, or copy the config below. Suits: Cursor · HTTP clients.

Add to Cursor Add to VS CodeClaude Desktop / Claude Code: paste the config below.

Or add it manually — claude_desktop_config.json (Claude Desktop) or .cursor/mcp.json (Cursor):

{
  "mcpServers": {
    "mcp": {
      "url": "https://api.outputcharts.com/mcp"
    }
  }
}
One line, from the terminal
Claude Code
claude mcp add --transport http mcp https://api.outputcharts.com/mcp
VS Code
code --add-mcp '{"name":"mcp","type":"http","url":"https://api.outputcharts.com/mcp"}'

Syntax from each client's docs (Claude Code: claude mcp add; Codex: codex mcp add; VS Code: code --add-mcp). Placeholders in angle brackets are values you fill in. Codex takes hosted servers in config.toml ([mcp_servers.<name>] url = …) rather than on the command line.

A starting point — check the repository for exact arguments and setup. Restart your client after editing the config.

Category
Data & Analytics
Version
1.0.0
Registry
active
Published
11/18/2026
Listed in:Official MCP registry ↗how this is checked

Is it safe? Is it maintained?

Serverdex check: Nov 22, 2026

Looks healthy: Output Charts is maintained, open source, hosted endpoint answering without a key.

Maintained
Active
Last commit 3 days ago (Nov 19, 2026), 0 open issues.
Official registry
Active
Published as com.outputcharts/mcp in the official MCP registry, version 1.0.0.
Source
Open source, MIT
Public repository under the MIT licence, 0 stars, 0 forks.
Runs
Hosted by the publisher
Your client talks to api.outputcharts.com: prompts and tool arguments leave your machine for that host.
Credentials
None needed to connect
The hosted endpoint completed the Serverdex initialize + tools/list handshake with no key (checked Nov 22, 2026); individual tools may still ask for one.
Owner
Unclaimed
Nobody has claimed this page yet; the data above comes from the registry, GitHub and the live check.

Facts only: last commit and licence from GitHub, the entry's status from the official registry, credentials from the live check. Not a code audit — run the security scan on the endpoint yourself and see the status history.

Live check

checked Nov 22, 2026, 10:07 UTCStatus history & uptime →
● Working290 msprotocol 2025-06-18v1tools

The endpoint answered the MCP handshake as "output-charts" and listed 22 tools. Answering since Nov 19, 2026.

Context cost ≈ 10k tokens of tool definitions a client loads per conversation (estimate: characters ÷ 4) across 22 tools.

Tools (22)

  • signup3 params

    Create an account for a person's email and a Manage key for this agent; the person claims the account from the claim link. 5 per IP and 300 in all a day. Creates an account for the person's email, with a seven-day Solo trial and a Manage key for this agent, and emails them a claim link. The trial is once per person: a mailbox that had one (plus tags and Gmail dots count as the same mailbox), or a second sign-up from one network within 30 days, gets the account on Free with no trial, and the response says so in fix. 409 email_taken when the address already has an account: its owner makes a key under Account → API keys instead. Limited to 5 sign-ups per IP and 300 in all a day (429 rate_limited).

    Show parameters
    • emailstringrequiredThe person's address. The account is theirs; the claim email goes there.
    • agentNamestringThe agent or product making the account, such as Claude Code. Names the key and is mentioned in the claim email.
    • useCasestringWhat the person wants a dashboard for, in a sentence.
  • The key, its owner's tier and dashboard allowance, and the limits. Needs an API key: with none yet, call signup first.

  • Create a narrower key: push only, or bound to one dashboard. Shown once. A Push key bound to one dashboard is the right key for a CI job or a cron that only sends data. Solo owners hold at most five live keys. Needs an API key: with none yet, call signup first.

    Show parameters
    • namestringShown on the keys page.
    • scopestringpush: send data and read visuals. manage: everything this key can do.
    • dashboardIdstringBind the key to one of the owner's dashboards: it then reaches only that dashboard's visuals.
  • get_checkout_link2 params

    A Stripe Checkout link that puts this account on Solo; give it to the account's owner. Works after the trial has ended, when every other call answers requires_solo. Works on Free and after the trial has ended: this is the call to make after a 403 requires_solo. The link is a hosted Stripe page for the account's owner to complete; calls work again as soon as they pay. Needs an API key: with none yet, call signup first.

    Show parameters
    • intervalstringWhich Solo price the session is for.
    • promotionCodestringA Stripe promotion code to apply, such as a launch code the person was given; without one the Checkout page offers its own code field.
  • list_dashboards1 param

    The owner's dashboards, oldest first; ref narrows to the one with that ref. Needs an API key: with none yet, call signup first.

    Show parameters
    • refstringA slug you choose, 1 to 64 of a-z, 0-9 and -. Unique per owner for dashboards and per dashboard for visuals, and set once. Create with a ref so a later run find
  • create_dashboard8 params

    Create a dashboard; with a ref already in use, return that dashboard with created false. One call can make a live page: send visuals and publish true, and the answer carries the dashboard's url. A ref already used by one of the owner's dashboards returns that dashboard, unchanged, with created false; its visuals are then created or found by their own refs, so a run cut short is finished by the next one. Needs an API key: with none yet, call signup first.

    Show parameters
    • titlestringrequiredNot blank.
    • descriptionstring
    • schemestring
    • refstringA slug you choose, 1 to 64 of a-z, 0-9 and -. Unique per owner for dashboards and per dashboard for visuals, and set once. Create with a ref so a later run find
    • visualsarrayCreated in order, each as POST /v1/dashboards/{id}/visuals would, so give every visual a ref when the dashboard has one.
    • publishbooleanMake the page public for anyone with the link, as POST /v1/dashboards/{id}/publish would.
    • shareWitharrayPeople who may view the dashboard after signing in with these addresses, each made as POST /v1/dashboards/{id}/shares would and emailed the link: view-only, and
    • dryRunbooleanCheck everything and write nothing; answers 200 { dryRun: true } or the error the real call would give.
  • get_dashboard1 param

    A dashboard with its visual count and its visuals in reading order. Needs an API key: with none yet, call signup first.

    Show parameters
    • dashboardIdstringrequiredThe dashboard's id.
  • update_dashboard7 params

    Change title, description or scheme; set a ref once on a dashboard that has none. Send only the fields to change. A ref can be set once, on a dashboard that has none. Needs an API key: with none yet, call signup first.

    Show parameters
    • dashboardIdstringrequiredThe dashboard's id.
    • titlestring
    • descriptionstring
    • schemestring
    • refstringA slug you choose, 1 to 64 of a-z, 0-9 and -. Unique per owner for dashboards and per dashboard for visuals, and set once. Create with a ref so a later run find
    • indexablebooleanFalse takes the public page out of search engines, the gallery and the sitemap and mints a claim token (claimToken on the dashboard) for the person it was built
    • isShowcasebooleanTrue lists a published dashboard in the gallery, where search engines may index it (409 not_public on a dashboard that is not published); false takes it out, le
  • reorder_visuals2 params

    Put every visual of the dashboard in a new reading order and reflow. Needs an API key: with none yet, call signup first.

    Show parameters
    • dashboardIdstringrequiredThe dashboard's id.
    • visualIdsarrayrequiredEvery visual of the dashboard exactly once, in the new reading order.
  • publish_dashboard1 param

    Make the dashboard public for anyone with the link, under the same rules and caps as the app; listing it in the gallery is isShowcase on PATCH. Needs an API key: with none yet, call signup first.

    Show parameters
    • dashboardIdstringrequiredThe dashboard's id.
  • unpublish_dashboard1 param

    Make the dashboard private again. Needs an API key: with none yet, call signup first.

    Show parameters
    • dashboardIdstringrequiredThe dashboard's id.
  • share_dashboard2 params

    Give one person view access after they sign in with this address, and email them the link; an address that already has a share comes back with created false. View-only. A person with an account sees the dashboard at once; anyone else has the share attached the moment they sign up or sign in with that address. The same address again returns the existing share with created false and sends nothing. The dashboard need not be public: this is how named people see a private one. Needs an API key: with none yet, call signup first.

    Show parameters
    • dashboardIdstringrequiredThe dashboard's id.
    • emailstringrequiredThe person who may view the dashboard after signing in with this address. They get an email with the link.
  • list_shares1 param

    The dashboard's shares, oldest first, each with its status. Needs an API key: with none yet, call signup first.

    Show parameters
    • dashboardIdstringrequiredThe dashboard's id.
  • revoke_share2 params

    Revoke one share: the person loses access at once. Needs an API key: with none yet, call signup first.

    Show parameters
    • dashboardIdstringrequiredThe dashboard's id.
    • shareIdstringrequiredThe share's id.
  • create_visual7 params

    Create a visual with its document, size and position; with a ref already in this dashboard, return that visual with created false. A ref already used in this dashboard returns that visual, unchanged, with created false. Needs an API key: with none yet, call signup first.

    Show parameters
    • dashboardIdstringrequiredThe dashboard's id.
    • typestringrequired
    • titlestring
    • documentobjectrequiredThe visual's whole JSON document, valid for its type. Rules and an example per type: - bar: orientation is vertical. mode is grouped or stacked. Each data row i
    • sizeobjectDefaults to the type's default size. Width and height within the type's limits, which describe_visual_types lists per type with the widths the editor offers.
    • positionintegerIndex in reading order; absent or past the end puts the visual last.
    • refstringA slug you choose, 1 to 64 of a-z, 0-9 and -. Unique per owner for dashboards and per dashboard for visuals, and set once. Create with a ref so a later run find
  • batch_update2 params

    Replace the documents of several visuals at once, keyed by each visual's ref. Needs an API key: with none yet, call signup first.

    Show parameters
    • dashboardIdstringrequiredThe dashboard's id.
    • dataobjectrequiredThe new documents, keyed by the ref of the visual each one replaces, so one call keeps a whole dashboard fresh. Each is read as PUT /v1/visuals/{id}/data reads
  • get_visual1 param

    One visual with its type, title, ref, size, position and document. Needs an API key: with none yet, call signup first.

    Show parameters
    • visualIdstringrequiredThe visual's id.
  • update_visual5 params

    Change title, document or size; set a ref once on a visual that has none. The type cannot change. Send only the fields to change. The type cannot change; a ref can be set once, on a visual that has none. Needs an API key: with none yet, call signup first.

    Show parameters
    • visualIdstringrequiredThe visual's id.
    • titlestring
    • documentobjectThe visual's whole JSON document, valid for the visual's type: the rules per type are on create_visual's document and in describe_visual_types; get_visual shows
    • sizeobjectWidth and height within the type's limits, which describe_visual_types lists per type with the widths the editor offers.
    • refstringA slug you choose, 1 to 64 of a-z, 0-9 and -. Unique per owner for dashboards and per dashboard for visuals, and set once. Create with a ref so a later run find
  • delete_visual1 param

    Delete the visual, its pointer and its ref, then reflow the rest. Needs an API key: with none yet, call signup first.

    Show parameters
    • visualIdstringrequiredThe visual's id.
  • push_visual_data2 params

    Replace the visual's document; the body is the document itself, valid for the visual's type. Needs an API key: with none yet, call signup first.

    Show parameters
    • visualIdstringrequiredThe visual's id.
    • documentobjectrequiredThe visual's whole JSON document, valid for its type. Rules and an example per type: - bar: orientation is vertical. mode is grouped or stacked. Each data row i
  • append_rows3 params

    Add rows to the end of the visual's data and drop the oldest past keepLast; the visual's settings are unchanged. Adds rows to a line, area, bar, bar-horizontal, scatter, table or map visual; its settings (xKey, series, columns) are unchanged, and numeric strings are coerced as on push. On a map the rows merge by region: a row whose code matches an existing one replaces it, the others are added, and keepLast is ignored. A kpi, gauge, pie, funnel or markdown visual has no row list: replace its document with PUT /v1/visuals/{id}/data instead. Over HTTP keepLast may also go in the query string (?keepLast=7), and the body may be text/csv: the header row is the keys the visual's rows have. Needs an API key: with none yet, call signup first.

    Show parameters
    • visualIdstringrequiredThe visual's id.
    • rowsarrayrequiredAdded after the rows the visual holds, in order.
    • keepLastintegerKeep only the newest keepLast rows after the append, dropping the oldest. The type's cap applies in any case: line 500, area 500, bar 500, bar-horizontal 500, s
  • describe_visual_types

    The visual types, each with its document rules, an example document and its size limits; the widths, schemes and limits.

Checked by Serverdex with a plain initialize + tools/list call to api.outputcharts.com/mcp, no credentials, about once a day. A failed check is never a removal.

On GitHub

read Nov 19, 2026
Stars
0
Forks
0
Last push
Nov 19, 2026
License
MIT

Shellai-agentschartchartsclaude-codecursordashboarddata-visualizationmcpmcp-serverskillskill-mdskills

From the README

Output Charts skill for AI agents Output Charts turns JSON into a dashboard with a stable public link. This repository holds the skill file that teaches an agent the whole flow: open an account for the person it works for, build a published dashboard in one HTTP call, hand back the link, and keep the page fresh with pushes from a script, a cron job or its own next run. SKILL.md is a copy of the file the site serves at outputcharts.com/skill/SKILL.md. The site's copy is the one that moves first; ./check-skill.sh says whether this one still matches it. What the skill does Given a person who wants "a dashboard of these numbers", an agent that has read SKILL.md can: 1. Sign the person up with POST /v1/signup (no key needed): one call with their email address answers a Manage key, an MCP URL and a claim link. The account starts on a seven-day Solo trial, no card. 2. Build a live dashboard in one call: POST /v1/dashboards with the visuals and publish: true answers the public URL. Re-running the same body never makes duplicates. 3. Keep it fresh: replace one visual, append rows to a chart or a table (JSON or CSV), or update several visuals at once by ref. 4. Make a narrower key for CI or a cron, so the Manage key never lands in a repository secret. 5.…

Read the full README on GitHub →

Remotes

  • streamable-httphttps://api.outputcharts.com/mcp

The most-starred Data & Analytics servers in the index, with their live-check result.

ServerStarsLast pushLive check
PostHog41,013Nov 2026Needs sign-in
PostHog MCP Server40,870Nov 2026Needs sign-in
Agent-Native Analytics7,735Nov 2026Needs sign-in
TradingMCP5,320Nov 2026Needs sign-in
Jitsu5,138Nov 2026Needs sign-in

Output Charts: questions people ask

Is Output Charts a remote or a local MCP server?
According to its entry in the official MCP registry, Output Charts ships as a hosted endpoint (streamable-http) that your client connects to by URL.
Does Output Charts need an API key?
Its hosted endpoint completed the Serverdex live check — an MCP initialize + tools/list call — with no credentials on Nov 22, 2026. Individual tools may still ask for a key when called.
Is Output Charts safe to use?
Looks healthy: Output Charts is maintained, open source, hosted endpoint answering without a key. In detail — maintained: Active; official registry: Active; source: Open source, MIT; runs: Hosted by the publisher; credentials: None needed to connect. Serverdex check of Nov 22, 2026. This is a reading of the repository, the registry entry and the live check, not a code audit; run the Serverdex security scan on the endpoint before trusting it with real data.
Is Output Charts still maintained?
Active: the repository's last commit 3 days ago. Last push Nov 19, 2026, 0 GitHub stars, MIT licence. Read from GitHub on Nov 19, 2026.
What tools does Output Charts expose?
22 tools as listed by the server itself during the live check, including signup, whoami, create_api_key, get_checkout_link, list_dashboards. The full list with parameters is in the Live check section above.
How do I add Output Charts to Claude, Cursor or VS Code?
Copy the config in "Connect this server" into your client's MCP config file (claude_desktop_config.json, ~/.cursor/mcp.json or .vscode/mcp.json), or use the one-click Add to Cursor / Add to VS Code buttons and the one-line commands for Claude Code and Codex; then restart the client.
Browse all Data & Analytics →

Add the badge to your site

Show visitors that Output Charts is listed here — it’s also the link we check for a free listing.

Output Charts — listed on Serverdex

HTML — for your website

<a href="https://serverdex.io/server/com-outputcharts-mcp?utm_source=badge"><img src="https://serverdex.io/brand/badge.svg" alt="Output Charts — listed on Serverdex" width="123" height="40" loading="lazy"></a>

Recommended. A dofollow link from your own domain is the one that counts for search engines, and it's the link we check for a free listing.

Markdown — for your README

[![Output Charts — listed on Serverdex](https://serverdex.io/brand/badge.svg)](https://serverdex.io/server/com-outputcharts-mcp?utm_source=badge)

Nice for visibility, but GitHub marks README links nofollow, so it doesn't pass authority. Use the HTML badge on your site as well.

Add to CursorAdd to VS CodeOpen in Claude Code

Install buttons — for your README

[![Add to Cursor](https://serverdex.io/brand/install-cursor.svg)](https://serverdex.io/install/cursor/com-outputcharts-mcp) [![Add to VS Code](https://serverdex.io/brand/install-vscode.svg)](https://serverdex.io/install/vscode/com-outputcharts-mcp) [![Open in Claude Code](https://serverdex.io/brand/install-claude-code.svg)](https://serverdex.io/install/claude-code/com-outputcharts-mcp)

One click opens Cursor or VS Code with this server's config prefilled; the Claude Code button lands on the one-line command. The links point at Serverdex, so when your config changes the buttons keep working.

Install buttons — HTML for your docs

<a href="https://serverdex.io/install/cursor/com-outputcharts-mcp"><img src="https://serverdex.io/brand/install-cursor.svg" alt="Add to Cursor — via Serverdex" width="140" height="28"></a>
<a href="https://serverdex.io/install/vscode/com-outputcharts-mcp"><img src="https://serverdex.io/brand/install-vscode.svg" alt="Add to VS Code — via Serverdex" width="147" height="28"></a>
<a href="https://serverdex.io/install/claude-code/com-outputcharts-mcp"><img src="https://serverdex.io/brand/install-claude-code.svg" alt="Open in Claude Code — via Serverdex" width="180" height="28"></a>

Same buttons as plain links for a docs page or website.

Prefer a live badge with the score, stars and live check? Score badge (links to a page that explains the number and back to this listing).