VarwoWant to connect REA to Claude Code? Start by previewing the client-specific setup, then verify that Claude can see the MCP server before beginning an investigation. This guide covers Claude Code; it does not treat the browser chat app or Claude Desktop as the same integration.
Open REA's installation guide · Start with a preview · Verify the connection
Independent guide, unaffiliated with REA or Anthropic. Documentation checked October 23, 2026. Commands are reviewed examples, not a setup executed on this site.
Using Codex or Cursor instead? The REA MCP guide covers selecting a client and checking the connection layers. This page stays focused on Claude Code.
What REA adds to Claude Code
REA exposes inspection workflows to a configured agent. Claude Code supplies the agent environment; the analysis capability and its prerequisites depend on your target and tools. Installing an MCP server does not by itself create model access or an external analysis-tool license.
If you are still choosing what to inspect, start with the REA project overview. For the authoritative client details, use REA's client configuration documentation.
1. Preview setup for Claude Code
First confirm that your Node/npm environment meets REA's current requirements and that Claude Code is installed. In a local terminal, review the plan without applying it:
npx rea-agents@latest setup --client claude_code --dry-runThe package runner can still download software. The dry run is for the setup plan, not a promise of zero network activity. Review the resolved version and the exact paths named in the plan.
When you are ready to apply those changes, run:
npx rea-agents@latest setup --client claude_codeThe upstream installation guide documents the client selector, review step, and restart. Do not select every detected client unless you intend to configure all of them.
Decide the scope before applying
The default Claude Code setup described by REA is client-wide. If you only want one project or a separate profile to discover the integration, follow the installation guide's scoped alternatives before applying the default setup. Do not assume it affects only the terminal's current folder.
2. Restart the selected Claude Code session
After setup completes, restart the intended client or profile. Keep its configuration context consistent between setup and verification. A second session using a different profile may not have the same registration.
3. Check registration and readiness
REA's documented client check can be run from your terminal:
npx rea-agents@latest doctor --client claude_code --skill --jsonInspect the result rather than treating an exit message as proof that every analysis engine works. Also list Claude Code's MCP connections:
claude mcp listUse the client configuration reference and scoped readiness instructions to interpret failures. Keep any diagnostic report local until you have removed private paths and data you do not intend to share.
4. Give Claude one question with a clear check
Here is an original prompt for software you own or have permission to examine. Replace the target and feature; do not claim the example has already been run:
Use REA to inspect my local demo app's search behavior.
First identify the target version and the relevant analysis route.
Explain whether matching ignores letter case and whitespace.
Show the evidence for each conclusion and list any uncertainty.
Check three small inputs: "Tea", "tea", and " tea ".
Do not modify the original app or access unrelated files.
Deliver a short evidence table and a suggested next step.Inspect the evidence yourself. If you later ask for an implementation, define the required behavior first and check it against the same inputs. A plausible final explanation is not a substitute for checking the produced files and behavior.
Match the analysis route to the target
| Target | Preparation |
|---|---|
| JavaScript/Electron application | A local application folder or package and a clearly identified build |
| Native executable | A supported provider/engine configuration and the correct target artifact |
| A website you control | A page, reproduction steps, and the browser connection required by the workflow |
Consult the upstream target-specific guide before promising that an unfamiliar file format is supported. This page does not provide a compatibility guarantee for every APK, binary, or application.
Troubleshooting
| Problem | Next check |
|---|---|
| REA is absent in Claude | Setup used claude_code, not another client; restart and inspect the active profile |
| MCP appears but calls fail | Read scoped diagnostics; check the runtime and exact error |
| Native provider is missing | Configure an appropriate engine using upstream instructions |
| A skill is present but tools are missing | Verify MCP registration separately; instructions and a running server are different things |
| It works in one project only | Check the intended profile/scope before re-running broad setup |
Record the failing command and resolved package version before making changes. Avoid deleting unrelated MCP configuration as a troubleshooting shortcut.
Frequently asked questions
Does this work in Claude Desktop too?
REA documents multiple clients, but Desktop and Code have distinct setup and configuration. Follow the guide for the client you actually use; these commands target Claude Code.
Do I need to paste a Claude API key into this page?
No. This page has no key field and performs no setup. Use your existing authorized Claude environment and the upstream registration process.
Is there a one-click command generator here?
The commands above are static, reviewable examples. This page does not run installers. A future interface can help select commands, but it must preserve the setup review step and clearly state the chosen client and scope.
How do I update it?
Use REA's current maintenance instructions and review the changed setup plan. Record the version used for your investigation so a future update does not silently change the basis of a reported result.