React debugging in Chrome DevTools: a 5-view panel (Dashboard/Profiler/State/Effects/Settings) with render+memory pro...
Copy the install, test the workflow, then decide if it earns a permanent slot.
The signal is softer here. Treat it like a pattern source unless it solves a very specific gap.
Copy the install, test the workflow, then decide if it earns a permanent slot.
You can test this quickly and remove it cleanly if it misses.
GitHub health unknown. no security policy. 0 open issues make this testable, but not something to trust blind.
AI Agent
Universal
Model
Multiple
Fastest way to find out if react-debugger-extension belongs in your setup.
Copy the install command, run a real test, and back it out cleanly if it slows you down.
claude mcp add react-debugger-extension -- npx react-debugger-extensionRun this first. You will know quickly if the workflow earns a permanent slot.
claude mcp remove react-debugger-extensionNo messy cleanup loop. If it misses, remove it and keep moving.
Install Location
~/ └─ .claude.json └─ mcp_servers/ └─ react-debugger-extension ← registers here
React debugging in Chrome DevTools: a 5-view panel (Dashboard/Profiler/State/Effects/Settings) with render+memory profiling, issue detectors, a Redux inspector, AI analysis, and an MCP server for coding agents.
Source: GitHub repository
Source check: No source check recorded
Repository state: Not marked archived
Honeystax upvotes are community interest signals, not star ratings. GitHub stars and repository health are source measurements; editorial risk and trial-cost notes are Honeystax analysis.