$ loading_
Debug, inspect, and automate React Native runtime via Chrome DevTools Protocol.
This is an open-source third-party MCP debugging server under the MIT license with no declared secrets or remote endpoints, and the provided materials do not show clear high-risk red flags. Its core function involves local code execution and React Native runtime debugging/automation, which is typical for this class of tools; use it in a controlled development environment and verify actual permission boundaries.
The materials explicitly state that no keys or environment variables are required, and no API tokens, account credentials, or server-side authentication secrets are mentioned; based on the provided facts, credential leakage or abuse exposure appears low.
Although no remote host is declared, the tool performs debugging, inspection, and automation of React Native/Metro/Hermes runtimes via the Chrome DevTools Protocol, which typically involves connecting to local debugging targets. The materials do not show data being sent to unknown external endpoints, but actual network behavior should still be verified at deployment time.
The system flags this tool as executes-code, and its role as an MCP server for runtime debugging and automation reasonably implies the ability to launch local processes, perform debugging control, or drive the target runtime. These are standard powers for this class of tool, and the materials do not show red flags indicating system access beyond its stated purpose.
Its runtime debugging, inspection, and automation features may access application state, debug output, and data associated with Metro/Hermes sessions; however, the materials do not state that it broadly reads/writes arbitrary files, persists sensitive data, or requests data permissions unrelated to its purpose. Based on the current facts, this looks like normal development-time data exposure, though the real access scope should be verified in implementation.
There are positive signals: it is open source, auditable, and MIT-licensed, which lowers risk; however, it comes from a third-party registry, has 0 stars, unknown maintenance status, and no README, limiting verifiability and maturity. No closed-source exfiltration or obvious malicious indicators are shown, but supply-chain confidence is limited, so source and dependency review is advisable before use.
Copy the install command and let the AI configure it · recommended for beginners
No copy-paste install info for "metro-mcp" yet — see the docs or source repo.
Connect to the current React Native app, inspect Hermes/Metro runtime state, and list key debugging details.
A runtime overview, debugging details, and possible issues.
Based on the current page state, perform automated debugging actions: switch to the target screen, read console logs, and check network/runtime errors.
The automation results and a summary of errors.
For my Expo React Native project, inspect possible causes of slow startup, broken hot reload, or debugging failures, and provide troubleshooting suggestions.
Root-cause analysis and actionable troubleshooting steps.
Automate, inspect, monitor, and test React Native apps through MCP tools.
Connect Chrome DevTools so AI can debug pages and inspect performance.
Inspect, control, and debug React Native apps in simulators and emulators.
Control and debug running Node.js processes through a CDP-to-DAP bridge.
Automate Chromium for web actions, debugging, and browser testing tasks.
Control Chrome DevTools with AI for debugging, screenshots, and script execution.