@bicharts/chart-mcp 0.6.65 → 0.6.67
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/check-chart.mjs +11 -11
- package/dist/index.mjs +79 -79
- package/package.json +3 -3
- package/skills/bic-charts/SKILL.md +9 -1
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@bicharts/chart-mcp",
|
|
3
|
-
"version": "0.6.
|
|
3
|
+
"version": "0.6.67",
|
|
4
4
|
"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.",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"mcp",
|
|
@@ -43,8 +43,8 @@
|
|
|
43
43
|
},
|
|
44
44
|
"// 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.",
|
|
45
45
|
"devDependencies": {
|
|
46
|
-
"@bicharts/chart-host": "^0.6.
|
|
47
|
-
"@bicharts/shape-core": "^0.6.
|
|
46
|
+
"@bicharts/chart-host": "^0.6.66",
|
|
47
|
+
"@bicharts/shape-core": "^0.6.66",
|
|
48
48
|
"@modelcontextprotocol/sdk": "^1.0.0",
|
|
49
49
|
"@types/node": "^20.0.0",
|
|
50
50
|
"@types/papaparse": "^5.3.14",
|
|
@@ -170,7 +170,8 @@ Asking for these in `prompt` prose instead is the most expensive mistake availab
|
|
|
170
170
|
routinely costs two or three extra generations, and each one is minutes of wall-clock.
|
|
171
171
|
|
|
172
172
|
Other parameters worth knowing: `chart_type` (a preference, honored unless the data shape
|
|
173
|
-
disqualifies it), `renderer
|
|
173
|
+
disqualifies it), `renderer` (a JavaScript or TypeScript project gets D3 without asking, because D3 is what
|
|
174
|
+
`@bicharts/chart-host` draws), `width`/`height`, and
|
|
174
175
|
`reasoning_mode: "1P"` when you want the cheapest, fastest pass.
|
|
175
176
|
|
|
176
177
|
**Generation takes minutes.** Fire the calls for independent charts **in parallel** rather
|
|
@@ -447,6 +448,13 @@ Add `@using MyCharts.Components` to `_Imports.razor`, then on a page:
|
|
|
447
448
|
`integrationContract` says what each does. The common ones: `palette` (a categorical colour
|
|
448
449
|
list), `colorScaleLow`/`colorScaleHigh` (a sequential ramp's ends, what a choropleth reads),
|
|
449
450
|
`maxMapPoints` (a point map's cap). An option not in `optionsRead` does nothing on that chart.
|
|
451
|
+
- **Hover drop lines** - a 3D scatter can draw, on hover, a line from a point to each back wall of
|
|
452
|
+
its cube, so the point's three values read off the gridlines. It is off unless someone wants it:
|
|
453
|
+
name it in the request ("with drop lines") and it starts on; otherwise ASK THE USER ONCE whether
|
|
454
|
+
they want it, then pass `hoverDropLines: true` in the chart's options on a yes. The result's
|
|
455
|
+
`dropLines` says which applies: `ask` carries the question, `on`/`off` means the user already
|
|
456
|
+
answered (the client asked them) and the generated component applies it. Keep the answer when
|
|
457
|
+
the chart is regenerated; never ask again.
|
|
450
458
|
- **GeoKind** - the result's `geo.kind` (the text reply's `Geo:` line). Without it a map draws
|
|
451
459
|
its marks over no land. `loadGeo` takes that geometry from chart-host itself, so the
|
|
452
460
|
`data.geo.json` the tool also writes beside a map is the same shapes as a file: the page never
|