About Code Reaper
CodeReaper is an MCP tool for Cursor that uses browser exploration and V8 coverage to locate unused JavaScript and help remove it. It provides risk scores, patch generation, and optional verification for developers cleaning up web projects.
Key features
- 01Autonomous browser UI exploration
- 02V8 coverage analysis
- 03Dead-code risk scoring
- 04Patch generation and verification
- 05Patch rollback support
Use cases
- 01Find unused JavaScript on a local site
- 02Review suggested dead-code removals
- 03Verify or roll back code patches
MCP support
CodeReaper integrates with Cursor as an MCP tool. It exposes tools for scanning sites, analyzing dead code, generating and applying patches, verification, and rollback.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMECodeReaper
CodeReaper is an AI-driven MCP tool for Cursor that finds and removes dead JavaScript by exploring real UIs and capturing V8 coverage.
Key Features
- Autonomous UI exploration via the Index browser agent
- V8 precise coverage to identify zero-execution functions
- Risk scoring and removal recommendations
- Patch generation and optional verification replay
- MCP integration for Cursor workflows
Quick Install
pip install codereaper
playwright install chromium
codereaper
When you first run codereaper, it prompts for your Gemini API key and saves it in your global ~/.cursor/mcp.json so Cursor can invoke it later.
Alternative Install
# pipx
pipx run codereaper
Prerequisites
- Python 3.11+
- Playwright Chromium (installed via
playwright install chromium) - A Gemini API key (or OpenAI / Anthropic if you change providers)
Quick Start
- Install and run
codereaper(it updates~/.cursor/mcp.json) - Restart Cursor
- Ask the assistant:
"Find dead JavaScript code on http://localhost:3000"
Usage
Command:
codereaper
Example scan with local source mapping:
"Find dead code on http://localhost:3000, source is in ./test_site"
MCP Tools
| Tool | Description |
|---|---|
find_dead_code | Full pipeline: scan + analyze. Returns dead-code report with file paths, line numbers, risk scores, and removal recommendations. |
scan_website | Scan only (no analysis). Returns scan_id for later use. |
analyze_dead_code | Analyze a completed scan. Takes scan_id. |
generate_patches | Generate unified diffs to remove dead code (conservative / balanced / aggressive). |
get_patch_diff | Retrieve the combined diff for a patch. |
apply_patch | Apply a patch to source files (stores snapshots for rollback). |
verify_patch | Re-run the browser agent to check for regressions after patching. |
rollback_patch | Restore original files from pre-patch snapshots. |
list_scans | List recent scans. |
get_scan_status | Get detailed status of a scan. |
Troubleshooting
- If the browser doesn’t open, install Chromium:
playwright install chromium - If the scan fails with key errors, ensure
GEMINI_API_KEYexists in~/.cursor/mcp.json - If local pages don’t load, confirm your dev server is running and reachable
- If Gemini rate limits hit, retry after the quota window resets
Update
- 02-09-2026: v0.2.3 release
Issues & Feedback
Open an issue with steps to reproduce and logs if possible. Feedback and suggestions are welcome.
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.