@fusedashlabs/ui9000-mcp 5.3.0

package/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2025 Ido Salomon
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,495 @@
+# UI9000-MCP
+
+MCP server for creating charts from data. Attach a CSV or pass values in chat, choose a chart type (bar, line, pie, map, KPI, network, and more), and the chart renders in the MCP Apps view — Cursor, Claude Desktop, or any host that supports MCP Apps.
+
+**npm:** [`@fusedashlabs/ui9000-mcp`](https://www.npmjs.com/package/@fusedashlabs/ui9000-mcp)  
+**Server key** in Cursor / Claude: `UI9000-MCP`
+
+---
+
+## Install in Cursor or Claude (npm)
+
+Node.js 22+. The CLI starts **stdio MCP** plus a local **data-link HTTP** server on `127.0.0.1` (so widgets can fetch JSON). No clone required.
+
+### Cursor
+
+Add to `~/.cursor/mcp.json` (or project `.cursor/mcp.json`):
+
+```json
+{
+  "mcpServers": {
+    "UI9000-MCP": {
+      "command": "npx",
+      "args": ["-y", "@fusedashlabs/ui9000-mcp"],
+      "env": {
+        "MCP_TOOL_PROFILE": "mvp"
+      }
+    }
+  }
+}
+```
+
+Restart Cursor. Use `"full"` for every chart tool.
+
+### Claude Desktop
+
+Edit `claude_desktop_config.json`:
+
+```json
+{
+  "mcpServers": {
+    "UI9000-MCP": {
+      "command": "npx",
+      "args": ["-y", "@fusedashlabs/ui9000-mcp"],
+      "env": {
+        "MCP_TOOL_PROFILE": "mvp"
+      }
+    }
+  }
+}
+```
+
+Optional env:
+
+| Variable | Default (npx CLI) | Meaning |
+| --- | --- | --- |
+| `MCP_TOOL_PROFILE` | `mvp` | `mvp` = 6 chart tools; `full` = all chart types |
+| `MCP_BASE_URL` | auto `http://127.0.0.1:8088` | Skip local HTTP if you already run `pnpm mcp:serve` |
+| `MCP_UI_RESOURCE_MIME` | `mcp-app` | Claude / Cursor MCP Apps MIME |
+| `PORT` | `8088` | Local data-link port (`0` / in-use → random) |
+| `STORAGE_DIR` | `~/.mcp-ui/data` | Signed payload files |
+| `MCP_DATA_LINK_SECRET` | dev default locally | Required in production-like envs |
+
+Attach a CSV in chat, then ask for a chart (see `chart-test-kit/prompts.md` in the workspace).
+
+---
+
+## Requirements
+
+- **Node.js 22+**
+- **pnpm** (via corepack or global install)
+- Sibling package **`ui9000-widgets`** at `../ui9000-widgets` when building the MCP App View (`file:` dependency)
+
+---
+
+## Quick Start (<10 min)
+
+1. **Install:**
+   ```bash
+   pnpm install
+   pnpm --dir ../ui9000-widgets build   # if widgets changed / first clone
+   pnpm build:mcp-app
+   ```
+
+2. **Environment:**
+   ```bash
+   cp env.local .env   # or env.prod / .env.example
+   ```
+
+3. **HTTP/SSE** (signed data-links + local HTTP):
+   ```bash
+   pnpm run mcp:serve
+   ```
+   Default port from `.env` (often `8088` or `5173`). Expect: `MCP Server running over SSE on port …`
+
+4. **Stdio** (Claude Desktop / Cursor local MCP):
+   ```bash
+   pnpm run mcp:serve:stdio
+   ```
+   Stdio alone does **not** serve `/v1/data-links`. Keep `pnpm mcp:serve` running (or point `MCP_BASE_URL` at a deployed HTTP instance) whenever charts need signed payloads. Data-link files live under **`mcp-ui/.data`** (package root), not `process.cwd()`, so Cursor/Claude stdio and `mcp:serve` share the same store.
+
+### Install in Claude Desktop (from a clone)
+
+Prefer **npx** (see [Install in Cursor or Claude (npm)](#install-in-cursor-or-claude-npm)). Clone + stdio is for local development.
+
+Edit `claude_desktop_config.json` (absolute paths; prefer `tsx` over `pnpm` to avoid Corepack version checks):
+
+```json
+{
+  "mcpServers": {
+    "UI9000-MCP": {
+      "command": "/absolute/path/to/mcp-ui/node_modules/.bin/tsx",
+      "args": ["/absolute/path/to/mcp-ui/src/mcp-stdio.ts"],
+      "env": {
+        "MCP_BASE_URL": "http://localhost:8088",
+        "MCP_TOOL_PROFILE": "mvp"
+      }
+    }
+  }
+}
+```
+
+Or install the **`.mcpb`** bundle (see [MCPB pack](#mcpb-pack-p28)) via Claude’s extension install dialog.
+
+### Install in Cursor (from a clone)
+
+Prefer **npx** (see [Install in Cursor or Claude (npm)](#install-in-cursor-or-claude-npm)). Clone + `tsx` is for local development.
+
+Add to `~/.cursor/mcp.json` (or project `.cursor/mcp.json`). Prefer invoking **`tsx` directly** (avoids Corepack/pnpm version mismatch when Cursor spawns the process):
+
+```json
+{
+  "mcpServers": {
+    "UI9000-MCP": {
+      "command": "/absolute/path/to/mcp-ui/node_modules/.bin/tsx",
+      "args": ["/absolute/path/to/mcp-ui/src/mcp-stdio.ts"],
+      "env": {
+        "MCP_BASE_URL": "http://localhost:5173",
+        "MCP_TOOL_PROFILE": "mvp"
+      }
+    }
+  }
+}
+```
+
+Run `pnpm install` once so `node_modules/.bin/tsx` exists. Keep `pnpm mcp:serve` running for signed data-links.
+
+Match `MCP_BASE_URL` / `PORT` to your running `mcp:serve`. Cursor may show tool results as links/text; full MCP Apps iframe rendering varies by host (see [Known limitations](#known-limitations)).
+
+### Prompt examples (copy-paste)
+
+| # | Prompt | Expected tool / chart |
+|---|--------|------------------------|
+| 1 | `Create a line chart of monthly sales: Jan 10, Feb 20, Mar 15. Title "Sales trend".` | `generate_simple_single_series_chart` → `lineChart` (inline `@ui9000/widgets`) |
+| 2 | `Pie chart of share: Alpha 40, Beta 35, Gamma 25. Title "Market share".` | `generate_pie_chart` → pie (`@ui9000/widgets`) |
+| 3 | `Load this CSV as a dataset then chart revenue by region with a bar chart:` *(paste small CSV or use `load_dataset` then chart with `datasetId`)* | `load_dataset` → `generate_simple_single_series_chart` / bar |
+
+### Screenshot
+
+Add a PNG of a rendered chart in Claude (MCP Apps) at `docs/screenshots/claude-chart.png` when available. Until then, verify locally: tool result `_meta.dataUrl` in the MCP App View.
+
+### Transport support
+
+| Transport | Command / endpoint | FuseDash | Claude Desktop | Cursor |
+|-----------|--------------------|----------|----------------|--------|
+| Streamable HTTP | `POST /mcp` via `mcp:serve` | Yes | Supported | Possible via URL config |
+| SSE | `GET /sse` via `mcp:serve` | Yes | Supported | Possible via URL config |
+| Stdio | `pnpm mcp:serve:stdio` | No | Primary local path | Primary local path |
+
+**P13 verification:** automated IT covers list-tools / read `ui://ui9000/chart` / call chart tool on in-memory, Streamable HTTP, SSE, and stdio (`src/mcp/transport.integration.test.ts`). Claude Desktop visual check: install via stdio config above (or `.mcpb`), confirm MCP App View loads; for HTTP use local `mcp:serve` URL if the host allows remote MCP.
+
+Chart tools advertise `_meta.ui.resourceUri: ui://ui9000/chart`. CSP `connectDomains` comes from `MCP_BASE_URL` (`frameDomains` is empty — widgets fetch JSON, no nested charts app).
+
+**Render:** `@ui9000/widgets` in the MCP App View. Unsupported `chartType` values show the View empty state (no `apps/charts` iframe).
+
+Rebuild the View after editing `src/mcp-app/` or widgets:
+
+```bash
+pnpm --dir ../ui9000-widgets build
+pnpm build:mcp-app
+```
+
+### MCPB pack (P28)
+
+```bash
+pnpm pack:mcpb
+```
+
+Produces `dist/mcp-ui.mcpb` from `manifest.json` (stdio entry via `pnpm` + this directory). Requires Node 22 + pnpm on the install host. User config prompts for `MCP_BASE_URL`.
+
+### GitHub release (P29)
+
+Push a tag `mcp-v*` or `v*` (or run **Release mcpb** workflow dispatch) to:
+1. Pack `dist/mcp-ui.mcpb` and attach it to a GitHub Release
+2. Trigger the existing `ci.yml` tag path that deploys HTTP/SSE to staging (`mcp-v*`)
+
+Remote clients: use staging `MCP_BASE_URL` → `GET /sse` or `POST /mcp`, plus `/v1/data-links` for chart payloads.
+
+### Known limitations
+
+| Topic | Detail |
+|-------|--------|
+| Map charts | Empty View until Mapbox/PMTiles land in `@ui9000/widgets` |
+| Host UI | Claude MCP Apps render `ui://`; Cursor/VS Code may only show tool text/`dataUrl` |
+| Stdio vs data-links | Chart tools need HTTP `MCP_BASE_URL` reachable for signed payloads |
+| Widget coverage | Unsupported types show empty state in the MCP App View — no charts iframe |
+| SSE “reconnect” | `GET /sse?sessionId=…` returns **400** — clients must open a new SSE session |
+| Tool profile | `MCP_TOOL_PROFILE=mvp` shrinks `tools/list`; FuseDash uses `full` by default |
+
+### Host verification (P31)
+
+Same stdio / HTTP / `.mcpb` artifacts for every host — **no per-host code forks**.
+
+| Host | Install path | Tools / data-links | MCP Apps UI (`ui://`) | Status |
+|------|--------------|--------------------|----------------------|--------|
+| Claude Desktop | Stdio or `.mcpb` | Yes (with HTTP `MCP_BASE_URL`) | Yes (primary) | Verified path (P13 + IT) |
+| Cursor | Stdio (`~/.cursor/mcp.json`) | Yes | Partial / host-dependent | Smoke locally |
+| VS Code Insiders (MCP) | Stdio or HTTP URL | Expected yes | Depends on MCP Apps support in extension | Not fully verified — re-test after release |
+| ChatGPT (MCP Apps) | Remote HTTP when host allows | Expected yes | Depends on host CSP / Apps support | Not fully verified — use same HTTP artifact |
+| Goose | Stdio or HTTP | Expected yes | Host-dependent | Not fully verified — no Goose-specific code |
+
+If a host needs a code branch, fix handshake/CSP in P1 instead of forking.
+
+### Production secret check (P04)
+
+```bash
+# Offline: ensure env.prod (or ENV_FILE) is not the known-dev default — never prints the secret
+pnpm check:data-link-secret
+ENV_FILE=env.prod pnpm check:data-link-secret
+```
+
+HTTP/stdio entrypoints refuse to start when `NODE_ENV`/`MCP_ENV`/`ENV_FILE` look production-like and `MCP_DATA_LINK_SECRET` is missing, too short, or a known default (`dev-secret-key-for-testing`, `secret`, …).
+
+### Known limitations
+
+1. **Build the image:**
+   ```bash
+   docker build --build-arg ENV_FILE=env.prod -t mcp-ui .
+   ```
+   
+   The build process will extract the `PORT` value from your `env.prod` file and display it in the logs.
+
+2. **Run the container:**
+   ```bash
+   docker run -p 5173:5173 mcp-ui
+   ```
+   
+   Replace `5173` with the actual `PORT` value from your `env.prod` file (shown during build).
+
+   **With persistent storage:**
+   ```bash
+   # Windows PowerShell
+   docker run -p 5173:5173 -v ${PWD}/.data:/app/.data mcp-ui
+   
+   # macOS/Linux
+   docker run -p 5173:5173 -v $(pwd)/.data:/app/.data mcp-ui
+   ```
+
+   **Run in background:**
+   ```bash
+   docker run -d -p 5173:5173 --name mcp-ui-container mcp-ui
+   ```
+
+---
+
+## Environment Variables
+
+Create a `.env` file in the project root with the following variables:
+
+| Variable | Description | Default |
+|----------|-------------|---------|
+| `PORT` | Port for the Express MCP server | `8088` |
+| `MCP_BASE_URL` | Base URL for signed data links | `http://localhost:8088` |
+| `MCP_DATA_LINK_SECRET` | Secret key for signing data links | `dev-secret-key-for-testing` |
+| `CORS_ALLOWED_ORIGINS` | Comma-separated list of allowed origins or `*` | `*` |
+| `STORAGE_DIR` | Directory for storing chart payloads (relative to project root) | `.data` |
+| `DATA_LINK_TTL_HOURS` | Time-to-live for data links in hours | `24` |
+| `MAX_PAYLOAD_SIZE_MB` | Maximum payload size in megabytes for data links | `1.5` |
+| `MCP_TOOL_PROFILE` | `full` (default, FuseDash) or `mvp` (6 charts + helpers) | `full` |
+| `MCP_UI_RESOURCE_MIME` | MCP Apps MIME (`mcp-app`) | `mcp-app` (npx) |
+
+**Example `.env` file:**
+```env
+PORT=5173
+STORAGE_DIR=.data
+MCP_BASE_URL=http://localhost:5173
+MCP_DATA_LINK_SECRET=your-secret-key-here
+DATA_LINK_TTL_HOURS=24
+MAX_PAYLOAD_SIZE_MB=1.5
+CORS_ALLOWED_ORIGINS=https://charts.example.com,https://mcp.example.com
+```
+
+---
+
+## API Endpoints
+
+### Data Links
+
+**Create a data link:**
+```http
+POST /v1/data-links
+Content-Type: application/json
+
+{
+  "config": { ... },
+  "data": { ... },
+  "meta": {
+    "source": "mcp",
+    "expiresInHours": 24
+  }
+}
+```
+
+**Response:**
+```json
+{
+  "id": "abc123",
+  "dataUrl": "http://localhost:5173/v1/data-links/abc123?sig=...&exp=..."
+}
+```
+
+**Retrieve a data link:**
+```http
+GET /v1/data-links/:id?sig=...&exp=...
+```
+
+**Response:**
+```json
+{
+  "id": "abc123",
+  "config": { ... },
+  "data": { ... },
+  "createdAt": "2024-01-01T00:00:00Z",
+  "ttlSeconds": 86400,
+  "meta": { ... }
+}
+```
+
+### Health Checks
+
+- `GET /health` - Detailed health status with stats
+- `GET /health/ready` - Readiness probe
+- `GET /health/live` - Liveness probe
+
+---
+
+## MCP Tools (SSE)
+
+The MCP server exposes tools via Server-Sent Events (SSE):
+
+- **SSE Endpoint:** `GET /sse` and `POST /sse/message`
+- **Alias:** `GET /mcp` and `POST /mcp/message`
+
+### Available Chart Tools
+
+All tools are defined in `src/mcp/registerTools.ts` and include:
+
+- **Basic Charts:** Bar, Line, Lollipop, Area (simple, grouped, stacked, cumulative)
+- **Advanced Charts:** Sankey, Treemap, Histogram, Bubble, Scatterplot, Boxplot, Punchcard
+- **Specialized:** SparkLine, SparkArea, KPIs, Map (with multiple layer types)
+- **ML/Stats:** KS Plot, ROC Curve, Gini Impurity & Entropy, Violin, Partial Dependence, Bias-Variance Tradeoff
+- **Q-Q Plot:** Scatterplot with reference line option
+
+All tools return an `externalUrl` UI resource that embeds the charting application with the signed data link.
+
+---
+
+## Storage
+
+Chart payloads are stored as JSON files in the `STORAGE_DIR` directory (default: `.data/`):
+
+- Each data link is saved as `{id}.json`
+- Files are automatically cleaned up when expired (TTL check on access)
+- Storage directory is created automatically if it doesn't exist
+
+**Location:** `{STORAGE_DIR}/{id}.json` relative to the project root (or container working directory).
+
+---
+
+## Development
+
+### Scripts
+
+- `pnpm run mcp:serve` - Run the MCP Node.js server (Express + SSE)
+- `pnpm run dev` - Run the React Router UI in development mode
+- `pnpm run build` - Build the React Router application
+- `pnpm run typecheck` - Type check the codebase
+- `pnpm test` - Run tests
+- `pnpm run lint` - Lint code
+- `pnpm run lint:fix` - Fix linting issues
+
+### Project Structure
+
+```
+src/
+  ├── mcp-node.ts          # Express server + MCP initialization
+  ├── mcp/
+  │   └── registerTools.ts # MCP tool definitions
+  ├── api/
+  │   ├── healthCheck.ts   # Health check handlers
+  │   └── handleDataLink.ts # Data link API handlers
+  └── utils/
+      ├── dataLinkStore.ts # Filesystem-based TTL storage
+      ├── dataLinkHandlers.ts # CORS, validation, rate limiting
+      └── createChartData.ts # Helper for chart data links
+```
+
+---
+
+## Docker Details
+
+### Build Process
+
+The Dockerfile:
+1. Extracts the `PORT` value from the specified `ENV_FILE` during build
+2. Displays the extracted port in build logs
+3. Copies the environment file as `.env` for runtime use
+4. Runs the MCP server with `pnpm run mcp:serve`
+
+### Build Arguments
+
+- `ENV_FILE` - Environment file to use (default: `env.prod`)
+
+### Example Build & Run
+
+```bash
+# Build with custom env file
+docker build --build-arg ENV_FILE=env.prod -t mcp-ui .
+
+# Check the PORT value in build logs (look for "PORT extracted from env.prod: XXXX")
+
+# Run with the extracted port
+docker run -p 5173:5173 mcp-ui
+
+# Run with persistent storage
+docker run -p 5173:5173 -v ${PWD}/.data:/app/.data mcp-ui
+
+# Run in background
+docker run -d -p 5173:5173 --name mcp-ui-container mcp-ui
+
+# View logs
+docker logs mcp-ui-container
+
+# Stop container
+docker stop mcp-ui-container
+```
+
+---
+
+## Security Notes
+
+- **Use a strong `MCP_DATA_LINK_SECRET`** in production
+- **Restrict `CORS_ALLOWED_ORIGINS`** to specific domains instead of `*`
+- **Adjust `DATA_LINK_TTL_HOURS`** based on your data retention requirements
+- **Rate limiting** can be enabled in `src/utils/dataLinkHandlers.ts`
+
+---
+
+## FAQ
+
+**Q: Where are data files stored?**  
+A: In the `STORAGE_DIR` directory (default: `.data/`) relative to the project root. Files are named `{id}.json`.
+
+**Q: How are charts rendered?**  
+A: MCP Apps View (`ui://ui9000/chart`) plus `_meta.dataUrl`. There is no `apps/charts` iframe.
+
+**Q: How do I enforce strict CORS?**  
+A: Set `CORS_ALLOWED_ORIGINS` to a comma-separated list of allowed domains: `CORS_ALLOWED_ORIGINS=https://example.com,https://other.com`
+
+**Q: What port does the server use?**  
+A: The port is read from the `PORT` environment variable (in `.env` file). Default is `8088`.
+
+**Q: How do I check if the server is running?**  
+A: Visit `http://localhost:<PORT>/health` or use the health check endpoints.
+
+---
+
+## Publish to npm
+
+From this repo (must be logged in to an npm user/org that can publish `@fusedashlabs/*`):
+
+```bash
+pnpm install
+pnpm build:npm
+npm publish --access public
+```
+
+CI: push a `v*` / `mcp-v*` tag or run the **Publish npm** workflow. Set GitHub secret `NPM_TOKEN`.
+
+After publish, Cursor/Claude use `npx -y @fusedashlabs/ui9000-mcp` with server key `UI9000-MCP` (see top of this README).
+
+---
+
+## License
+
+Apache-2.0