@bicharts/chart-mcp 0.6.34 → 0.6.45

package/README.md

@@ -47,7 +47,7 @@ only render text); `structuredContent` is for code, so nothing has to string-par
 
 | field | |
 | --- | --- |
-| `code` | the `render()` source (omitted when `include_code: false`) |
+| `code` | the `render()` source (omitted when `include_code: false`, which is the default when `out_dir` is given - the code is then on disk) |
 | `chartName`, `language`, `version`, `creditCost` | what was produced, and what it cost |
 | `correlationId` | the handle into the server-side log — quote it in any support request |
 | `outputHash` | the server's identity for this exact code (the same code always carries the same hash) — keep it with the chart |
@@ -201,18 +201,50 @@ visual (the MCP hits the same billed endpoint):
 
 The response header line shows `credits: N` so you can see what each call cost.
 
+## Telemetry
+
+The server tells the BIC service three things, and nothing else:
+
+- **A usage counter** for each call of `list_eligible_charts` and `generate_chart` that reaches the
+  service: the tool's name, this server's client version and a random nonce. No data, no account,
+  no machine identity.
+- **One row when `generate_chart` returns code**, joined to the generation the service already
+  logged (by its output hash) and marked as delivered through the MCP: the call's duration, the
+  row count, the requested language and this server's build. It records that the code was handed
+  over, never that anyone drew it.
+- **One row when a generation fails after the service answered**, carrying the service's own message.
+
+`assess_data_shape` never sends anything - it profiles your data locally, telemetry on or off.
+
+Set `BIC_MCP_TELEMETRY=0` in the server's environment to turn all of it off.
+
 ## The agent skill (recommended)
 
 This package ships `skills/bic-charts/SKILL.md` — the golden path from empty directory to a
 working cross-filtered dashboard: the scaffold command block, when to use the authoritative
 contract parameters instead of `prompt` prose, the coordinated-dashboard recipe, and the
-handful of places builds measurably lose time. Copy it where your agent looks for skills:
+handful of places builds measurably lose time. Copy it where your agent looks for skills, in the
+folder you'll work in. `npx` keeps the package in its own cache, not under `npm root`, so unpack
+it from the registry instead:
 
 ```powershell
+$tgz = npm pack @bicharts/chart-mcp
+tar -xzf $tgz
 mkdir -Force .claude\skills
-Copy-Item -Recurse (npm root)\@bicharts\chart-mcp\skills\bic-charts .claude\skills\
+Copy-Item -Recurse package\skills\bic-charts .claude\skills\
+Remove-Item -Recurse package, $tgz
+```
+
+```bash
+tgz=$(npm pack @bicharts/chart-mcp 2>/dev/null)
+tar -xzf "$tgz"
+mkdir -p .claude/skills && cp -r package/skills/bic-charts .claude/skills/
+rm -rf package "$tgz"
 ```
 
+(PowerShell does not expand a `*` for `tar`, so `tar -xzf bicharts-chart-mcp-*.tgz` fails there;
+capturing the file name `npm pack` prints works in both shells.)
+
 An agent that reads it first does in a few calls what otherwise takes thirty — most of the
 difference is not knowing the API, it is not knowing the shape of the answer.