rn-devtools-hub

The agent runtime for React Native. Your agent sees the app the way React sees it, knows which file produced each element, acts without coordinates, and proves that it works. Zero dependencies, inert in production, your data stays on your machine.

GitHub Integration guide Protocol (reference) llms.txt

Getting started in 3 steps

# 1. In your project (devDependency)
npm install --save-dev rn-devtools-hub

# 2. The hub, from the project root (Bun or Node 20+)
npx rn-devtools-hub

# 3. In the app: 3 lines of glue, see the integration guide

From Claude Code

/plugin marketplace add rn-devtools-hub/rn-devtools-hub
/plugin install rn-devtools-hub

That registers the MCP server and installs a skill that teaches an agent to chain its tools. Clients that speak only stdio use npx rn-devtools-hub mcp, which bridges to the hub and starts it on demand.

Screenshots

Overview panel — Overview: requests, error rate, JS thread lag, connection and device

Network panel — Network: colored methods, foldable JSON, copy as cURL, redacted secrets

Mirror panel — Mirror: live device screen over adb with tap, swipe and keys

What being inside the runtime buys you

The SDK runs inside your app's JavaScript runtime. An accessibility-driven tool sees what the OS exposes; a WebDriver-driven one sees a black box. Neither can read a component's props, call a handler, intercept a request or write to a store. Everything below follows from that position.

The agent can	Because
Find an element by role and accessible name, then act on it	Actions go through the app's own props, not through pixels
Get the file and line behind each element	The location lives in React's dev bookkeeping, symbolicated against Metro
Prove a step without a screenshot	A screenshot cannot show a request that failed silently
Tell a stale native build from a code problem	Only the runtime knows what the binary actually is
Freeze the clock and the network	Date and fetch are in the runtime
Put the app in an exact state without walking ten screens	Stores are reachable directly
Explain a visual regression, not just score it	The changed region maps back to the component that owns it

For AI agents

The llms.txt file sums it all up. The step-by-step integration procedure, the pitfalls and the validation are in AGENTS.md. The hub exposes a local MCP server to query the running app.