What do Claude REA and REA Claude mean?
These searches usually mean connecting Claude to REA’s tools. This guide uses the local MCP integration in Claude Code. Claude in a browser, Claude Code and Claude Desktop have different configuration surfaces; identify your client first.
Preview, then configure Claude Code
Use a supported Node runtime, then run the commands in order. The dry run displays a plan without writing configuration. The next setup command enters the approval flow. Review the selected client, paths and optional installations before approving changes.
node --version
npm --version
npx rea-agents@6.5.0 setup --client claude_code --dry-run
npx rea-agents@6.5.0 setup --client claude_code
npx rea-agents@6.5.0 doctor --client claude_code --jsonConfiguration scope and restart
Default Claude Code registration uses mcpServers.rea in ~/.claude.json, with workflow instructions under ~/.claude/skills. CLAUDE_CONFIG_DIR changes the profile paths. The default registration is client-wide, not project isolation. Follow the upstream local-scope procedure when you need one-project discovery, then restart the appropriate Claude Code session.
Verify tool discovery before target analysis
Doctor checks the selected configuration. Next, confirm REA’s tools are visible in Claude Code. On a small JavaScript directory you own, ask: “Find the command-generation entry point, cite file locations, and separate observations from inferences.” Inspect the cited evidence rather than treating a fluent explanation as proof.
If you meant Claude Desktop
Do not copy Claude Code configuration into Desktop. Use interactive setup to select the correct client and fully quit Desktop before changing its configuration. Windows MSIX installations have additional path rules; use the official client reference and diagnostics.
Official client configuration reference
Continue your investigation
- Build a setup plan for your environment
- Inspect the reproducible case study
- Troubleshoot by symptom
- Browse all field guides