React Native Debug MCP
Enables AI agents to inspect, log, and control React Native apps on Android emulators or iOS simulators, including UI tree, tap, scroll, and hot reload.
README
React Native Debug MCP
Let AI agents see, understand, and interact with your React Native app running on Android emulator or iOS simulator — through a single MCP server.
Point your MCP client at this server and an agent can connect to your app, read logs, inspect the UI, tap buttons, type text, scroll, take screenshots, and reload — all without leaving the conversation.
https://github.com/user-attachments/assets/0d5a5235-9c67-4d79-b30f-de0132be06cd
Features
Connect and Control
- Android + iOS — one server handles both platforms
- Multi-session — debug multiple devices or apps at the same time
- Hot reload — reload your app instantly via Metro; automatic fallback to native reload when Metro is unavailable
See What's Happening
- Live logs — stream device logs in real time (Android
logcat/ iOSsimctl) - Error filtering — surface only errors so the agent focuses on what matters
- Network inspector — capture HTTP requests and responses with cursor-based polling
- Screenshots — capture the screen as a PNG image the agent can see inline
Understand the UI
- UI tree — get the full view hierarchy (Android UIAutomator / iOS WebDriverAgent)
- Visible elements — list what's on screen with text, bounds, and testIDs
- Screen context — get the current activity/screen name so the agent knows where it is
Interact with the App
- Tap, scroll, type, back — drive the app like a real user
- Tap by testID — target elements by
testIDinstead of fragile coordinates - testID discovery — list all testIDs on screen, search by exact or partial match
- testID remediation — when a testID is missing, the agent gets a ready-to-paste code fix and can reload to verify
Requirements
- Node.js 20+
- Android SDK /
adbonPATH - Xcode command line tools (
xcrun) and iOS Simulator (for iOS) - React Native app running on emulator/simulator
- Metro running (default:
8081) - WebDriverAgent reachable for iOS (default:
http://127.0.0.1:8100)
Quickstart
Option A: Global install (use from any project)
npm install -g rn-debug-mcp
Add to your MCP client config:
{
"mcpServers": {
"rn-debug": {
"command": "npx",
"args": ["-y", "rn-debug-mcp"],
"env": {
"WDA_BASE_URL": "http://127.0.0.1:8100"
}
}
}
}
Option B: Local dev dependency (per-project)
npm install -D rn-debug-mcp
npm run build
Add to your MCP client config:
{
"mcpServers": {
"rn-debug": {
"command": "node",
"args": ["/ABS/PATH/TO/node_modules/rn-debug-mcp/dist/src/index.js"],
"env": {
"WDA_BASE_URL": "http://127.0.0.1:8100"
}
}
}
}
iOS Support
iOS works automatically on first connect_app({ platform: "ios" }). WebDriverAgent sources are cloned and built transparently if not already present.
- If WDA is already running on
:8100(or the configuredWDA_BASE_URL), the install/build is skipped entirely. - Set
WDA_NO_AUTO_INSTALL=1to disable automatic installation and require manual setup. - Set
WDA_BASE_URLto point to an externally managed WebDriverAgent instance.
Manual / Advanced Setup
Install WDA sources manually:
npx --no-install rndmcp install wda
Run WDA standalone:
npm run ios:wda
Optional overrides:
WDA_PROJECT_PATH="/abs/path/to/WebDriverAgent.xcodeproj" npm run ios:wda
WDA_DEVICE_ID="<booted-simulator-udid>" npm run ios:wda
WDA_DESTINATION='platform=iOS Simulator,name=iPhone 16' npm run ios:wda
Tools
Session and Connection
connect_app({ platform?, deviceId?, metroPort? })list_sessions({})set_active_session({ sessionId })close_session({ sessionId })get_connection_status({ sessionId? })disconnect_app({ sessionId? })reload_app({ sessionId? })
Logs, Errors, and Network
get_logs({ sessionId?, sinceCursor?, limit?, levels?, tags?, sources? })get_errors({ sessionId?, sinceCursor?, limit?, levels?, tags?, sources? })get_network_requests({ sessionId?, sinceCursor?, limit?, phases?, methods?, statuses?, urlContains?, sources? })
UI and Context
get_screen_context({ sessionId? })get_ui_tree({ sessionId?, maxDepth?, maxNodes? })get_visible_elements({ sessionId?, maxDepth?, maxNodes?, limit?, clickableOnly?, includeTextless?, skipVisibilityCheck?, testId?, testIdMatch? })get_screen_test_ids({ sessionId?, maxDepth?, maxNodes?, limit?, includeNonClickable?, includeInvisible? })get_elements_by_test_id({ sessionId?, testId, maxDepth?, maxNodes?, limit?, clickableOnly?, includeTextless?, skipVisibilityCheck?, testIdMatch? })get_test_id_remediation_plan({ sessionId?, desiredAction, desiredTestId?, matchMode? })
Interaction
tap({ sessionId?, x, y })tap_element({ sessionId?, elementId, maxDepth?, maxNodes? })type_text({ sessionId?, text, submit? })press_back({ sessionId? })scroll({ sessionId?, direction, distanceRatio?, durationMs? })take_screenshot({ sessionId? })
Recommended Agent Flow (testID-first)
get_elements_by_test_idwithtestIdMatch: "exact".- If unknown IDs, call
get_screen_test_ids. - If empty, retry
get_elements_by_test_idwithtestIdMatch: "contains". - If still empty:
- call
get_screen_context - call
get_test_id_remediation_plan - patch app code with suggested testID
- call
reload_app - retry exact testID lookup
- call
- If unresolved:
- try
tap_elementfrom visible candidates - fallback to
tap({ x, y }) - use
scroll,press_back, andtype_textfor navigation/input
- try
testID naming convention: screen.element.action (example: checkout.submit.button).
Platform Notes
connect_appdefaults toplatform: "android"for backward compatibility.- iOS tap coordinates use point space (WDA coordinates), not screenshot pixels.
- If converting screenshot pixels to iOS points:
pointX = round(pixelX / scaleFactor)pointY = round(pixelY / scaleFactor)
get_elements_by_test_iddefaults:skipVisibilityCheck: true(RN-friendly)clickableOnly: false(broader matching)
get_screen_test_idsdefault:includeInvisible: true.
Development
npm run typecheck
npm test
CLI usage:
rndmcp # Start MCP server over stdio
rndmcp install wda # Clone WebDriverAgent into this package
Troubleshooting
- iOS connect reports missing WDA:
- WDA is auto-installed on first
connect_app({ platform: "ios" })unlessWDA_NO_AUTO_INSTALL=1 - set
WDA_BASE_URLto an already running WDA, or - run
rndmcp install wdaand thennpm run ios:wdafor manual setup
- WDA is auto-installed on first
- Reload fallbacks:
- Android: ADB broadcast/key events
- iOS simulator:
Cmd+Rkeyboard trigger viaosascript
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.