docs: add Continue.dev MCP snippet to MCP_USAGE.md

[Kunall7890]

Linked issue

Closes #5

Type of change

• Bug fix (non-breaking change that fixes an issue)
• Feature (non-breaking change that adds functionality)
• Performance improvement
• Documentation only
• Refactor (no behavior change)
• Test additions or fixes
• Chore (tooling, deps, build config)

What changed

Added a ## Continue section to cli/docs/MCP_USAGE.md so that Continue.dev users can connect the react-debugger MCP server without having to figure out the config format themselves. The section covers three setup options (global YAML, workspace-scoped YAML, and legacy JSON) plus step-by-step verification instructions including how to call get_fiber_node from the Continue Agent panel.

Testing notes

Verified the snippet is present in the file:

$ node -e "
const fs = require('fs');
const content = fs.readFileSync('cli/docs/MCP_USAGE.md', 'utf8');
if (content.includes('mcpServers') && content.includes('react-debugger')) {
console.log('OK - snippet found in file');
} else {
console.log('ERROR - snippet missing');
}
"

OK - snippet found in file

Note: Full tool verification requires the mcp subcommand to be published to npm. The doc already carries a Preview/unreleased warning for this reason.

Claim confirmation

• I starred the repo ⭐
• I commented I'll take this on the issue before starting work.

Checklist

• npm run test:run passes locally (docs-only change, no logic affected)
• npm run build succeeds locally (docs-only change, no logic affected)
• CHANGELOG.md entry added — skipped (docs-only PR)
• PR title follows Conventional Commits: docs: add Continue.dev MCP snippet to MCP_USAGE.md
• No new runtime dependencies added

Screenshots / GIFs

Screenshot of Continue Agent showing react-debugger tools loaded will be added once @nhonh/react-debugger@latest mcp is published to npm (currently preview/unreleased per the doc header).

Additional notes

Continue.dev recently migrated from config.json to config.yaml as its preferred format. This PR covers both formats so existing users on either version are unblocked. The workspace-scoped YAML option is also included for teams who want per-project MCP configuration.

[gemini-code-assist]

Code Review

This pull request adds documentation for integrating the React Debugger MCP server with the Continue AI coding assistant, covering global, workspace-scoped, and legacy configuration options. The review feedback points out two issues: the workspace-scoped YAML configuration contains incorrect top-level wrappers and metadata, and the verification instructions at the end of the file are cut off and need to be completed.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[gemini-code-assist]

In Continue, individual files placed in the .continue/mcpServers/ directory represent a single MCP server configuration. Therefore, they should not contain the top-level mcpServers list wrapper or metadata like version and schema. Instead, the file should directly define the server's configuration properties (like command and args).

Suggested change

	name: react-debugger
	version: 1.0.0
	schema: v1
	mcpServers:
	- name: react-debugger
	command: npx
	args:
	- -y
	- "@nhonh/react-debugger@latest"
	- mcp
	command: npx
	args:
	- -y
	- "@nhonh/react-debugger@latest"
	- mcp

[gemini-code-assist]

The instruction on this line is cut off and ends abruptly. Please complete the sentence to guide the user on what they should type in the Continue chat panel to verify the tools.

Suggested change

	3. In the Continue chat panel, type:
	3. In the Continue chat panel, ask a question that triggers the tool, for example: "Get the fiber node of the root element".

[hoainho]

Hey @Kunall7890 — welcome back for round 2! 🎉

The CI is showing a false-negative on the Star Check (read-replica lag — your star is definitely there, verified in the stargazer list, but the API can't see it for ~30s+ after a new push). I've applied the pre-star-rule label to bypass that and re-run CI. No action needed on your side.

What I love about this PR

• You read my follow-up suggestions from ux: replace alert() validation with inline error messages in ReduxTab #58 and picked the most actionable one. That's exactly the contributor loop I was hoping for — small, scoped, immediately useful.
• 3 config options + verify steps. Most contributors stop at "here's a YAML snippet"; you went the extra mile to cover workspace-scoped and legacy JSON paths, plus a click-by-click verification recipe for get_fiber_node. That's the kind of thing that prevents a GitHub issue three months from now.
• 57+ / 1- in 1 file. Minimal, focused, no drive-by refactors. The kind of diff I can read in 30 seconds and merge with confidence.
• Closes [Easy] Add docs/MCP_USAGE.md mcp.json snippet for Continue.dev #5 properly with the Closes #5 trailer — auto-closes the issue on merge, no manual bookkeeping.
• Hits on launch day 🚀 — Sat 2026-06-07 is the planned launch window for the v2.0.3 release, so this lands in the launch-day changelog.

Two small suggestions for future contributions (no change required here)

These are nits I noticed in passing — your PR is already great, take them as future-project ideas:

1. Continue.dev's actual MCP config format may want a type: stdio field for newer Continue versions. If a user reports "tools don't load," that's the first thing to check. You can verify by looking at Continue's actual config schema at https://docs.continue.dev/customize/deep-dives/configuration.
2. @nhonh/react-debugger@latest is correct, but a one-liner about what @latest resolves to (currently v2.0.3 at the time of this PR) would help users understand the version they're getting.

Build+Test note (FYI, not a blocker)

The Build+Test job had 2 pre-existing test failures (test debt: emoji assertions in UIStateTab.test.tsx that were written for v1.x and not updated when v2.0.0 removed the emojis). The workflow auto-reports these as pass with a warning. If you want a "real first PR" of test cleanup, those are in CONTRIBUTING.md's "Known test debt" section — but they're not what I'd open with. Issue #9 (zod schema unit tests) is the cleaner entry.

Merging now

Going to squash-merge once CI re-runs (should be ~30s). Issue #5 will auto-close. Welcome back to the contributors list, twice in a row! 🎉

— Hoài