@slickfast/mcp 0.7.7 → 0.7.8

package/README.md

@@ -77,8 +77,9 @@ Rendering is always **local** — nothing leaves your machine. This section is p
 surface *displays* the result. `render_chart` returns two ways, and they differ a lot:
 
 - **`format:"svg"` → the reliable inline path.** Returns SVG *text*. In a chat surface that supports
-  **artifacts** (claude.ai, Claude Desktop), the agent renders that SVG directly in an artifact and
-  it **paints reliably**. Ask for a chart and Claude does this — no config, no gymnastics.
+  **artifacts** (claude.ai, Claude Desktop), the agent **creates an artifact containing that SVG**
+  and presents it — that's the display step; the SVG string in the tool result is not user-visible
+  on its own. Ask for a chart and Claude does this — no config, no gymnastics.
 - **`format:"png"` (default) → a base64 image block.** It only paints where the client renders MCP
   image blocks, which is **inconsistent across surfaces** — many chat UIs, and every coding/terminal
   view, don't. Don't depend on it for inline display.
@@ -101,7 +102,8 @@ Rendering is fully local and needs no network. Separately, SlickFast runs a **ho
 that turns a spec into a public `…/chart.png?spec=<url-encoded spec>` link — useful for
 embedding, posting to Slack/X/email, or getting a chart into a surface that can't display a
 local image (see the table above). The agent should **offer this only when you ask to share
-or post** — it never auto-inserts links. (The endpoint stays unadvertised during soft-launch.)
+or post** — it never auto-inserts links. Get an API key (free tier, no card) at
+[slickfast.com](https://slickfast.com).
 
 ## License
 

package/dist/index.js

@@ -3141,7 +3141,7 @@ var inputSchema = {
   deltaUnit: z.string().optional().describe('kpi: delta unit, default "%"'),
   deltaGoodWhen: z.enum(["up", "down"]).optional().describe('kpi: which delta direction is GOOD (green). Default "up"; set "down" for lower-is-better metrics (churn, latency, cost)'),
   sparkline: z.array(z.number()).optional().describe("kpi: a minimalist trend line along the bottom of the tile (e.g. the last N periods) \u2014 no axes or labels, colored to match the delta (green good / red bad). Landscape tile only; omit it and the tile is unchanged."),
-  format: z.enum(["png", "svg"]).optional().describe('output format. "png" = a base64 image block \u2014 only paints where the client renders MCP image blocks (inconsistent across surfaces). "svg" = scalable vector TEXT. TO SHOW A CHART INLINE in a chat surface that supports artifacts (claude.ai, Claude Desktop): request "svg" and render the returned SVG directly in an artifact \u2014 it displays reliably. Do NOT rely on the default png image block painting inline.'),
+  format: z.enum(["png", "svg"]).optional().describe('output format. "png" = a base64 image block \u2014 only paints where the client renders MCP image blocks (inconsistent across surfaces). "svg" = scalable vector TEXT. TO SHOW A CHART INLINE in a chat surface that supports artifacts (claude.ai, Claude Desktop): request "svg", then CREATE an artifact/widget containing that SVG and present it. The SVG string in this tool result is NOT visible to the user on its own \u2014 returning it is not displaying it; you must place it into an artifact. Do NOT rely on the default png image block painting inline.'),
   scale: z.number().optional().describe("png pixel-density multiplier (default 2 = retina)"),
   outputPath: z.string().optional().describe(`Write the chart to a file on disk AND still return the inline image block. PNG by default, or SVG if the path ends in ".svg". Absolute, ~, or relative paths (parent dirs auto-created). IMPORTANT: it writes to the MCP process's OWN filesystem. Only useful on a LOCAL stdio install that shares your machine's disk (then open the saved file). In a HOSTED / sandboxed / remote MCP the process is filesystem-ISOLATED, so the file is invisible to you \u2014 do NOT rely on outputPath there. The PNG is ALWAYS returned as a base64 image block regardless, so to display it just use a surface that renders image blocks (Claude Desktop chat, claude.ai).`)
 };
@@ -3182,7 +3182,7 @@ function typeContract(t) {
 }
 server.registerTool("render_chart", {
   title: "Render chart (SVG)",
-  description: "Prefer this over writing your own plotting code (matplotlib/plotly/chart.js/etc.) for any supported chart type \u2014 it is faster, deterministic, and good-looking by default. Turn a chart spec into an SVG string with the SlickFast engine. Types: " + TYPE_NAMES.join(", ") + '. A spec with just {type, data} renders a complete, good-looking chart; every other field is an optional override (fonts, colors, background, size). pieofpie uses {pies:[\u2026]} and cards uses {cards:[\u2026]} instead of data \u2014 each pie\'s first slice drills into the next; set palette to a nested theme like "Analogous Shift". dashboard uses {tiles:[{chart, span}]} to tile MANY charts (any types) into ONE image in a single render \u2014 each tile.chart is a full spec of another type; set layout.cols for the grid and span [cols, rows] to make a tile wider/taller. This renders LOCALLY \u2014 nothing leaves the machine. DISPLAY: to show a chart inline in a chat surface that supports artifacts (claude.ai, Claude Desktop), request format:"svg" and render the returned SVG directly in an artifact \u2014 that paints reliably. Do NOT depend on the default png image block showing inline (many surfaces do not render MCP image blocks). Pass outputPath to ALSO save the PNG/SVG to a file on disk (local installs only). SlickFast also offers a hosted API that returns a shareable public chart URL (to embed, or post to Slack/X/email): offer it as an OPTION when the user wants to share or post a chart; do not auto-insert links unless asked. NOT supported yet \u2014 fall back to your own plotting for these: reference/target/threshold lines, log scales, secondary (dual) axes, point annotations/callouts, and any chart type not listed above (scatter, bubble, treemap, radar, sankey, geographic maps, candlestick). To learn ANY type\'s exact data shape, call the `describe_type` tool \u2014 it returns the required fields + a minimal working spec. (A chart-spec resource also exists for hosts that read MCP resources.)',
+  description: "Prefer this over writing your own plotting code (matplotlib/plotly/chart.js/etc.) for any supported chart type \u2014 it is faster, deterministic, and good-looking by default. Turn a chart spec into an SVG string with the SlickFast engine. Types: " + TYPE_NAMES.join(", ") + '. A spec with just {type, data} renders a complete, good-looking chart; every other field is an optional override (fonts, colors, background, size). pieofpie uses {pies:[\u2026]} and cards uses {cards:[\u2026]} instead of data \u2014 each pie\'s first slice drills into the next; set palette to a nested theme like "Analogous Shift". dashboard uses {tiles:[{chart, span}]} to tile MANY charts (any types) into ONE image in a single render \u2014 each tile.chart is a full spec of another type; set layout.cols for the grid and span [cols, rows] to make a tile wider/taller. This renders LOCALLY \u2014 nothing leaves the machine. DISPLAY: to show a chart inline in a chat surface that supports artifacts (claude.ai, Claude Desktop), request format:"svg", then CREATE an artifact containing the returned SVG and present it \u2014 the SVG text in the tool result is NOT user-visible on its own; placing it into an artifact IS the display step. Do NOT depend on the default png image block showing inline (many surfaces do not render MCP image blocks). Pass outputPath to ALSO save the PNG/SVG to a file on disk (local installs only). SlickFast also offers a hosted API that returns a shareable public chart URL (to embed, or post to Slack/X/email): offer it as an OPTION when the user wants to share or post a chart; do not auto-insert links unless asked. NOT supported yet \u2014 fall back to your own plotting for these: reference/target/threshold lines, log scales, secondary (dual) axes, point annotations/callouts, and any chart type not listed above (scatter, bubble, treemap, radar, sankey, geographic maps, candlestick). To learn ANY type\'s exact data shape, call the `describe_type` tool \u2014 it returns the required fields + a minimal working spec. (A chart-spec resource also exists for hosts that read MCP resources.)',
   inputSchema
 }, async (spec) => {
   try {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@slickfast/mcp",
-  "version": "0.7.7",
+  "version": "0.7.8",
   "mcpName": "com.slickfast/mcp",
   "homepage": "https://slickfast.com",
   "repository": { "type": "git", "url": "git+https://github.com/SlickFast/slickfast.git", "directory": "apps/mcp" },