@slickfast/mcp 0.7.5 → 0.7.6

package/README.md

@@ -1,30 +1,43 @@
 # SlickFast — charts & dashboards for AI agents
 
-SlickFast turns a small JSON spec into a polished, retina-quality chart — **47 chart and
-information-design types** (bar, line, pie, KPI, cards, funnel, gauge, heatmap, calendar,
-gantt, waterfall…), plus **multiple charts tiled into a single dashboard image in one call**.
-It runs as an [MCP](https://modelcontextprotocol.io) tool, so an AI agent hands it a spec and
-gets back a finished PNG (or SVG). Everything renders **locally** — nothing leaves your machine.
+**A tiny JSON spec in → a finished, retina-quality chart out. Milliseconds, a handful of
+tokens, nothing leaves your machine.**
+
+SlickFast is a **native SVG engine built for AI agents** — not a browser screenshotting a
+webpage, not a plotting library an agent has to write code against. A pure
+`spec → SVG → PNG` pipeline: **47 chart and information-design types** (bar, line, pie, KPI,
+cards, funnel, gauge, heatmap, calendar, gantt, waterfall…), plus **entire multi-chart
+dashboards tiled into one image in a single call**. It runs as an
+[MCP](https://modelcontextprotocol.io) tool, so an agent hands it a spec and gets back a
+finished PNG (or SVG).
 
 ```txt
 render_chart({ type: "bar", data: { labels: ["Q1","Q2","Q3"], series: [{ values: [12,19,8] }] } })
   → a retina PNG, rendered on your machine
 ```
 
-## Why it's built for agents
-
+## Why agents (and the people paying for their tokens) pick SlickFast
+
+- **Tokens are the real cost — a spec is nearly free.** An agent hand-writing SVG or
+  matplotlib code burns hundreds to thousands of output tokens, then often retries when it
+  doesn't render. A SlickFast spec is a few dozen tokens, and `{type, data}` alone is a
+  finished, well-designed chart. A whole dashboard is **one tool call**, not ten renders
+  and layout math.
+- **Changes are one-field edits.** Swap `bar` → `line`, change a palette, resize for a
+  slide: edit one key, re-render. The agent never rewrites code or reasons about a diff —
+  which is what makes iteration with a human ("make it dark, bigger title") actually cheap.
+- **No headless browser.** Most chart-to-image pipelines secretly spawn Puppeteer or
+  Playwright — hundreds of MB, slow cold starts, flaky output. SlickFast renders pure
+  in-memory, milliseconds per chart.
+- **Native SVG, vector-first.** Output is a few KB of crisp-at-any-scale SVG (or retina PNG
+  on demand) — small enough to cache, embed, or ship anywhere.
 - **Deterministic — same spec, same bytes, forever.** No randomness, no timestamps, no
-  headless-browser drift. Outputs are **cacheable, testable, and reproducible**, with zero
-  flaky pixel diffs. Almost no charting tool can promise this — and it's exactly what a
-  tool-calling agent needs.
-- **Never throws garbage at the model.** Empty data, a bad tile, a filtered-to-nothing series →
-  a clean, graceful frame, not a crash or a stack trace. Reliability is a feature when the
-  caller is an agent, not a human who can eyeball the error.
-- **Fails loud on real mistakes.** An unknown palette or enum is *rejected* with a clear error
-  listing the valid options — so the agent fixes it immediately instead of silently shipping the
-  wrong-looking chart.
-- **Good-looking by default.** A spec of just `{type, data}` renders a complete, well-designed
-  chart; fonts, colors, palettes, and size are optional overrides.
+  browser drift. Cacheable, testable, reproducible; zero flaky pixel diffs. Almost no
+  charting tool can promise this — and it's exactly what a tool-calling agent needs.
+- **Never throws garbage at the model.** Empty data, a bad tile, a filtered-to-nothing
+  series → a clean, graceful frame, not a crash or a stack trace. A real mistake (unknown
+  palette, bad enum) → a **loud error listing the valid options**, so the agent
+  self-corrects in one step.
 - **100% local & private.** Rendered and rasterized on your machine. Nothing is sent anywhere.
 
 ## Tools
@@ -41,7 +54,7 @@ render_chart({ type: "bar", data: { labels: ["Q1","Q2","Q3"], series: [{ values:
 - **`list_palettes()`** → every valid `palette` name, grouped into flat palettes and nested
   themes, with their colors. Ask *"what palettes are available?"*.
 - **`report_issue(summary, spec?)`** → *"report this bug."* Formats a bug report and returns a
-  prefilled email link you click to send — SlickFast sends nothing itself.
+  prefilled GitHub-issue link and email link you click to send — SlickFast sends nothing itself.
 
 ## Install
 
@@ -95,11 +108,19 @@ or post** — it never auto-inserts links. (The endpoint stays unadvertised duri
 **AGPL-3.0-only.** Free to use, self-host, and embed under the AGPL's terms (your friends
 running it locally are completely unaffected). Building it into a **closed-source product
 or a hosted service**? That needs the AGPL'd source opened — or a **commercial license**
-from us instead. Reach out for commercial terms.
+from us instead. Write to feedback@slickfast.com for commercial terms.
+
+## Feedback, bugs & feature requests
+
+- **GitHub:** [SlickFast/slickfast](https://github.com/SlickFast/slickfast) — bug reports and
+  feature requests via the [issue templates](https://github.com/SlickFast/slickfast/issues/new/choose).
+- **Email:** feedback@slickfast.com
+- Or ask your agent to *"report this as a SlickFast issue"* — the `report_issue` tool drafts
+  the report (with the repro spec) for you. Nothing is ever sent automatically.
 
 ## Developing locally
 
-Clone the repo, then from the package directory:
+Clone [the repo](https://github.com/SlickFast/slickfast), then from the package directory:
 
 ```bash
 cd apps/mcp

package/dist/index.js

@@ -3292,9 +3292,11 @@ server.registerTool("report_issue", {
     "_Reported via the SlickFast report_issue tool._"
   ].filter(Boolean).join("\n\n");
   const mailto = `mailto:${FEEDBACK_EMAIL}?subject=${encodeURIComponent("SlickFast bug: " + summary)}&body=${encodeURIComponent(body)}`;
-  const text = `Bug report ready \u2014 **nothing has been sent.** To submit, click this link (it opens your mail client):
+  const ghIssue = `https://github.com/SlickFast/slickfast/issues/new?labels=bug&title=${encodeURIComponent("[bug] " + summary)}&body=${encodeURIComponent(body)}`;
+  const text = `Bug report ready \u2014 **nothing has been sent.** To submit, pick either:
 
-${mailto}
+- **GitHub issue** (preferred \u2014 public, trackable): ${ghIssue}
+- **Email** (opens your mail client): ${mailto}
 
 Or copy the report below into an email to ${FEEDBACK_EMAIL}:
 

package/package.json

@@ -1,6 +1,10 @@
 {
   "name": "@slickfast/mcp",
-  "version": "0.7.5",
+  "version": "0.7.6",
+  "mcpName": "com.slickfast/mcp",
+  "homepage": "https://slickfast.com",
+  "repository": { "type": "git", "url": "git+https://github.com/SlickFast/slickfast.git", "directory": "apps/mcp" },
+  "bugs": { "url": "https://github.com/SlickFast/slickfast/issues", "email": "feedback@slickfast.com" },
   "description": "SlickFast — render 47 chart & info-design types (bar, line, pie, KPI, cards, funnel, matrix, gauge, calendar…) plus multi-chart dashboards tiled into one image, as SVG/PNG via MCP. Local and deterministic; nothing leaves your machine.",
   "keywords": ["mcp", "model-context-protocol", "chart", "charts", "dashboard", "data-visualization", "svg", "png", "ai", "agent", "claude", "llm", "deterministic"],
   "license": "AGPL-3.0-only",