![\"rn-devtools-hub\"](\"assets/logo.svg\"){kind=logo}
\n\n \n
\n The agent runtime for React Native. Your agent sees the app the way React\n sees it, knows which file produced each element, acts without coordinates,\n and proves that it works. Zero dependencies, no telemetry or usage\n counting, with a local hub and SDK.\n
\n\n\n Documentation ·\n Quick start ·\n Integration ·\n Contributing\n
\n\n## Use it from an agent\n\nBoth plugins install the MCP server plus a skill that teaches the agent to\nchain its tools: check the project context before debugging anything that\nlooks impossible, prove results with assertions instead of screenshots, wait\non events instead of sleeping, and read an element's source instead of\ngrepping the repository.\n\n**Claude Code**\n\n```\n/plugin marketplace add rn-devtools-hub/rn-devtools-hub\n/plugin install rn-devtools-hub\n```\n\n**Codex**\n\n```\ncodex plugin marketplace add rn-devtools-hub/rn-devtools-hub\ncodex plugin add rn-devtools-hub\n```\n\nThen start the hub at the root of your app, which is what the agent talks\nto:\n\n```\nnpx rn-devtools-hub\n```\n\nRegistering the server by hand works too. Claude Code:\n\n```\nclaude mcp add rn-devtools --transport http http://127.0.0.1:8973/mcp\n```\n\nCodex, in `~/.codex/config.toml`:\n\n```toml\n[mcp_servers.rn-devtools]\nurl = \"http://127.0.0.1:8973/mcp\"\n```\n\n**Cursor** has no marketplace, so it is two files in your own project.\nDeclare the server in `.cursor/mcp.json`:\n\n```json\n{\n \"mcpServers\": {\n \"rn-devtools\": { \"type\": \"http\", \"url\": \"http://127.0.0.1:8973/mcp\" }\n }\n}\n```\n\nAnd copy the rule, which is the Cursor equivalent of the skill:\n\n```bash\nmkdir -p .cursor/rules\ncp node_modules/rn-devtools-hub/templates/cursor-rule.mdc \\\n .cursor/rules/rn-devtools-hub.mdc\n```\n\nIt ships with `alwaysApply: false`, so Cursor pulls it in when the task\nmatches instead of paying for it on every request.\n\nFor any other agent, the skill on its own comes from the\n[skills.sh](https://skills.sh) registry:\n\n```\nnpx skills add rn-devtools-hub/rn-devtools-hub\n```\n\nIt writes `.agents/skills/rn-devtools-hub` and links it into whichever\nagents it detects, from Gemini CLI and Copilot to Windsurf and Zed. This\ninstalls the skill only, so register the server as above and start the hub\nto give the agent something to talk to.\n\nAny client that speaks only stdio uses `npx rn-devtools-hub mcp`, which\nbridges to the hub and starts it on demand.\n\nWhen a testing or debugging task starts, the agent is instructed to announce\nthe project and its clickable dashboard URL, then continue automatically.\nThe hub supplies the actual bound port and current token, including when a\nsecond project uses a fallback port. The link is also available in the\n`dashboard` field of `list_devices`, `get_project_context` and `session_start`.\n\n## Screenshots\n\n\n ![\"Overview](\"assets/screenshots/overview.png\")
\n Overview: request counts, error rate, JS thread lag, connection and device at a glance\n
\n ![\"Network](\"assets/screenshots/network.png\")
\n Network: colored methods, slow requests highlighted, foldable JSON, copy as cURL, secrets redacted before they leave the device\n
\n ![\"Mirror](\"assets/screenshots/mirror.png\")
\n Mirror: the live device screen over adb, click to tap, drag to swipe, wheel to scroll, plus Back/Home/Recents/Dev menu\n
\n ![\"Tools](\"assets/screenshots/tools.png\")
\n Tools: what the agent did and what the app did back, calls per tool split into answered / empty / failed, failures grouped by message, empty answers with the reason the tool gave, and the context each answer bills the agent\n