Slickfast MCP logo

Slickfast MCP

Render deterministic charts, dashboards, scientific plots, and HTML pages locally or publish them through SlickFast.

Install Slickfast MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "mcp-139": {
      "command": "npx",
      "args": [
        "-y",
        "@slickfast/mcp"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— the server itself is confirmed live (we called its tools/list endpoint). The stdio install command is a separate, ongoing check.

Overview

Slickfast MCP connects AI agents to the SlickFast rendering engine for deterministic charts, tiled dashboards, scientific plots, and complete HTML Pages. Its MCP tools accept JSON specifications and return SVG, PNG, HTML, palette data, type schemas, or hosted URLs, with local rendering keeping chart data on the machine. Reach for it when an agent needs repeatable visual output without generating plotting code, or when a chart, report, or dashboard must be shared publicly. Scientific types include scatter, error bars, survival, Bland–Altman, Q–Q, and volcano plots with logarithmic axes and related statistics.

Use cases

  • Render repeatable charts from agent-generated JSON
  • Build tiled dashboards from multiple chart specifications
  • Generate scientific plots with logarithmic axes and analysis statistics
  • Publish shareable charts or report-style HTML Pages

Key features

  • Supports 47 gallery chart types and scientific plots
  • Renders dashboards with configurable tile layouts
  • Produces deterministic SVG, PNG, and HTML output
  • Provides chart schemas, minimal examples, palettes, and galleries
  • Publishes charts and Pages through API-key-backed hosted workflows

Tools15

What Slickfast MCP lets your agent do. Expand a tool for its parameters.

Verified live~10.7k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

21/23 checks healthy over the last 92d

What it can do

From the 15 tools this server returned when we ran it; 15 declare their own safety hints.

Can delete or modify data · 1Handles credentials · 4Makes network requests · 10Read-only tools · 14
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceNot published
Package age115 days
Maintainers1

Observed 2026-10-17 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 8d ago via OSV.dev · @slickfast/mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars1Stargazers on the source repository.
npm downloads1kPackage downloads in the last 30 days.
Last commitTodayMost recent push to the default branch.
Tools exposed15Callable tools this server registers over MCP.
Directory activity8 viewsConfig copies, upvotes, and views on AllMCPs.

How Slickfast MCP works

What Slickfast MCP does

Slickfast MCP turns structured JSON specifications into visual output through the SlickFast engine. It supports 47 gallery chart types, including bars, lines, areas, pies, funnels, gauges, tables, timelines, and dashboards. A dashboard can combine many chart specifications into one tiled image, with configurable grid columns and tile spans.

The server also exposes scientific chart types through the same engine: scatter, errorbar, lineplot, barplot, survival, Bland–Altman, Q–Q, and volcano. These support features such as logarithmic axes and plot-specific calculations including Kaplan–Meier curves, Bland–Altman analysis, Q–Q plots, and volcano-chart negative log10 p-values.

For document-style output, Pages combine a hero, prose, charts, grids, statistics, and a footer into one HTML page. Local rendering produces self-contained output without contacting a remote service. Public charts and Pages are separate workflows that send content to the hosted SlickFast API.

How it works

Use describe_type before constructing an unfamiliar chart specification. It returns the chart family, expected top-level data key, and a minimal working example. Calling it without a type lists the supported gallery and scientific types. describe_pagespec serves the same purpose for Pages and returns the page structure, section types, themes, limits, and examples.

render_chart converts a specification into an SVG result and can also save PNG or SVG output to a local file. render_page converts a page specification into HTML and can write it to disk. Both operations are local. For large local specifications, specPath or pagespecPath loads JSON from a file instead of passing the entire object through the host argument pipe.

Palette selection is handled by list_palettes, which returns valid flat palettes and nested themes along with a swatch-board image. The server also includes gallery for rendered examples and their reusable specifications, plus read_chart for retrieving the JSON twin of a SlickFast chart URL.

Setup and configuration

Install the MCP package through an MCP client using the @slickfast/mcp package and the command npx -y @slickfast/mcp. The same command can be added to clients such as Claude Desktop, Claude Code, Cursor, and VS Code. Clients that accept remote MCP URLs can connect to https://mcp.slickfast.com/mcp instead.

Leave SLICKFAST_API_KEY unset for local-only rendering. Add a free API key when using share_chart, publish_page, or API-key-backed page history through my_pages. The key is not needed for local charts, local Pages, palettes, type descriptions, galleries, or live onboarding and news tools.

Tools and capabilities

  • Render gallery, scientific, and dashboard specifications with render_chart.
  • Generate complete HTML reports or status pages with render_page.
  • Publish public chart URLs with share_chart and public Pages with publish_page.
  • Inspect specifications using describe_type, describe_pagespec, and read_chart.
  • Browse examples, palettes, onboarding information, news, and MCP installation status.
  • Push a rendered chart to a TRMNL e-ink display with push_to_trmnl.
  • Create a formatted issue report with report_issue when the user explicitly requests feedback submission.

Limitations and notes

Rendering is local by default, but sharing charts, publishing Pages, reading hosted chart URLs, and pushing to TRMNL contact external endpoints. Published Pages are unlisted rather than private: anyone with the URL can open the page and fetch its JSON twin, so secrets should not be included.

The renderer does not currently support secondary axes on gallery types, bubble charts, treemaps, radar charts, Sankey diagrams, geographic maps, candlesticks, boxplots, or histograms. Use another plotting tool for those cases. Chat surfaces that support artifacts may require the returned SVG to be placed in an artifact before it becomes visible inline.

The project is licensed under AGPL-3.0-only. Closed commercial embedding or self-hosting outside the AGPL terms requires a commercial license.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Slickfast MCP

Slickfast MCP is an MCP server that connects AI agents to the SlickFast deterministic rendering engine. Its main tools render 47 chart types, scientific plots, tiled dashboards, and HTML Pages from JSON specifications, while other tools describe schemas, list palettes, show galleries, and publish selected outputs.

Install it with an MCP client configured to run `npx -y @slickfast/mcp`. Add the package as a stdio MCP server, or connect to the hosted endpoint at `https://mcp.slickfast.com/mcp` when the client accepts remote MCP URLs.

Yes, Slickfast MCP works with Cursor. The package includes a Cursor MCP installation link, and Cursor can also connect to the hosted MCP endpoint. Local configuration uses the `npx -y @slickfast/mcp` command.

No, local chart and Page rendering works without an API key. Set `SLICKFAST_API_KEY` when you want to share a chart, publish a Page, or use API-key-backed page history; those workflows contact the hosted SlickFast API.

Create a dashboard specification with a `tiles` array, where each tile contains a complete chart specification and an optional `[columns, rows]` span, then pass it to `render_chart`. Set `layout.cols` to control the grid width.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewSlickfast MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/mcp-139?style=directory)](https://allmcps.com/mcp/mcp-139)
HTML Embed
<a href="https://allmcps.com/mcp/mcp-139"><img src="https://allmcps.com/api/badge/mcp-139?style=directory" alt="Slickfast MCP on AllMCPs" /></a>