frontend-mcp

# Frontend Perception Engine (CRG as Optional Library) This project implements a frontend navigation layer where: - Browser Use stays the browser automation engine. - Code Review Graph (CRG) is used only as an optional knowledge source. - Browser execution continues even when CRG is unavailable. ## Architecture ```text Cursor / Claude ↓ Our MCP ↓ Frontend Navigation Layer ↓ Browser Use ↓ Browser ``` CRG is integrated behind `ICodeGraph`, so it can be replaced later by another backend such as `FrontendInteractionGraph` without changing Browser Use orchestration. ## Dependency Integration CRG is integrated as a dependency (not forked, not modified): - `code-review-graph>=2.3.6` - `browser-use>=0.13.3` Install: ```bash pip install -e . ``` ## Frontend Perception MCP (No LLM in Server) The MCP server is deterministic runtime only (browser observation + actions + verify). Your coding agent (Cursor/Claude/Codex) remains the brain. ### Install ```bash pip install frontend-mcp ``` Upgrade: ```bash pip install -U frontend-mcp ``` Full setup for **Cursor / Claude Code / Codex / OpenCode** (MCP config + optional rules): → [`docs/INSTALL.md`](docs/INSTALL.md) Optional install helper (progress + Chromium): ```bash frontend-mcp-install --with-browser # or: uvx --from frontend-mcp frontend-mcp-install --with-browser ``` Legacy name still works (thin reverse alias → same `frontend-mcp`): ```bash pip install frontend-perception-engine ``` **Do not mix** PyPI installs with `pip install -e .` in this repo; editable installs can leave broken metadata that blocks upgrades. Use one or the other. Development install from this repo: ```bash pip install -e . # or: python -m navigation.cli.install --editable . ``` ### Run MCP server Using module entrypoint: ```bash python -m navigation.mcp ``` Using script entrypoint: ```bash frontend-perception-mcp ``` …