About GenClass
GenClass is an MCP server that helps coding agents investigate race conditions in locally running web apps. It records request and response behavior, explores reordered responses, and replays findings to check whether a fix works.
Key features
- 01Record clicks, requests, responses, and errors
- 02Detect stale writes and duplicate submissions
- 03Explore behavior under reordered responses
- 04Replay a finding to verify a fix
- 05Generate Playwright regression tests
- 06Inspect endpoint latency and error rates
Use cases
- 01Investigate search results overwritten by stale responses
- 02Reproduce a race before and after changing a handler
- 03Create a regression test from a recorded finding
- 04Compare endpoint behavior under varied response order
MCP support
GenClass runs as an MCP server for coding agents and exposes tools to inspect findings, explore response order, replay bugs, and generate tests. It connects to a development page through `@genclass/runtime`'s agent link.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
Tools
9Saved tool list · updated today
This tool takes no parameters.
Details
From the project README@genclass/mcp
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'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_exploreruns 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_replaydelivers the exact order that produced a bug again, before your fix (reproduced) and after it (not reproduced), andgenclass_explainwrites 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).
Install
Pick your client. Every block pins this release, so the client starts exactly this version;
npx -y @genclass/[email protected] config <client> prints the same lines, and genclass_setup prints the block for the
client it runs in.
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):
claude mcp add --scope project genclass -- npx -y @genclass/[email protected]
# or: npx -y @genclass/[email protected] 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):
{
"mcpServers": {
"genclass": {
"command": "npx",
"args": [
"-y",
"@genclass/[email protected]"
]
}
}
}
Cursor
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):
{
"mcpServers": {
"genclass": {
"command": "npx",
"args": [
"-y",
"@genclass/[email protected]"
]
}
}
}
VS Code
code --add-mcp '{"name":"genclass","command":"npx","args":["-y","@genclass/[email protected]"]}'
Or .mcp.json at the workspace root (the portable format; .vscode/mcp.json takes the same entry under servers):
{
"mcpServers": {
"genclass": {
"command": "npx",
"args": [
"-y",
"@genclass/[email protected]"
]
}
}
}
Codex CLI
codex mcp add genclass -- npx -y @genclass/[email protected]
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:
[mcp_servers.genclass]
command = "npx"
args = ["-y", "@genclass/[email protected]"]
startup_timeout_sec = 30
Gemini CLI
gemini mcp add genclass npx -- -y @genclass/[email protected] # -s user: for all projects
Or .gemini/settings.json in the project (~/.gemini/settings.json for all projects):
{
"mcpServers": {
"genclass": {
"command": "npx",
"args": [
"-y",
"@genclass/[email protected]"
]
}
}
}
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):
{
"mcpServers": {
"genclass": {
"command": "npx",
"args": [
"-y",
"@genclass/[email protected]"
]
}
}
}
Devin CLI and Devin Desktop's Devin Local agent:
devin mcp add -s user genclass -- npx -y @genclass/[email protected]
Cline
cline mcp add genclass --yes -- npx -y @genclass/[email protected]
Or MCP Servers, Configure, Configure MCP Servers (~/.cline/data/settings/cline_mcp_settings.json):
{
"mcpServers": {
"genclass": {
"command": "npx",
"args": [
"-y",
"@genclass/[email protected]"
]
}
}
}
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/[email protected]), or ~/.config/goose/config.yaml:
extensions:
genclass:
type: stdio
name: genclass
enabled: true
cmd: npx
args: ["-y", "@genclass/[email protected]"]
env_keys: []
envs: {}
timeout: 300
Zed
~/.config/zed/settings.json (.zed/settings.json in the project), or Settings, AI, MCP Servers, Add Server:
{
"context_servers": {
"genclass": {
"command": "npx",
"args": [
"-y",
"@genclass/[email protected]"
]
}
}
}
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:
{
"mcpServers": {
"genclass": {
"command": "npx",
"args": [
"-y",
"@genclass/[email protected]"
]
}
}
}
OpenCode
opencode.json in the project (~/.config/opencode/opencode.json for all projects), or opencode mcp add:
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"genclass": {
"type": "local",
"command": [
"npx",
"-y",
"@genclass/[email protected]"
],
"enabled": true
}
}
}
Any other MCP client: a stdio server, command npx, arguments -y @genclass/[email protected], 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):
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.
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:genclassand new findings arrive in the session as they happen (notifications/claude/channel). - Prompt hook (part of the Claude Code plugin):
npx -y @genclass/[email protected] init --hookadds aUserPromptSubmithook 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) | |
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.
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), which
GenClass.init({ telemetry: false }) turns off; the agent link is not part of them.
License
Apache-2.0
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.