Droidective MCP
An Android debugging app for macOS with an MCP server: an agent reads Reactotron data from React Native on localhost
- 62 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- The server hands the agent data from a React Native app: it is redacted by default, but redaction applies only in MCP and the Reactotron UI hides nothing
- The token is optional, so without it the port on 127.0.0.1 is open to any program on this computer
Install
- Works in
Manual install
claude mcp add --transport http reactotron http://127.0.0.1:4567/mcpEnable MCP in Droidective settings first: it is off by default.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The server hands the agent data from a React Native app: it is redacted by default, but redaction applies only in MCP and the Reactotron UI hides nothing
- The token is optional, so without it the port on 127.0.0.1 is open to any program on this computer
This is third-party code. Review the repository files before installing.
What it does
Droidective is a macOS app that gathers the familiar `adb`, `dumpsys`, `logcat` and other commands into a command palette: 61 tools for Android devices and React Native. For agents it has a built-in MCP server. Droidective embeds a Reactotron relay, so a React Native app configured for Reactotron reports straight into it, with no separate desktop Reactotron. The MCP server hands that data to an agent over Streamable HTTP. Its contract of 10 tools and 8 resources matches the server built into the official Reactotron. The server is enabled in the settings, in the MCP section, and is off by default. It listens only on 127.0.0.1, validates the `Origin` header, can require a static token and redacts sensitive data in responses by default. The MCP part works on Apple platforms only.
Who it is for. React Native and Android developers on macOS who debug an app together with an agent and want to give it Reactotron data.
Good fit when
- A React Native app misbehaves, and the agent looks at the data it sends to Reactotron
- Desktop Reactotron is not running but the agent needs the data: the relay is already built into Droidective
- Next to the agent you want a panel with `logcat`, screen mirroring and the other `adb` tools in one window
- Reactotron data must stay on the computer: the server listens only on 127.0.0.1
Not a fit when
- The agent has to tap buttons and install APKs: the MCP part serves only Reactotron data, and device control needs another server
- You work on Windows or Linux: the app is in beta there, and the MCP server is built for Apple only
- The app is not configured for Reactotron: there will be no data for the agent
Example request
Look at what the app sent to Reactotron over the last few minutes and name the most likely cause of the crash.MCP
- Transport
- http
- Authentication
- not required
Limitations
The MCP server works only in the macOS version. The Windows and Linux builds ship on the beta channel unsigned, and their screens are not yet at macOS level.
It needs macOS 14 or newer and `adb` from Android platform-tools. The server is off by default and serves Reactotron data; device control is not part of it. The contract follows official Reactotron at a pinned commit, so new Reactotron tools reach Droidective with a delay.
How to disable. Switch the server off in Droidective settings, in the MCP section, and remove the connection with `claude mcp remove reactotron`.
FAQ
How do I connect Droidective to Claude Code?
Enable MCP in the app settings, it is off by default, and run `claude mcp add --transport http reactotron http://127.0.0.1:4567/mcp`. Droidective has to stay running.
What data does the agent see?
What a React Native app configured for Reactotron sends. The server follows the contract of the MCP built into official Reactotron: 10 tools and 8 resources. Sensitive data in responses is redacted by default.
Does the MCP part work on Windows and Linux?
No. The MCP server part is built for Apple only, and the Windows and Linux versions ship on the beta channel.
Is a token required?
No, the server can be enabled without one. If a static token is set, the server demands it in a request header.
What else is in the app besides MCP?
61 features: `logcat` streams, screen mirroring, APK install, a file explorer, an app browser, a performance chart, an HTTP client. All are called from the command palette, opened with the shortcut from settings.
Discussion
No questions or reviews yet.
Related
MCP serversAn MCP server exposes Android screens, element search, taps, input and screenshots to agents testing authorized applications.
An MCP server to drive iOS and Android: simulators, emulators and real devices via accessibility trees and screenshots
An MCP server that drives an Android device over ADB: app navigation, input and automated tests
Android MCP Server: control Android through ADB
Android MCP Server
A Python MCP server: the agent takes screenshots of an Android device, reads clickable interface elements and runs ADB commands
Buoy MCP lets an agent read a running React Native or Flutter app, tap its screen and inspect the network
MCP server for Android through ADB and scrcpy: an agent sees the screen, taps, types text and launches apps.
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Droidective (this card) | yes | not required | 62 | |
| Mobile MCP | no | not required | 10,325 | aimed at controlling a device and does not serve Reactotron data |
| Android MCP | no | not required | 917 | aimed at driving Android and not at Reactotron data |
README in short
The documentation describes the app: the macOS DMG install, requirements (`adb`, optional emulator and Java), the list of 61 features and the Swift project structure. The Reactotron section explains how the app receives data and passes it to agents, and the platform table separates finished macOS from the Windows and Linux beta.