graphein-mcp 0.13.0 → 0.15.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "graphein-mcp",
-  "version": "0.13.0",
+  "version": "0.15.0",
   "type": "module",
   "description": "Model Context Protocol server for Graphein — wraps generate → validate → repair → render → critique into one tool call, and serves Graphein's schema + agent guide as resources so a model that never saw the API can still build correct charts.",
   "license": "MIT",
@@ -61,9 +61,9 @@
     "prepack": "tsup"
   },
   "dependencies": {
-    "@graphein/node": "^0.13.0",
+    "@graphein/node": "^0.15.0",
     "@modelcontextprotocol/sdk": "^1.20.0",
-    "graphein": "^0.13.0",
+    "graphein": "^0.15.0",
     "zod": "^3.23.0"
   }
 }

package/resources/agent-guide.md

@@ -734,5 +734,17 @@ chart.resize();           // re-measure after a layout change
 chart.destroy();          // remove on teardown (SPA route change, etc.)
 ```
 
+### Inspect & edit from the DOM
+
+Every `render`/`renderDashboard` root carries its effective config — the spec **minus its
+`data`** — as JSON in a `data-graphein-spec` attribute, plus a `data-graphein-type` marker.
+A browser tool can find Graphein visuals with
+`document.querySelectorAll('[data-graphein-spec]')` and read what they are without a JS handle.
+It's **two-way**: editing the attribute re-renders the chart, merging your edited config with
+the chart's existing in-memory data. Malformed JSON or specs that fail `validateSpec` are
+ignored, so a partial edit can't break a live chart. Opt out per chart (or dashboard) with
+`inspect: false` — `render(el, spec, { inspect: false })`, `renderDashboard(el, spec, { inspect: false })`,
+or the `inspect` prop on `<Chart>` / `<Dashboard>`.
+
 See the full field‑by‑field [Spec Reference](./spec-reference.md) and the
 machine‑readable [JSON Schema](./chart-spec.schema.json).