@corva/ui 3.69.0-5 → 3.69.0-6

package/MCP_README.md

@@ -34,6 +34,16 @@ supports Claude Code, Cursor, and Codex CLI.
 - `get_diagnostics` - Get MCP server health metrics (memory, uptime, request stats, telemetry status)
 - `submit_feedback` - Send feedback about `@corva/ui` or this MCP server to the maintainers (docs gaps, wrong/missing
   props, search misses). The assistant can also call this on its own when it hits a gap.
+- `get_migration_guide` - Get the component migration manifest (source -> target pairs, tiers, per-prop transforms)
+- `get_dataset_types_guide` - Static reference for typing Corva dataset payloads from live field coverage: reading
+  `datasets_fields` output, mapping it to TypeScript, and wiring self-contained types into `@corva/ui` data callers.
+  Pairs with the `generate_dataset_types` prompt, which runs the full generate-and-stamp workflow.
+- `get_corva_mcp_setup_guide` - Static connection reference for the Corva MCP data server: endpoints, per-client
+  registration commands, browser OAuth flow, and the verification call. Pairs with the `setup_corva_mcp` prompt, which
+  runs the guided end-to-end setup.
+- `get_figma_to_code_guide` - Static method reference for implementing Figma designs with `@corva/ui`: source
+  precedence, capability-based component search across V2 and V1, token and prop discipline, and gap reporting. Pairs
+  with the `figma_to_code` prompt, which runs the strict guided workflow.
 
 ### Usage
 
@@ -101,6 +111,77 @@ mode (inside the `@corva/ui` repo itself) is auto-detected from `package.json` a
 /mcp__corva-ui__healthcheck
 ```
 
+- `migrate_components` — Migrate `@corva/ui` components from an older form to their current recommended replacement
+  (e.g. V1 → V2, deprecated V2 → Next, and future generations). Discovers `@corva/ui` imports across the workspace,
+  proposes a tiered plan (🟢 automatic / 🟡 supervised / 🔴 assisted), edits on your confirmation, leaves
+  `// TODO(migrate)` breadcrumbs for non-mechanical changes, then typechecks/lints. Backed by the
+  `get_migration_guide` tool.
+
+**Argument** (optional):
+
+- `input` — Freeform. Empty or `all` = broad scan of the whole workspace. One or more component names (e.g.
+  `Button Modal`) = targeted. Natural language ("migrate our buttons and modals") is parsed for intent.
+
+**Example invocations** (Claude Code):
+
+```
+/mcp__corva-ui__migrate_components
+/mcp__corva-ui__migrate_components Button Modal
+/mcp__corva-ui__migrate_components all
+```
+
+- `setup_corva_mcp` — Set up the remote **Corva MCP** (`corvian.corva.ai`) — the companion server for live Corva data
+  (separate from this docs server). Registers the remote HTTP server for Claude Code / Cursor / Codex CLI (any other
+  MCP client works via its own config) — globally for your user (default) or locally for the current project — walks
+  you through browser OAuth, and verifies with one read-only data call. Skips straight to verification when already
+  connected.
+
+**Argument** (optional):
+
+- `input` — Say `qa` to target the QA endpoint (`https://corvian.qa.corva.ai/mcp`); default is production
+  (`https://corvian.corva.ai/mcp`). Say `project` (or `local`) to register for the current project only; default is
+  user-global. Extra context (e.g. a preferred dataset for the verification call) is passed through.
+
+**Example invocations** (Claude Code):
+
+```
+/mcp__corva-ui__setup_corva_mcp
+/mcp__corva-ui__setup_corva_mcp qa
+/mcp__corva-ui__setup_corva_mcp project
+```
+
+**Notes:** auth is a browser OAuth flow — no API keys are stored or asked for. Newly registered MCP servers become
+visible only after a reconnect (`/mcp` in Claude Code) or a client restart; once reconnected the server is ready to
+use — re-running the prompt afterwards is an optional just-in-case check that verifies the connection with one data
+call. User-global registration makes the data server available in all your projects; project registration defaults
+to user-private config files and writes repo-tracked ones (a shared `.mcp.json`, a project `.codex/config.toml`)
+only after you explicitly accept that.
+
+- `generate_dataset_types` — Generate a best-effort TypeScript payload type for a Corva dataset collection from its
+  **live field coverage**, read through the Corva MCP's dataset tools. Dataset payloads are dynamic, so the result is
+  a **hint, not a contract**: partially-present fields become optional, ambiguous ones become `unknown`, and the type
+  carries a provenance stamp (collection, environment, sample size, date). The emitted types are self-contained (an
+  app-local record wrapper plus the `Payload`) and plug into `@corva/ui` data callers with a cast at the response
+  boundary. Re-running it for a collection whose generated type already exists
+  reports drift against the stamp instead of silently overwriting.
+
+**Argument** (optional; the assistant asks if missing):
+
+- `input` — The collection to type, as `provider#dataset` (e.g. `corva#wits`) or a searchable name. Extra context is
+  passed through: `qa` reads the QA environment, an asset/company narrows sampling scope, and a target file or type
+  name directs where the type lands.
+
+**Example invocations** (Claude Code):
+
+```
+/mcp__corva-ui__generate_dataset_types corva#wits
+/mcp__corva-ui__generate_dataset_types corva#completion.wits into src/apps/frac/types.ts as FracWitsPayload
+```
+
+**Prerequisite:** the remote Corva MCP must be connected in the same client session — run
+`/mcp__corva-ui__setup_corva_mcp` first if it is not. The prompt reads real data to compute the shape, so sampling
+stays scoped and minimal, and raw sample values are never pasted into committed code.
+
 ## Setup
 
 > **Just generated a fresh project with the latest `create-corva-app`?** MCP is already configured for Claude Code,