@bicharts/chart-mcp 0.6.46 → 0.6.48

package/README.md

@@ -1,7 +1,20 @@
-# @bicharts/chart-mcp (experimental)
+# @bicharts/chart-mcp
 
 > **Make Generative AI for Charts *Better*.**
 
+**Docs and examples:** [RegiaBI for developers](https://bizintelligencechampions.com/regiabi/developers?loc=npmmcp)
+· live demos in [React](https://codexguy.github.io/bicharts-react-demo/) and
+[Blazor](https://codexguy.github.io/bicharts-blazor-demo/) · the
+[React walkthrough](https://github.com/codexguy/bicharts-react-demo/blob/master/docs/WALKTHROUGH.md) · the
+[Blazor recipe](https://github.com/codexguy/bicharts/tree/main/examples/blazor) ·
+[how a fresh agent built a Blazor app through this server](https://bizintelligencechampions.com/articles/apps-ontologies-regiabi-sep2026)
+· [all articles](https://bizintelligencechampions.com/articles) ·
+[terms](https://bizintelligencechampions.com/terms-regiabi)
+
+Listed in the official [MCP Registry](https://registry.modelcontextprotocol.io/v0/servers/com.regiabi%2Fchart-mcp/versions/latest)
+as `com.regiabi/chart-mcp`, so any MCP host that reads the registry can find it; or run it with
+`npx -y @bicharts/chart-mcp` (setup below).
+
 An MCP (Model Context Protocol) stdio server that puts **RegiaBI** behind any
 MCP-capable AI client (Claude Code, Claude Desktop, Copilot Studio, Cursor, …).
 
@@ -103,14 +116,6 @@ Example (a semantic-model query result):
 }
 ```
 
-## Build
-
-```powershell
-cd mcp
-npm install
-npm run build     # bundles to dist/index.mjs (single file)
-```
-
 ## Credentials (`generate_chart` and `list_eligible_charts`)
 
 **A trial or paid BIC account is required — no freemium.** Use the same
@@ -278,33 +283,5 @@ or in a project `.mcp.json`:
 Claude Desktop uses the same `command`/`args`/`env` block in
 `claude_desktop_config.json` under `mcpServers`.
 
-**Developing on the server itself?** Point at your build instead, so you are not
-running whatever npx last cached:
-
-```powershell
-claude mcp add --scope user bic-chart-dev -- node c:/Source/PowerBI_Controls/llmchart/mcp/dist/index.mjs
-```
-
-The ready banner prints the build stamp, which is how you tell the two apart.
-
-Try: *"Assess the shape of testharness/datasets/divisional_revenue_by_year.csv,
-then generate a chart for it and write the preview to ./out."*
-
-## Wire notes
-
-Wire-compatible with the visual/harness envelope (see
-`testharness/harness/client.py`, the reference implementation): gzip→base64→`.`
-body, FNV X-Signature, `clientVersion >= 2.0.0.0`, plus `host: "SDK"` so prompts
-resolve to the generic host profile once server rev 144 + tokenized config are
-live (older servers ignore the field — deployment-order safe).
-
-## Publishing (when the experiment proves out — NOT yet)
-
-1. Keep `"private": true` until the conscious decision to release.
-2. Publish **built artifacts only** (`files: ["dist"]` already enforces this —
-   the tarball carries the bundled `dist/index.mjs`, no source, no history).
-3. `npm publish --access public` under the org scope; users then configure
-   `"command": "npx", "args": ["-y", "@bicharts/chart-mcp"]` — zero-install.
-4. List in MCP registries/directories for discoverability.
-5. shape-core rides inside the bundle minified (shared, not shown); the
-   open-source decision for readable source is separate and deferred.
+Try: *"Assess the shape of ./sales.csv, then generate a chart for it and write the
+preview to ./out."*