@bicharts/chart-mcp 0.3.5 → 0.5.49

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/README.md CHANGED
@@ -1,13 +1,22 @@
1
1
  # @bicharts/chart-mcp (experimental)
2
2
 
3
- An MCP (Model Context Protocol) stdio server that lets any MCP-capable AI client
4
- (Claude Code, Claude Desktop, Copilot Studio, Cursor, …) use the BIC chart engine:
3
+ > **Make Generative AI for Charts *Better*.**
4
+
5
+ An MCP (Model Context Protocol) stdio server that puts **RegiaBI** behind any
6
+ MCP-capable AI client (Claude Code, Claude Desktop, Copilot Studio, Cursor, …).
7
+
8
+ What that buys you: a working, interactive chart that **fits your data on the first
9
+ try** — real source you commit, with no D3, Vega or charting-API expertise in the
10
+ loop, and a solid starting point to adjust rather than a blank page. Because the
11
+ engine knows what ~90 chart types can honestly say, it will sometimes propose a view
12
+ — or a measure — you had not thought to ask for. Three tools:
5
13
 
6
14
  - **`assess_data_shape`** — profiles a CSV **locally** with the same measurement
7
15
  engine the Power BI visual uses (`@bicharts/shape-core`). No backend call, no
8
16
  credentials, no data leaves the machine. The free-teaser tool.
9
17
  - **`list_eligible_charts`** — the **authoritative** list of chart types that can
10
- render this data (server-side policy, not a local guess; **zero-credit**, no LLM).
18
+ render this data (server-side policy, not a local guess; **no LLM**, but a network
19
+ call to the engine and therefore **metered** — see Credentials).
11
20
  By default it **auto-detects the project's language** (JS/TS vs Python from the
12
21
  working dir) and returns the charts for THAT language — **scoped to its renderers
13
22
  and ranked by the picker's chart-type×renderer weights** (best first), each tagged
@@ -16,8 +25,10 @@ An MCP (Model Context Protocol) stdio server that lets any MCP-capable AI client
16
25
  `renderer: "D3"/"PLOTLY"/…` to rank one specific renderer, or `renderer: ""` for the
17
26
  full **renderer-agnostic** eligibility across all renderers (unranked — the wide "what
18
27
  *can* render" net). `top: N` trims to the best N. If the language can't be auto-detected
19
- and none is given, the tool asks you to specify one. Credentials optional (a license
20
- only unlocks *draft* types).
28
+ and none is given, the tool asks you to specify one. **Credentials required** no LLM
29
+ is not the same as no cost, because eligibility *is* the engine's own answer. Free within
30
+ a generous hourly allowance; beyond it a call may draw usage credits. A live licence
31
+ additionally unlocks *draft* types.
21
32
  - **`generate_chart`** — profiles locally, then calls the BIC backend, which picks
22
33
  an eligible chart type for the measured shape (or honors `chart_type`) and
23
34
  returns code that has passed the backend's gates/QC. Renderer selection is the same
@@ -96,12 +107,20 @@ npm install
96
107
  npm run build # bundles to dist/index.mjs (single file)
97
108
  ```
98
109
 
99
- ## Credentials (generate_chart only)
110
+ ## Credentials (`generate_chart` and `list_eligible_charts`)
100
111
 
101
112
  **A trial or paid BIC account is required — no freemium.** Use the same
102
113
  **License Key**, **Licensee**, and **Secret Key** from your BIC account (the ones
103
- the Power BI visual's license settings use). `assess_data_shape` needs no
104
- credentials at all (it runs entirely locally).
114
+ the Power BI visual's license settings use).
115
+
116
+ `assess_data_shape` needs no credentials at all — it runs entirely locally in
117
+ `@bicharts/shape-core` and never calls the backend. `list_eligible_charts` **does**
118
+ need them: it is the server's own eligibility verdict, not a local guess, which is
119
+ the whole reason it is worth calling. It is free within a generous hourly allowance;
120
+ beyond that, a call may draw usage credits from the account (both knobs are
121
+ server-configured), so don't put it inside a tight loop. Use of the API and this MCP
122
+ server is covered by the
123
+ [RegiaBI Programmatic Access Terms](https://bizintelligencechampions.com/terms-regiabi).
105
124
 
106
125
  Two ways to supply them — env wins over the file:
107
126