@bicharts/chart-mcp 0.6.55 → 0.6.56

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@bicharts/chart-mcp",
-  "version": "0.6.55",
-  "description": "MCP (Model Context Protocol) stdio server for BIC AI charts: profile a dataset locally, then generate chart code that has passed the BIC backend's render gates. Works with any MCP-capable client (Claude Code, Claude Desktop, Cursor, Copilot Studio). Requires a BIC trial or paid account.",
+  "version": "0.6.56",
+  "description": "MCP (Model Context Protocol) stdio server for BIC AI charts: profile a dataset locally, then generate chart code that has passed the BIC backend's render gates. Works with any MCP-capable client (Claude Code, Claude Desktop, Cursor, Copilot Studio). An account pays to author charts; the code it writes is yours and runs with no licence.",
   "keywords": [
     "mcp",
     "modelcontextprotocol",
@@ -43,8 +43,8 @@
   },
   "// dependencies": "NONE, deliberately. dist/ bundles every module the server uses, so a runtime dependency installs nothing it needs - it only makes npx fetch that package (and its tree) before the first start. Everything the bundle carries is a devDependency; scripts/verify-package.mjs fails the release if a dependency appears or a shipped file imports anything but Node's built-ins.",
   "devDependencies": {
-    "@bicharts/chart-host": "^0.6.52",
-    "@bicharts/shape-core": "^0.6.52",
+    "@bicharts/chart-host": "^0.6.56",
+    "@bicharts/shape-core": "^0.6.56",
     "@modelcontextprotocol/sdk": "^1.0.0",
     "@types/node": "^20.0.0",
     "@types/papaparse": "^5.3.14",

package/skills/bic-charts/SKILL.md

@@ -769,7 +769,9 @@ render inside them.
 **9. Check every chart, then deploy.** Check every chart locally with this server's `check_chart` tool,
 at the size the panel will give it - by default it reads the chart's `minChartWidth` and `minChartHeight`
 off its `BicChartPanel`, so pass no size unless you mean another one. A `WARNING` line in its reply is a
-label likely cut off at that size: deal with it before you call the chart done.
+label cut off at that size: deal with it before you call the chart done. The reply says whether more room fixes it.
+Never edit the generated chart code by hand: if something's wrong with a generated chart, regenerate it
+(`generate_chart` with a prompt describing the fix) or report it.
 You don't need to deploy to check a chart. Then `npx tsc -b` and the tests. Deploying (`npx rayfin up`), on Rayfin 1.36.1:
 - Signed in? `npx rayfin login status` (a subcommand, not a `--status` flag); `npx rayfin login` if not.
 - Name the workspace: `npx rayfin up -w "<workspace>"`. Left out, it deploys to My Workspace.
@@ -779,6 +781,8 @@ You don't need to deploy to check a chart. Then `npx tsc -b` and the tests. Depl
 - Deleted the app outside Rayfin? `rayfin/.deployments.json` still names the deleted item, so the next
   `rayfin up` fails with 404 Not Found. Move that file aside and deploy again.
 
+What it costs: only the calls that author a chart (generate_chart, and the eligibility lists beyond a free hourly allowance) draw on the account. The chart code they write is the user's to keep and ship: it needs no licence, account, credits or connection to us to run, view or deploy, for any number of viewers.
+
 ## 4. Things that will otherwise cost you time
 
 - **Place names, not coordinates.** If your data has city/state/ZIP but no lat/lon, pass a