Two tools with one dependency between them: the app list gives you the app that the log read takes. What it changes is where the debugging happens — a stack trace can be read and reasoned about in the place you are already editing, instead of being copied out of a separate debugger window and pasted back. maxLogs is the argument that keeps a chatty app from filling the context with render warnings.
A two-tool bridge to a React Native app's debugger: the apps connected to Metro, and console logs over the debugger WebSocket.
- getConnectedApps, listing the apps attached to Metro on a given server port
- readConsoleLogsFromApp, reading a named app's console logs through the debugger WebSocket, bounded by maxLogs
A running Metro server with a React Native app connected to it. getConnectedApps takes the Metro port, and readConsoleLogsFromApp takes an app from what it returns.
One command — npx -y @twodoorsdev/react-native-debugger-mcp