ExecBro
About
Debug and drive live React Native apps: logs, network, screenshots, UI automation, and fiber-tree inspection.
Details
- Author
- igorzheludkov
- Categories
- Productivity, Developer Tools, Other
Jump to
Setup
Install ExecBro in your MCP client (Claude Desktop, Cursor, Windsurf, and others).
Repository: https://github.com/igorzheludkov/execbro
Follow the installation instructions in the repository README, then restart your MCP client.
Give your AI assistant eyes and hands into your running React Native app.Like Chrome DevTools — but for AI agents.
Build, debug, and verify features end-to-end — without leaving the chat.
ExecBro is the runtime bridge between your AI coding assistant and your running React Native app — exposing MCP tools to read logs and network, inspect component state, capture screenshots, tap the UI, and run JS. Zero config, no SDK or code changes required to start — and installing theoptional SDKis recommended for the most robust log and network capture.
- Setup ExecBro as an MCP server for your agent of choice
- Setup UI automation helpers
- Install the SDK in your React Native app— optional, but recommended for the most robust log, network, and state experience
- Authorize and link to the web dashboard— optional for usage stats and session history,required to unlock unlimited usage via ExecBro Pro
- Start your React Native app (npm start/expo start)
- Ask your AI assistantin plain language — e.g. "Connect to the simulator and investigate what caused the error on the screen"
Log in atexecbro.comto see your ExecBro activity rendered back to you: which tools you use most, toolerror rates, and yoursession history— so you can spot flaky tools, track usage over time, and understand how your agent drives the app across sessions. It's built from the same anonymous telemetry described inTelemetry & Privacy, tied to your installation ID.
Linking your installation here is alsorequired to unlockExecBro Pro— signing in and authorizing your installation is what lets the unlimited-usage plan take effect; without it, the free tier's monthly cap applies even after subscribing.
- Console Log Capture- Captureconsole.log,warn,error,info,debugwith filtering and search. Note: on a cold start (first app launch), logs emitted before the MCP server connects are missed — subsequent reloads capture everything. Install the optionalSDKto buffer logs from the very first line of app startup
- Network Request Tracking- Monitor HTTP requests/responses with headers, timing, and body content. Like logs, early network requests on cold start may be missed before the connection is established. Install the optionalSDKfor full capture from app startup including request/response bodies
- Response Mocking- Replace or tamper with HTTP responses so error paths are reached through the app's real code — the request builder, the error branch, the retry — instead of being faked by writing state directly. Simulate offline, delay responses, fail only the first attempt to test a retry, or re-issue a captured request with one field changed. Rules survive reload, and altered traffic is always tagged. See themocking tutorial
- JavaScript Execution- Run code directly in your app (REPL-style) and inspect results
- Global State Debugging- Discover and inspect Apollo Client, Redux stores, Expo Router, and custom globals. Wire stores and other app internals straight into the agent with the optionalSDKfor direct, reliable state access
- Bundle Error Detection- Get Metro bundler errors and compilation issues with file locations
- Tap-to-Source- Point at any element with RN's Element Inspector and get back the absolute source file and line where it is rendered, resolved from the React fiber's_debugStackvia Metro symbolication. Works on React 19, where_debugSourceno longer exists. Selections are buffered in the background, so taps you make during a manual inspector session are captured without asking the agent first
- iOS Simulator- Screenshots, app management, URL handling, boot/terminate (via simctl)
- Android Devices- Screenshots, app install/launch, package management (via ADB)
- Unified Tap- Singletaptool with automatic fallback chain: fiber tree → accessibility → OCR → coordinates. Auto-detects platform, accepts coordinates from screenshots and layout tools unchanged. Returns post-tap screenshot and verifies visual change by default
- Unified Swipe- Singleswipetool that auto-routes to iOS or Android based on the connected device. Takes coordinates in the same screen space as the layout tools and screenshots — no conversion — and returns averification.meaningfulsignal so agents detect end-of-list, non-scrollable surfaces, and missed coordinates — and on a screen with no React Native connection it says it could not inspect rather than guessing. Essential for scrolling virtualized lists (FlatList/SectionList) where off-screen items aren't in the fiber tree
- Real Multi-Touch Pinch(Android emulator only — iOS in progress)- Apinchtool that sends two genuine kernel touch contacts through the Android emulator's multi-touch bridge, so it zooms maps, galleries, WebViews, and native views alike — it works below the app, not through React Native. Returns the sameverification.meaningfulsignal asswipe, and refuses on unsupported targets instead of faking a result
- UI Automation- Swipe, long press (tapwithduration, resolving the target by testID/text/component), key events, and text input on both platforms.input_texttargets a field itself and verifies the write by reading it back; on Bridgeless/Fabric appsreplace:trueoverwrites pre-filled values by updating React state throughonChangeText, so controlled components (Formik, react-hook-form, useState) stay consistent.native:truetypes into whatever the OS reports as focused, with no RN connection needed, anddismiss_keyboardoperates the same way
- Accessibility Inspection- Query UI hierarchy to find elements by text, label, or resource ID
- OCR Text Extraction- Extract visible text with tap-ready coordinates via Google Cloud Vision (works on any screen content)
- Connect All Devices-scan_metroautomatically discovers and connects to all Bridgeless targets on each Metro port
- Device Targeting- Every tool accepts an optionaldeviceparameter for targeting specific devices by name (case-insensitive substring match)
- Per-Device Buffers- Logs and network requests are captured separately per device for clean debugging
- Cross-Platform Comparison- Debug iOS and Android side-by-side, comparing logs, network traffic, and component trees
- Auto-Discovery- Scans Metro on ports 8081, 8082, 19000-19002 automatically
- Multi-Device Support- Connects to all Bridgeless targets simultaneously, with per-device log and network buffers
- Auto-Reconnection- Exponential backoff (up to 8 attempts) when connection drops
- Efficient Buffering- Circular buffers: 500 logs, 200 network requests, 100 inspector selections
- Platform Support- Expo SDK 54+ (Bridgeless) and React Native 0.70+ (Hermes)
Add ExecBro to Claude Code in one command — no installation,npxfetches the latest version on demand:
claude mcp add execbro --scope user -- npx -y execbro@latest
Then fully restart the client (quit and relaunch) so it picks up the new server.
Using a different client or need platform setup?Thefull setup guidecovers Claude Desktop, Codex CLI, Cursor, VS Code Copilot, Windsurf, Zed, and Gemini CLI, plusAndroidandiOS simulator UI automationrequirements.
ExecBro works with zero app changes, but installing the companionexecbro-sdkpackage is the single biggest upgrade to debugging quality. It lets youwire up the important parts of your app — your state stores and your network layer — directly into the agent's reach, so the AI inspects real Redux/TanStack Query state and full request/response bodies instead of guessing from the outside.
It's onenpm installplus a singleinit()call in your app's entry file. See theSDK guidefor install, initialization, and every config option.
- Node.js 20.9+
- React Native app running with Metro bundler
- Recommended:execbro-sdkin your app — wires stores and the network layer into the agent for dramatically better debugging (optional; ExecBro works without it)
- iOS UI automation:AXe CLI(brew install cameroncooke/axe/axe, default) orFacebook IDB(brew install idb-companion, opt in viaIOS_DRIVER=idb) — required for tap, swipe, text input, accessibility on iOS Simulator
- Optional for offline OCR fallback: Python 3.6+ (only needed when cloud OCR is unavailable, seeOCR guide)
Pre-built skills for common debugging workflows — session setup, log inspection, network debugging, and more. See theskills guidefor the full list and installation instructions.
See thefull tool referencefor all tools with descriptions. Key tools:
Just describe what you want in plain language — the agent picks the right tools. You don't need to know tool names or ask for a specific one. For example:
Connect to the simulator and investigate what caused the error on the screen
Check the network logs and investigate why this error is happening
Why is the current screen empty? Take a look and figure it out
The list won't scroll — scroll it down and check what's going on
Why does this button look wrong — what component renders it and where?
The agent connects to Metro, reads logs and network, inspects the screen, and drives the UI as needed to answer.
- Fetches device list from Metro's/jsonendpoint
- Connects to the main JS runtime via CDP (Chrome DevTools Protocol) WebSocket
- EnablesRuntime.enableto receiveRuntime.consoleAPICalledevents
- Network capture via two paths:
- With SDK: Reads from the SDK's in-app buffer viaRuntime.evaluate— captures all requests from startup with full headers and bodies, including cold-start events that CDP would miss
- Without SDK: Enables CDPNetwork.enable(on supported targets) or injects a JS fetch interceptor as fallback. On cold start, events emitted before the CDP connection is established are lost; subsequent reloads capture everything
- One server per session— each agent session (each terminal or IDE window) runs its own ExecBro MCP server instance.
- Connects on request, not on startup— the server never auto-connects. It only attaches to your running React Native app when you ask it to (e.g.scan_metro), so it stays out of the way until you actually need a device.
- One driver per device— if two or more sessions in the same project point at the same Metro/device, they'll compete to control it, like a car with two steering wheels. Keep interaction to a single session per device.
- Want parallel sessions? Give each its own device + port— run separate work in agit worktreewith its own Metro instance on a different port, and connect a second device (simulator/emulator) to it. For example, keepmainon the default8081and start the worktree's Metro on8082(npx react-native start --port 8082, ornpx expo start --port 8082), then launch that worktree's app pointed at8082. Each agent session thenscan_metros and drives its own device, so the two never fight over the connection.
- Make sure the app is running on a simulator/device
- Check that Metro bundler is running (npm start)
- Ensure the app is actively running (not just Metro)
- Tryclear_logsthen trigger some actions in the app
- Checkget_appsto verify connection status
- On cold start (first launch):The CDP connection is established after the app's early initialization code has already run, so startup logs and network requests are missed. Once connected, usereload_app— the subsequent reload captures everything from the beginning because the connection is already in place. To capture startup events on every launch, install the optionalSDK
ExecBro sends two separate signals, not one:
- Usage metering(required, always on) — a counted tool-call signal that powers the free tier and enforces its monthly cap. This stays on whenever you're using the free tier; it cannot be disabled and still use ExecBro's free tools.
- Product analytics(optional) — tool names, success/failure, and durations, used to improve the product.No source code, file paths, or app content is ever sent.This is what powers yourusage dashboard. Disable it withEXECBRO_TELEMETRY=falsein your MCP server config. Doing so turns off analytics only — it doesnotdisable usage metering, which keeps counting tool calls against the free-tier cap regardless.
See theTelemetry & Data Collection guidefor the full breakdown of what's collected, auto-registration, and how to opt out, andPRIVACY.mdfor the complete privacy policy.
ExecBro isfree to use— every feature, fully intelligent — up to600 tool calls per month. That covers evaluation and everyday debugging. Heavy users can remove the cap withExecBro Pro($8.99/mo) for unlimited calls and every future hosted feature. Seeexecbro.com/pricing.
[!NOTE]Grandfather notice:the 600-call monthly cap starts applying2026-08-01for new installs. If you already had ExecBro installed before then, you get a free month on top — your cap doesn't start until2026-08-31. You'll also see this as an in-app notice. No action needed unless you want tolink your account and upgrade to Proahead of time. Questions?zigor535@gmail.com.
Please run this at the end of your session to help me make the tools better.ExecBro is built for AI agents, so the most valuable feedback comes from the agent itself — paste this prompt to your agent:
Write a report about your experience with the ExecBro tools — where you were struggling and what could be improved. Save it as a Markdown file for me, then submit it using thesend_feedbacktool (type"feedback") so it becomes a GitHub issue.
It takes 30 seconds: your agent runssend_feedback, hands you a pre-filled GitHub issue URL (environment info already attached), and you click submit — no GitHub setup, no copy-pasting. Real friction logs from real sessions are what shape the roadmap and get fixed first, so please send one. 🙏 And if you just have a quick idea or question, drop intoGitHub Discussionsto share feedback, request features, and vote on what gets built next.
Ships as the npm packageexecbro. The package was previously published asreact-native-ai-devtoolsand before that asreact-native-ai-debugger— both legacy names keep receiving identical builds via mirror-publish, so existing installations and MCP configs keep working unchanged. New installs should useexecbro.
[!IMPORTANT]Already using ExecBro?npxcaches packages indefinitely, so you may be stuck on an old version without realizing it. Update your MCP config to usenpx -y execbro@latest(seeSetup) so every session pulls the latest release with new tools and bug fixes. New installs after this change auto-update automatically.
An MCP server that equips your AI coding assistant with live, verified Android knowledge — so it builds from official sources, not from memory.
24 AI-callable tools for API mocking, chaos engineering, security scanning, SSL checks, CORS debugging, OpenAPI validation, JWT decoding, HAR analysis, distributed tracing, webhook capture, automation workflows, and uptime monitoring. Supports OAuth2 and Bearer token auth.
Python MCP server for TMDB search, Stremio library management, and Android TV playback/control over native ADB.
Drives an Android emulator or a real device over adb: screenshots, UI hierarchy with true device-pixel coordinates, tap and type, app lifecycle, logcat, and Gradle builds and tests.
Interact with Android devices using the Android Debug Bridge (ADB).
Control Android devices via the Android Debug Bridge (ADB).
An agentic toolkit to control, debug, and profile iOS and Android apps.
The deepest Android Debug Bridge MCP server — 147 tools from UI to baseband.
MCP server which expose Android's app runtimes to coding agents.
A plugin-based MCP server for React Native runtime debugging, inspection, and automation. Connects to Metro bundler via Chrome DevTools Protocol — no app code changes needed for most features.
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
