Potencia tu agente
El comando propio del publicador. No es un endpoint de PlugMCP.
Host a copy with our keys and logs.
npx -y [email protected]Claude Code no tiene enlace de instalación para un comando local. Copia el comando de abajo y ejecútalo en una terminal.
claude mcp add steve228uk-metro-mcp -- npx -y metro-mcp@0.15.0Ejecútalo en una terminal.
{ "mcpServers": { "steve228uk-metro-mcp": { "command": "npx", "args": [ "-y", "[email protected]" ] } }}claude_desktop_config.json
¿URL remota o un comando en tu máquina? En qué se diferencian las dos instalaciones
Ejecutar en PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
AbrirA 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.
Works with Expo, bare React Native, and any project using Metro + Hermes.
claude mcp add metro-mcp -- npx -y metro-mcp
# or with Bun
claude mcp add metro-mcp -- bunx metro-mcp
codex mcp add metro-mcp -- npx -y metro-mcp
# or with Bun
codex mcp add metro-mcp -- bunx metro-mcp
Codex stores MCP servers in ~/.codex/config.toml by default, and the Codex CLI and IDE extension share that configuration.
If you prefer to configure it manually:
[mcp_servers.metro-mcp]
command = "npx"
args = ["-y", "metro-mcp"]
Run OpenCode's interactive MCP installer:
opencode mcp add
Choose a local server, name it metro-mcp, and use npx -y metro-mcp as the command.
If you prefer to configure it manually, add this to opencode.json in your project, or to ~/.config/opencode/opencode.json for a global install:
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"metro-mcp": {
"type": "local",
"command": ["npx", "-y", "metro-mcp"],
"enabled": true
}
}
}
Or with Bun:
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"metro-mcp": {
"type": "local",
"command": ["bunx", "metro-mcp"],
"enabled": true
}
}
}
{
"mcpServers": {
"metro-mcp": {
"command": "npx",
"args": ["-y", "metro-mcp"]
}
}
}
Or with Bun:
{
"mcpServers": {
"metro-mcp": {
"command": "bunx",
"args": ["metro-mcp"]
}
}
}
If you use several MCP clients, add-mcp can write the config for supported agents, including Claude Code, Codex, Cursor, OpenCode, and VS Code:
npx add-mcp metro-mcp --all -g -y
metro-mcp supports multiple agents at the same time. Standard stdio installs start or reuse a local shared daemon for the same project directory and Metro/config options, so Codex, Claude Code, Cursor, and other clients can connect concurrently to the same running Metro app and see the same logs, network requests, errors, and runtime state.
If you want to expose one long-lived MCP endpoint yourself, start the shared server explicitly:
npx -y metro-mcp serve --mcp-port 8765
This serves Streamable HTTP at http://127.0.0.1:8765/mcp. The endpoint supports both the 2025-era MCP handshake and the 2026-07-28 negotiation; /sse and /messages are intentionally unavailable. Tools such as supergateway can point at the Streamable HTTP endpoint instead of launching a fresh stdio process per request.
codex mcp add metro-mcp -- npx -y metro-mcp --port 19000
# or
claude mcp add metro-mcp -- npx -y metro-mcp --port 19000
For OpenCode, add the port to the command array:
"command": ["npx", "-y", "metro-mcp", "--port", "19000"]
xcrun simctl is used for most operations)adb on your PATHbrew install idb-companion. Tools will tell you when IDB is needed.metro-mcp connects to your running Metro dev server the same way Chrome DevTools does:
No app modifications required for core debugging features.
→ See the full tools reference.
Hermes (the React Native JavaScript engine) only allows a single CDP debugger connection at a time. Since metro-mcp uses that connection, pressing "j" in Metro or tapping "Open Debugger" in the dev menu will steal the connection and disconnect the MCP.
metro-mcp solves this with a built-in CDP proxy that multiplexes the single Hermes connection, allowing Chrome DevTools and the MCP to work simultaneously.
Use the open_devtools MCP tool instead of the usual methods. It opens the same React Native DevTools frontend (rn_fusebox) that Metro uses, but routes the WebSocket connection through the proxy so both can coexist.
The tool automatically finds Chrome or Edge using the same detection as Metro and opens a standalone DevTools window.
The CDP proxy is enabled by default. To change the port or disable it:
# Set a fixed proxy port
METRO_MCP_PROXY_PORT=9222 npx metro-mcp
# Disable the proxy entirely
METRO_MCP_PROXY_ENABLED=false npx metro-mcp
Get live Metro CDP connection status in your Claude Code status bar.
Run setup_statusline in Claude Code — it writes a script to ~/.claude/metro-mcp-statusline.sh, then ask Claude to add it to your status bar:
/statusline add the script at ~/.claude/metro-mcp-statusline.sh
The status bar segment shows three states:
Record real user interactions (taps, text entry, scrolls) and generate production-ready tests — no app code changes required.
Describe a flow and the AI navigates the app, then generates the test:
"Write an Appium test for the guest checkout flow — start by tapping 'Start Shopping' on the welcome screen and end when the cart screen is visible."
The AI calls start_test_recording, navigates using tap_element/type_text/swipe, then generates a complete test with real selectors observed from the fiber tree.
start_test_recording → inject interceptors
(interact with the app)
stop_test_recording → retrieve event log
generate_test_from_recording format=appium
Supports Appium (WebdriverIO), Maestro YAML, and Detox.
→ See the testing guide for full details, format examples, and tips.
Register custom commands and expose state to the MCP server — no package needed. Add this to your app entry point in dev mode:
if (__DEV__) {
globalThis.__METRO_BRIDGE__ = {
commands: {
// Run custom actions from the MCP client
login: async ({ email, password }) => {
return await authService.login(email, password);
},
resetOnboarding: () => {
AsyncStorage.removeItem('onboarding_completed');
},
switchUser: ({ userId }) => {
store.dispatch(switchUser(userId));
},
},
state: {
// Expose state snapshots readable via get_redux_state
userStore: () => useUserStore.getState(),
},
};
}
Use list_commands and run_command to call these from the MCP client.
For enhanced features like real-time Redux action tracking, navigation events, performance marks, and React render profiling, install metro-bridge — see the client SDK docs and profiling guide.
See configuration docs for environment variables, CLI arguments, and config file options.
metro-mcp is fully extensible. See the plugins guide to build your own tools and resources.
MIT
🚇 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.
{ "mcpServers": { "steve228uk-metro-mcp": { "command": "npx", "args": [ "-y", "[email protected]" ] } }}Herramientas
Aún no hay lista de herramientas. Los servidores remotos la reciben tras la primera comprobación de estado.
Preguntas frecuentes
Copia en esta página la configuración stdio para Cursor, Claude Desktop, Claude Code o VS Code. Usa la instalación del publicador, no un proxy de PlugMCP.
Este registro no indica ninguna variable de entorno obligatoria.
Metro se ejecuta localmente por stdio.
Última comprobación: 2026-10-27. 🚇 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.