@genclass/mcp 0.0.0-stage → 0.2.0

package/CHANGELOG.md

@@ -0,0 +1,83 @@
+# Changelog
+
+## 0.2.0 (2026-10-25)
+
+The `0.1.0` on npm (published 2026-10-25) is an earlier build: eight tools, no `genclass_scan`, no `GENCLASS_REPORT`.
+Everything below ships first in `0.2.0`.
+
+- **`genclass_setup` installs the newest runtime line.** It prints `npm install @genclass/runtime@beta` (the agent
+  entry and interaction analytics need 0.3.0-beta.1 or later) for a project on 0.2.x, on a range without a version
+  (`*`, `latest`: npm's `latest` is still 0.2.x) or with an older copy in `node_modules`, and says what the project
+  has. The README's connect step names `@beta` first.
+- **`genclass_scan {url, phone?, hosted?}`: audit any page in one step** ([docs/runtime/AGENT.md](../../docs/runtime/AGENT.md)
+  section 4.2). It runs `@genclass/runtime`'s `scan --json` (the project's own runtime when it has the command, else
+  `npx -y @genclass/runtime@beta`) in the project's folder: headless Chromium at desktop and phone sizes with the 23
+  measured visual checks, and returns a score and each problem with its element, selector and suggested CSS fix (page
+  text cleaned and labelled as data), plus the report as JSON (a second text block and `structuredContent`). It passes
+  `--local` unless the agent sets `hosted: true`, so without Playwright's Chromium it says how to install it instead
+  of sending the URL anywhere; `hosted: true` uses the genclass.dev page check (public pages only). The server's
+  instructions and the plugin skill say to scan a page before calling a UI change done. Nine tools.
+
+- **Fixed: a race replay counts page lines.** Explore compares page text as counts, so a product name the page
+  always shows once and a stale result showed a second time was "only in the failing run"; the replay verdict then
+  checked presence only, and the card alone made every replay "reproduced", including after the fix. The finding's
+  evidence now keeps the counts (`textCounts`) and the verdict needs the line as many times as the failing run showed
+  it. Found by the end-to-end walkthrough, covered by a test.
+- **Fixed: with `GENCLASS_REPORT` set, the tools' own calls are mirrored too.** The server's in-process API (what
+  `genclass_explain`, `genclass_replay`, `genclass_explore` and `genclass_clear` call when this session owns the
+  bridge) bypassed the reporting wrapper, so a dashboard only ever received the findings; the evidence read, the test,
+  replays armed and their verdicts, explore reports and clears reached it only through the bridge's HTTP path. Found
+  by the end-to-end walkthrough (`docs/evidence/e2e-walkthrough`), covered by a test.
+- **Opt-in reporting to the app's dashboard** (`GENCLASS_REPORT`; [docs/runtime/AGENT.md](../../docs/runtime/AGENT.md)
+  section 4.5). Set to `on` (with `GENCLASS_DASHBOARD`) or to a dashboard link, the server mirrors its log of the loop
+  to that dashboard: each finding the bridge makes, each time the agent reads its evidence (`genclass_explain`), each
+  replay armed and each replay verdict, each regression test written, each explore report (page loads compared, races
+  found) and each clear: `POST /api/projects/<secret>/agent`, batched, best effort, ids, kinds, page paths, verdicts,
+  counts and times only, never page text. The dashboard's Closed-loop development view then draws every issue's path
+  (found, reproduced, fix proven, closed, or round again when a replay after a fix still reproduces it) with the
+  period's counts, lists the log newest first, and shows per production problem what the agent reproduced, tested and
+  proved fixed. Off unless set; nothing sent feeds a decision, a finding or a tool result.
+
+- **Explore stops reporting order-dependent bookkeeping as races** ([docs/runtime/AGENT.md](../../docs/runtime/AGENT.md)
+  section 5.1, [RESULTS.md](../../docs/runtime/RESULTS.md) section 20). A reordered run is a race only when what the
+  page shows, its form values, the requests it sent or its errors differ from the request-order baseline; store values
+  that differ while the page is the same are listed as "Internal state only", and an overwrite a later response
+  repaired as "Along the way only", neither with a finding. A `[redacted]` value equals any value. Scenarios are
+  grouped with digits blanked, parenthesised counts dropped and a typing burst split by a label change joined again,
+  falling back to action kinds and element roles, then kinds, when names changed with the order; the report says how
+  many reordered runs it compared and says "0 compared" (no verdict) rather than "No race found" when none was. Race
+  finding titles, keys, replays and generated tests lead with what the page showed (store values only for a finding
+  with nothing else). Snapshots may carry up to 1,200 store fields and say how many the page left out. The explore
+  tool's description and the plugin skill say the same. On the Strapi admin's 21 interaction sessions the race-like
+  verdicts went from 16 to 0 (reordered runs reported as races: 62, all false, to 0; sessions without a usable verdict:
+  5 to 0), and the real 403 race is still found at 300, 600 and 900 ms (6 of 6 runs, 0 false); on a correct Redux
+  Toolkit Query page the false reports went from 18 of 18 reordered runs to 0; the e2e page still finds its race in 5
+  of 6 reordered runs and none on the fixed page.
+
+- First version: the GenClass MCP server for coding agents ([docs/runtime/AGENT.md](../../docs/runtime/AGENT.md)).
+  A bridge on 127.0.0.1:47357 that pages connect to through `@genclass/runtime/agent`; eight tools
+  (`genclass_status`, `genclass_findings`, `genclass_explain`, `genclass_explore`, `genclass_replay`,
+  `genclass_analytics`, `genclass_setup`, `genclass_clear`); findings deduplicated and kept in
+  `.genclass/agent/state.json`; explore verdicts from final states against request-order baselines; replays with
+  reproduced / not reproduced verdicts; Playwright regression tests generated from a finding; new findings pushed as
+  Claude Code channel events or through a `UserPromptSubmit` hook; one bridge shared by every agent session on the
+  machine; production numbers read from the developer's GenClass dashboard. No dependencies. The bridge accepts pages
+  only from the developer's machine (or origins listed in `GENCLASS_AGENT_ORIGINS`), binds each run to the page that
+  registered it (origin and token), guards its agent API with a per-user token, quotes every page string it shows the
+  agent and strips invisible characters. A Claude Code plugin (`plugin/`: the server, the prompt hook and a skill) and
+  an MCP Registry entry (`server.json`) ship with it. Needs `@genclass/runtime` 0.3.0-beta.1 or later in the app
+  (`@genclass/runtime/agent`). Released by `.github/workflows/release-mcp.yml` from a `mcp-v<version>` tag.
+- Ready for registries and directories: a `server.json` description of at most 100 characters (the official MCP
+  Registry's limit; checked against its 2025-12-11 schema and accepted by `mcp-publisher validate`), a `title` and
+  `websiteUrl`; the release workflow publishes it to the registry with GitHub OIDC (pinned, checksummed
+  `mcp-publisher`) after npm, and uploads an MCP Bundle (`npm run bundle`: `genclass-<version>.mcpb`, for Claude
+  Desktop and Smithery) as an artifact. Every launcher is pinned to the release (`npx -y @genclass/mcp@<version>`):
+  the plugin's server and hook, `init`, and the install blocks; `npm run sync` rewrites the pins from
+  `package.json` and the tests fail when one differs. Install blocks for Claude Code, Claude Desktop, Cursor (with an
+  install link), VS Code (`code --add-mcp` and an install link), Codex CLI, Gemini CLI, Windsurf, Cline, Goose, Zed,
+  JetBrains IDEs and OpenCode, printed by `genclass-mcp config [client]` and in the README; `genclass_setup` adds the
+  block for the client it runs in (from `clientInfo` at initialize). Every tool's annotations carry `title`,
+  `readOnlyHint`, `destructiveHint` and `openWorldHint`. The plugin has a README (what it installs, what the hook
+  sends where, how to turn it off), directory links in `plugin.json`, and an [Agent Plugins](https://agent-plugins.org)
+  `plugin.json` and `mcp.json` for Cursor and Codex; the repository root has `glama.json`, `gemini-extension.json`,
+  `llms-install.md` and `.cursor-plugin/marketplace.json`. Listing drafts: `docs/adoption/listings/mcp.md`.

package/LICENSE

@@ -0,0 +1,202 @@
+
+                                 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 [yyyy] [name of copyright owner]
+
+   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

@@ -1,3 +1,364 @@
-# Temporary Holding Version
+# @genclass/mcp
 
-This version is a temporary placeholder for this package. An operational version to replace this has been submitted for review and is awaiting a staged release.
+### Your coding agent can see the race, replay it, and prove the fix.
+
+An MCP server for Claude Code and other coding agents. It connects to the pages of your app running on your machine
+(through [`@genclass/runtime`](https://www.npmjs.com/package/@genclass/runtime)'s agent link) and gives the agent:
+
+- **What happened, in order.** Every click, request and response, the order the responses were delivered, what each
+  response wrote into the app's state, and uncaught errors with the click and request that led to them.
+- **Bugs that never throw.** A response that overwrote newer data (the classic stale search result or lost edit), the
+  same order submitted twice by two clicks, and the on-device model's own detections.
+- **Races found before users find them.** `genclass_explore` runs your steps again with the network answering in
+  different orders (and slower, if you like) and reports what ends differently from the run where responses came back
+  in order.
+- **Proof.** `genclass_replay` delivers the exact order that produced a bug again, before your fix (reproduced) and
+  after it (not reproduced), and `genclass_explain` writes a Playwright test that fails while the bug is there.
+
+Everything stays on your machine. No dependencies. The server is free. For developers who want the loop run for
+them, GenClass runs it as a service under Enterprise: the MCP server, collector and dashboard hosted by GenClass or
+inside your network ([genclass.dev/enterprise](https://genclass.dev/enterprise)).
+
+## Install
+
+Pick your client. Every block pins this release, so the client starts exactly this version;
+`npx -y @genclass/mcp@0.2.0 config <client>` prints the same lines, and `genclass_setup` prints the block for the
+client it runs in.
+
+<!-- install:start (generated from src/clients.ts by `npm run sync -w @genclass/mcp`; edit it there) -->
+
+### Claude Code
+
+As a plugin (the server, a prompt hook that brings new findings to each prompt, and a skill that tells Claude when to use it):
+
+```
+/plugin marketplace add genclass-dev/GenClass-lib
+/plugin install genclass@genclass
+```
+
+Or the server alone (`--scope project` writes `.mcp.json` for everyone on the project; `--scope user` for all your projects):
+
+```bash
+claude mcp add --scope project genclass -- npx -y @genclass/mcp@0.2.0
+# or: npx -y @genclass/mcp@0.2.0 init --hook   (.mcp.json, plus the prompt hook in .claude/settings.json)
+```
+
+### Claude Desktop
+
+Settings, Developer, Edit Config (`~/Library/Application Support/Claude/claude_desktop_config.json` on macOS, `%APPDATA%\Claude\claude_desktop_config.json` on Windows):
+
+```json
+{
+  "mcpServers": {
+    "genclass": {
+      "command": "npx",
+      "args": [
+        "-y",
+        "@genclass/mcp@0.2.0"
+      ]
+    }
+  }
+}
+```
+
+### Cursor
+
+[![Add genclass MCP server to Cursor](https://cursor.com/deeplink/mcp-install-dark.png)](https://cursor.com/link/mcp/install?name=genclass&config=eyJjb21tYW5kIjoibnB4IiwiYXJncyI6WyIteSIsIkBnZW5jbGFzcy9tY3BAMC4yLjAiXX0%3D) or `cursor://anysphere.cursor-deeplink/mcp/install?name=genclass&config=eyJjb21tYW5kIjoibnB4IiwiYXJncyI6WyIteSIsIkBnZW5jbGFzcy9tY3BAMC4yLjAiXX0%3D`
+
+Or `.cursor/mcp.json` in the project (`~/.cursor/mcp.json` for all projects):
+
+```json
+{
+  "mcpServers": {
+    "genclass": {
+      "command": "npx",
+      "args": [
+        "-y",
+        "@genclass/mcp@0.2.0"
+      ]
+    }
+  }
+}
+```
+
+### VS Code
+
+[![Install in VS Code](https://img.shields.io/badge/VS_Code-VS_Code?style=flat-square&label=Install%20Server&color=0098FF)](https://vscode.dev/redirect/mcp/install?name=genclass&config=%7B%22command%22%3A%22npx%22%2C%22args%22%3A%5B%22-y%22%2C%22%40genclass%2Fmcp%400.2.0%22%5D%7D) or from a terminal:
+
+```bash
+code --add-mcp '{"name":"genclass","command":"npx","args":["-y","@genclass/mcp@0.2.0"]}'
+```
+
+Or `.mcp.json` at the workspace root (the portable format; `.vscode/mcp.json` takes the same entry under `servers`):
+
+```json
+{
+  "mcpServers": {
+    "genclass": {
+      "command": "npx",
+      "args": [
+        "-y",
+        "@genclass/mcp@0.2.0"
+      ]
+    }
+  }
+}
+```
+
+### Codex CLI
+
+```bash
+codex mcp add genclass -- npx -y @genclass/mcp@0.2.0
+```
+
+Or `~/.codex/config.toml` (`.codex/config.toml` in a trusted project). The first start downloads the package, so allow more than the default 10 seconds:
+
+```toml
+[mcp_servers.genclass]
+command = "npx"
+args = ["-y", "@genclass/mcp@0.2.0"]
+startup_timeout_sec = 30
+```
+
+### Gemini CLI
+
+```bash
+gemini mcp add genclass npx -- -y @genclass/mcp@0.2.0   # -s user: for all projects
+```
+
+Or `.gemini/settings.json` in the project (`~/.gemini/settings.json` for all projects):
+
+```json
+{
+  "mcpServers": {
+    "genclass": {
+      "command": "npx",
+      "args": [
+        "-y",
+        "@genclass/mcp@0.2.0"
+      ]
+    }
+  }
+}
+```
+
+### Windsurf (Devin Desktop)
+
+`~/.codeium/windsurf/mcp_config.json` (Windsurf), `~/.config/devin/mcp_config.json` (Devin Desktop's Cascade agent; `%APPDATA%\devin\mcp_config.json` on Windows):
+
+```json
+{
+  "mcpServers": {
+    "genclass": {
+      "command": "npx",
+      "args": [
+        "-y",
+        "@genclass/mcp@0.2.0"
+      ]
+    }
+  }
+}
+```
+
+Devin CLI and Devin Desktop's Devin Local agent:
+
+```bash
+devin mcp add -s user genclass -- npx -y @genclass/mcp@0.2.0
+```
+
+### Cline
+
+```bash
+cline mcp add genclass --yes -- npx -y @genclass/mcp@0.2.0
+```
+
+Or MCP Servers, Configure, Configure MCP Servers (`~/.cline/data/settings/cline_mcp_settings.json`):
+
+```json
+{
+  "mcpServers": {
+    "genclass": {
+      "command": "npx",
+      "args": [
+        "-y",
+        "@genclass/mcp@0.2.0"
+      ]
+    }
+  }
+}
+```
+
+### Goose
+
+`goose://extension?cmd=npx&arg=-y&arg=%40genclass%2Fmcp%400.2.0&id=genclass&name=genclass&description=Find%20race%20conditions%20by%20reordering%20responses%2C%20replay%20one%2C%20prove%20the%20fix` (open it to install), or `goose configure` (Add Extension, Command-line Extension, command `npx -y @genclass/mcp@0.2.0`), or `~/.config/goose/config.yaml`:
+
+```yaml
+extensions:
+  genclass:
+    type: stdio
+    name: genclass
+    enabled: true
+    cmd: npx
+    args: ["-y", "@genclass/mcp@0.2.0"]
+    env_keys: []
+    envs: {}
+    timeout: 300
+```
+
+### Zed
+
+`~/.config/zed/settings.json` (`.zed/settings.json` in the project), or Settings, AI, MCP Servers, Add Server:
+
+```json
+{
+  "context_servers": {
+    "genclass": {
+      "command": "npx",
+      "args": [
+        "-y",
+        "@genclass/mcp@0.2.0"
+      ]
+    }
+  }
+}
+```
+
+### JetBrains IDEs
+
+AI Assistant: Settings, Tools, AI Assistant, Model Context Protocol (MCP), Add, then this JSON. Junie: `.junie/mcp/mcp.json` in the project (`~/.junie/mcp/mcp.json` for all projects), same JSON:
+
+```json
+{
+  "mcpServers": {
+    "genclass": {
+      "command": "npx",
+      "args": [
+        "-y",
+        "@genclass/mcp@0.2.0"
+      ]
+    }
+  }
+}
+```
+
+### OpenCode
+
+`opencode.json` in the project (`~/.config/opencode/opencode.json` for all projects), or `opencode mcp add`:
+
+```json
+{
+  "$schema": "https://opencode.ai/config.json",
+  "mcp": {
+    "genclass": {
+      "type": "local",
+      "command": [
+        "npx",
+        "-y",
+        "@genclass/mcp@0.2.0"
+      ],
+      "enabled": true
+    }
+  }
+}
+```
+
+<!-- install:end -->
+
+Any other MCP client: a stdio server, command `npx`, arguments `-y @genclass/mcp@0.2.0`, no environment variables
+required.
+
+Then connect the app's development build (once). The agent link needs the newest runtime line, `@genclass/runtime`
+0.3.0-beta.1 or later: `npm install @genclass/runtime@beta` (a bare `npm install @genclass/runtime` gets npm's
+`latest`, the older 0.2.x, which has no agent entry):
+
+```ts
+import { GenClass } from "@genclass/runtime";
+import { connectAgent } from "@genclass/runtime/agent";
+
+const rt = GenClass.init();
+if (import.meta.env.DEV) connectAgent(rt); // Next.js: process.env.NODE_ENV === "development"
+```
+
+Load a page of the dev server and ask the agent for `genclass_status`. The agent can also ask `genclass_setup`, which
+reads your `package.json` and shows the lines for your framework.
+
+## What the agent does with it
+
+```
+you:    the search results are sometimes for an older query
+agent:  genclass_findings → f1 [stale-write] /search: the response to GET /api/search "?q=reac"
+        overwrote "search.results" after a newer GET /api/search had already written it
+        genclass_explain f1 → steps, delivery order, a replay, a regression test
+        genclass_replay arm f1 → (loads the page, types) → result: REPRODUCED
+        (fixes the handler to keep only the latest answer, adds the test)
+        genclass_replay arm f1 → result: not reproduced
+        genclass_explore start {slow_ms: 600} → 8 runs → report: no race
+```
+
+On a real page in headless Chromium (the package's end-to-end check), explore found that race in 5 of 6 reordered runs
+of a page that never showed it on the developer's fast backend, the generated test failed on the buggy page and passed
+on the fixed one, and explore on the fixed page reported nothing. Details: [docs/runtime/AGENT.md](https://github.com/genclass-dev/GenClass-lib/blob/main/docs/runtime/AGENT.md).
+
+## Tools
+
+| tool | |
+|---|---|
+| `genclass_status` | connected pages, counts of findings, explore and replay state |
+| `genclass_findings` | ranked, deduplicated findings: races, stale writes, errors, duplicate requests, model detections, visual checks |
+| `genclass_explain` | one finding in causal order, the recorded steps, the replay, a Playwright regression test |
+| `genclass_explore` | `start` / `report` / `stop`: find what depends on response order |
+| `genclass_replay` | `arm` / `result`: reproduce one finding exactly |
+| `genclass_analytics` | per-endpoint latency, error rates and request counts, learned relations and flows; production numbers from your GenClass dashboard |
+| `genclass_setup` | the lines to add for your framework, and the config lines for the client it runs in |
+| `genclass_scan` | `{url, phone?, hosted?}`: audit any page (the dev server or a site you do not own) with the 23 measured visual checks in headless Chromium: a score and each problem with its element, selector and a suggested CSS fix, plus the JSON report. Runs `npx @genclass/runtime@beta scan --json --local` (or the project's own runtime); needs Playwright's Chromium (`npx playwright install chromium`), or `hosted: true` for the genclass.dev page check (public pages only) |
+| `genclass_clear` | forget recorded runs and findings |
+
+## New findings without asking
+
+- **Channels** (Claude Code research preview): start Claude Code with
+  `claude --dangerously-load-development-channels server:genclass` and new findings arrive in the session as they
+  happen (`notifications/claude/channel`).
+- **Prompt hook** (part of the Claude Code plugin): `npx -y @genclass/mcp@0.2.0 init --hook` adds a `UserPromptSubmit`
+  hook to `.claude/settings.json`; each prompt then carries the findings that changed since the last one.
+
+## Environment
+
+| variable | default | |
+|---|---|---|
+| `GENCLASS_AGENT_PORT` | `47357` | the bridge's port (the page then needs `connectAgent(rt, { url })`) |
+| `GENCLASS_STATE_DIR` | `.genclass/agent` | where findings persist between sessions; `none` keeps them in memory |
+| `GENCLASS_DASHBOARD` | | your dashboard's private link, for `genclass_analytics` `production` (`sample` reads the public sample) |
+| `GENCLASS_REPORT` | | `on` (with `GENCLASS_DASHBOARD`), or a dashboard link or secret: mirror this server's log of the loop to that dashboard's Closed-loop development view (each finding, each time its evidence is read, each replay armed and its verdict, each regression test written, each explore report, each clear), which draws every issue's path (found, reproduced, fix proven, closed, or round again) with counts and lists the log. Ids, kinds, page paths, verdicts, counts and times only, never page text; off unless set ([AGENT.md section 4.5](https://github.com/genclass-dev/GenClass-lib/blob/main/docs/runtime/AGENT.md)) |
+| `GENCLASS_AGENT_ORIGINS` | | exact page origins allowed besides this machine's, e.g. `http://192.168.1.20:5173` (the page then needs `connectAgent(rt, { anyHost: true })`) |
+| `GENCLASS_TOKEN_DIR` | `~/.genclass` | where the bridge keeps its API token (mode 0600) for the hook and other sessions |
+
+## Security
+
+The bridge listens on 127.0.0.1 only and checks the `Host` header. Pages may talk to it only from your machine
+(`localhost`, `127.0.0.1`, `*.localhost`) or an origin you list in `GENCLASS_AGENT_ORIGINS` (a `*.test` or LAN dev host): a public
+website, a router page or a captive portal you visit cannot plant findings, and a page can only add to its own run.
+The agent API refuses browsers and needs a token only your user can read. Everything a page sends is validated,
+capped, stripped of invisible characters and shown to the agent as quoted data, never as instructions. Nothing leaves
+your machine (the exceptions are under Privacy). See section 6 of
+[AGENT.md](https://github.com/genclass-dev/GenClass-lib/blob/main/docs/runtime/AGENT.md).
+
+## Privacy
+
+The server collects nothing and sends nothing to GenClass or anyone else. Findings stay on your machine, in
+`.genclass/agent/` in the server's working directory (the project, for clients that start servers there; set
+`GENCLASS_STATE_DIR` for clients that do not, such as Claude Desktop), which the server gitignores, and in the bridge's memory; the bridge's token is in
+`~/.genclass`. The one request that leaves the machine is `genclass_analytics` `{source: "production"}`, which reads
+your own GenClass dashboard when you set `GENCLASS_DASHBOARD` to its private link. `genclass_scan` loads the page the
+agent names (that is the page's own traffic) in a local browser; only with `hosted: true` is the URL sent to the
+genclass.dev page check, and when the project has no `@genclass/runtime` with `scan`, npx downloads it from npm. With `GENCLASS_REPORT` set (off by
+default) the server also mirrors its log of the loop to that dashboard, in small batches: the id, kind and page path of
+each finding, when its evidence was read, each replay armed and its verdict, when a regression test was written, each
+explore report (page loads compared, races found) and each clear, so the dashboard's Closed-loop development view
+draws every issue's path (found, reproduced, fix proven, closed, or round again) and lists what the agent did; never a
+title, an evidence line, a snapshot or any page text, and nothing it sends feeds a decision. The runtime in your app has its
+own disclosed diagnostics ([PRIVACY.md](https://github.com/genclass-dev/GenClass-lib/blob/main/PRIVACY.md)), which
+`GenClass.init({ telemetry: false })` turns off; the agent link is not part of them.
+
+## License
+
+Apache-2.0