Install & connect
To use React Native MCP you need the MCP server, client configuration, app setup, and native tools (idb / adb).
1. Install the MCP server
Global install (npm, pnpm, bun, yarn, deno):
Run without installing (npx, pnpx, bunx, etc.):
Cursor, Claude, and Copilot configs typically use the run-without-install approach.
2. Register the server in your client
Register the MCP server in your AI client.
- Cursor: See Using MCP — Cursor
- Claude Desktop: See Using MCP — Claude Desktop
- GitHub Copilot CLI: See Using MCP — Copilot CLI
3. React Native app setup
The app must use the Babel preset and enable the MCP runtime in the app entry so the MCP server can communicate with it. For console/network tools, run Metro as usual (the MCP server connects to Metro’s debugger; no Metro config change is required).
Babel preset
Add the preset in babel.config.js (AppRegistry wrapping, testID injection):
To apply only in development:
Render highlight (optional)
Visual re-render highlighting draws colored overlays on components when they re-render. You can enable it at app load via the Babel preset option. Default style is 'react-mcp' (cyan #61dafb, matches DevTools icon).
Example:
4. Native tools (idb / adb)
Tap, swipe, screenshots, etc. use idb (iOS) and adb (Android). You must install them.
Android — adb
- Included with Android Studio
- Standalone:
brew install --cask android-platform-tools(macOS) - Verify:
adb devices
iOS simulator — idb
Install idb (iOS Development Bridge):
Verify: idb list-targets
idb is macOS-only and supports simulators. Physical devices need separate setup.
5. Verify
- Start Metro (
bun run startornpm start) - Run the app in the iOS simulator or Android emulator
- In Cursor (or your client), confirm MCP is connected and tools like snapshot and tap work
If something fails, see the troubleshooting section in Using MCP or the repo issues.