@lineadraw/mcp 0.1.0

package/README.md

@@ -0,0 +1,85 @@
+# @lineadraw/mcp
+
+MCP server for Linea CAD documents, with the **full Linea editor in chat**
+(MCP Apps extension): Claude creates/edits documents through tools and opens
+them as a fully interactive editor directly in the conversation — the user
+can draw, snap, dimension, and edit, and their changes flow back into the
+same document Claude's tools operate on.
+
+## Run
+
+```bash
+npm run build -w @lineadraw/mcp     # bundles the editor into dist/editor.html
+npm run serve -w @lineadraw/mcp     # streamable HTTP on http://localhost:3001/mcp
+```
+
+MCP server definition
+
+```json
+"mcpServers": {
+    "linea": {
+      "command": "node",
+      "args": [
+        "C:\\Users\\MikhailKoshelev\\source\\repos\\linea\\packages\\mcp\\dist\\server.js",
+        "--stdio"
+      ]
+    }
+  }
+```
+
+Claude (web and Desktop) requires an **https** connector URL. Two options:
+
+**Tunnel** (no account, URL changes each run, briefly internet-reachable):
+
+```bash
+npx cloudflared tunnel --url http://localhost:3001
+```
+
+**Local TLS with [mkcert](https://github.com/FiloSottile/mkcert)** (nothing
+leaves your machine; the mkcert CA lands in the Windows/macOS trust store,
+which Claude Desktop honors):
+
+```powershell
+mkcert -install
+mkcert localhost
+$env:TLS_CERT="localhost.pem"; $env:TLS_KEY="localhost-key.pem"; npm run serve -w @lineadraw/mcp
+```
+
+Settings → Connectors → Add custom connector → the https URL + `/mcp`
+(e.g. `https://localhost:3001/mcp`). The MCP endpoint answers on `/` too.
+
+`node probe.mjs <url>` checks any URL the way a host would (GET probe + full
+handshake + a tool call).
+
+## Tools
+
+`linea_new_document` · `linea_open_document` · `linea_save_document` ·
+`linea_add_objects` (model space or `layout`) · `linea_update_objects`
+(per-id patches) · `linea_remove_objects` · `linea_transform`
+(move/rotate/scale/mirror/copy/array; degrees) · `linea_create_layout` ·
+`linea_summary` · `linea_get_document` · `linea_replace_document` (full-state
+save used by the in-chat editor) · `linea_export` (svg/png/pdf/dxf) ·
+**`linea_show_document`** — opens the in-chat editor.
+
+## The in-chat editor
+
+`ui-editor/` bundles the real `@lineadraw/editor` (React + Tailwind v4 + Inter)
+into ONE self-contained `dist/editor.html` (~5 MB) — the sandboxed iframe's
+CSP allows no external assets. `linea_show_document` renders it with the
+document pushed as the tool result. Committed edits are debounced into
+`linea_replace_document`, so the conversation's granular tools and the
+interactive editor share one source of truth (the server registry). Foreign
+changes (Claude's tool calls) are detected by revision polling and remount
+the editor with the camera restored.
+
+Sizing: the app reports a real content height (720px inline) through the
+protocol's auto-resize and fills the frame under the host's `fullscreen`
+display mode. Placement is the host's decision — the protocol offers
+`inline | fullscreen | pip` only, so a persistent "panel right of the chat"
+isn't requestable today.
+
+Open `dist/editor.html#demo` in a browser to develop the editor app
+standalone (loads a built-in document, no MCP host needed).
+
+In-chat caveat: disk-oriented menu items (Open/Save As) are limited by the
+iframe sandbox — save through the conversation via `linea_save_document`.