All servers / Developer / Metro MCP server
Metro MCP server
Plugin-based MCP server for React Native/Expo runtime debugging, inspection, and automation via Metro/CDP
Tested by ConnectATDScore 88 out of 100. Tested 2026-11-19 on package version 0.15.0. Package: metro-mcp · source
Score breakdown
| Runs | 18 / 20 | |
|---|---|---|
| Tool descriptions | 18 / 20 | |
| Package safety | 20 / 20 | |
| Maintenance | 20 / 20 | |
| Adoption | 12 / 20 |
What we saw
- Starts and answers the MCP handshake: yes (6.0 seconds including download)
- Tools offered: 88
- Last published: 2026-09-04
- Weekly downloads (npm): 1,469
- License: MIT · Direct dependencies: 10
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions. Under each name you can see how many of its parameters are explained.
get_console_logs7 of 7 parameters describedGet recent console output. Filter by level or search text.
clear_console_logs1 of 1 parameter describedClear the console log buffer.
get_network_requests5 of 5 parameters describedGet recent network requests from the React Native app.
get_request_details3 of 3 parameters describedGet full details of a specific network request including headers and body.
get_response_body3 of 3 parameters describedGet response body for a network request (cached if small; requires active session if large).
search_network6 of 6 parameters describedSearch network requests by URL pattern, method, or status code.
clear_network_requests1 of 1 parameter describedClear the network request buffer.
get_network_stats1 of 1 parameter describedGet aggregated network statistics: breakdown by domain, status code, and response times.
get_errors5 of 5 parameters describedGet recent uncaught exceptions from the React Native app.
clear_errors1 of 1 parameter describedClear the error buffer.
get_bundle_errors1 of 1 parameter describedGet recent Metro compilation/transform errors.
evaluate_js2 of 2 parameters describedExecute a JavaScript expression in the running React Native app and return the result. Use this for inspecting variables, calling functions, or querying app state.
list_devices1 of 1 parameter describedList connected devices and debuggable targets from Metro bundler.
get_app_infono parametersGet information about the connected React Native app (bundle URL, platform, device name).
get_connection_statusno parametersCheck the connection status to Metro bundler.
reload_app1 of 1 parameter describedReload the connected app and verify a fresh runtime. Uses Page.reload, with a directed Metro message fallback only for a verified app/device peer.
symbolicate1 of 1 parameter describedSymbolicate a stack trace using Metro bundler source maps. Converts minified/bundled locations back to original source files.
get_redux_state2 of 2 parameters describedGet the current Redux state tree or a specific slice. Works without client SDK if Redux DevTools extension is present or store is exposed globally.
dispatch_redux_action2 of 2 parameters describedDispatch a Redux action to the store.
get_redux_actions1 of 1 parameter describedGet recent Redux actions (requires metro-mcp client SDK for real-time tracking).
get_component_tree5 of 5 parameters describedGet a paged flat React component tree. Follow nextCursor to complete the snapshot and check traversal.complete before treating an empty page as authoritative.
find_components4 of 4 parameters describedSearch for components by name inside the app runtime. Check traversal.complete before treating no matches as definitive.
inspect_component3 of 3 parameters describedGet props, state, and hooks for the first exact component-name match, with traversal completeness metadata.
get_testable_elements2 of 2 parameters describedGet elements with testID or accessibilityLabel. Check traversal.complete before treating an empty elements array as definitive.
get_storage_keysno parametersList all AsyncStorage keys in the React Native app.
get_storage_item1 of 1 parameter describedRead a specific AsyncStorage key value.
get_all_storage1 of 1 parameter describedDump all AsyncStorage key-value pairs.
take_screenshot2 of 2 parameters describedCapture a screenshot from the connected iOS simulator or Android device.
list_simulators1 of 2 parameters describedList available iOS simulators or Android emulators.
install_certificate1 of 2 parameters describedInstall a root certificate on the iOS simulator or Android device.
get_native_logs2 of 3 parameters describedGet native platform logs from iOS simulator (syslog) or Android device (logcat).
app_lifecycle3 of 4 parameters describedLaunch, terminate, install, or uninstall an app on the simulator/emulator.
get_screen_orientation0 of 1 parameter describedGet the current screen orientation of the device.
open_deeplink1 of 2 parameters describedOpen a URL or deep link on the connected iOS simulator or Android device.
list_url_schemes2 of 2 parameters describedList URL schemes registered by an installed iOS app or Android package.
list_permissions2 of 2 parameters describedList all app permission statuses on the connected iOS simulator or Android emulator. Returns compact text: one name=status line per permission.
grant_permission3 of 3 parameters describedGrant a permission to the app on the connected iOS simulator or Android emulator.
revoke_permission3 of 3 parameters describedRevoke a permission from the app on the connected iOS simulator or Android emulator.
reset_permissions3 of 3 parameters describedReset one or all permissions for the app on the connected iOS simulator or Android emulator. On iOS, omitting service resets all services. On Android, omitting service resets all runtime permissions.
open_app_settings2 of 2 parameters describedOpen the connected app's system settings page using React Native Linking.openSettings().
list_elements1 of 3 parameters describedGet labelled or interactive elements from the focused React screen. Check traversal.complete before treating an empty elements array as definitive.
tap_element3 of 4 parameters describedTap by label, testID, or logical device-point coordinates. Uses React handlers, then installed SimView or IDB on iOS and adb on Android. Coordinates use native input directly; native results identify the backend and dispatch state.
type_text2 of 3 parameters describedType text into an input field. Targets a specific input by testID/label, or the first visible TextInput. Uses the React handler first, then SimView or IDB on iOS and the selected ADB serial on Android.
long_press4 of 5 parameters describedLong press using a React handler by label/testID, then semantic native input through SimView or IDB when the handler is unavailable. Explicit coordinates use native input directly; native results identify the backend and dispatch state.
swipe1 of 2 parameters describedScroll through React, then use installed SimView or IDB on iOS and the selected ADB serial on Android. Native results identify the backend and dispatch state.
press_button1 of 2 parameters describedPress a device button (HOME, BACK, VOLUME_UP, etc.).
get_navigation_state1 of 1 parameter describedGet the full React Navigation / Expo Router state tree including current route, params, and stack history.
get_current_routeno parametersGet the currently focused route name and params.
get_route_historyno parametersGet the navigation back stack / history.
list_routesno parametersList registered route names from available navigation state. Uninitialized nested navigators are not discoverable.
audit_accessibility3 of 3 parameters describedAudit the current screen within bounded Fiber traversal limits. Checks labels, roles, testIDs, and alt text; returns issues, summary, and traversal coverage.
check_element_accessibility2 of 2 parameters describedCheck accessibility properties of a specific component by name or testID.
get_accessibility_summaryno parametersQuick overview: counts of elements with and without proper accessibility props.
list_commandsno parametersList all custom commands registered by the app. Commands are registered on global.__METRO_BRIDGE__.commands or global.__METRO_BRIDGE_COMMANDS__.
run_command3 of 3 parameters describedExecute a custom command registered by the app. Pass parameters as a JSON object.
start_test_recordingno parametersInject interaction interceptors into the running app via the React fiber tree. Captures taps, text entry, long presses, keyboard submits, and scroll/swipe gestures — with no changes to your app code. Works with ScrollView, FlatList, SectionList, FlashList, and other scroll containers. Call stop_test_recording when done, then generate_test_from_recording to get the test.
stop_test_recordingno parametersStop the active recording, retrieve all captured events, and store them for test generation. Returns a summary of what was recorded. Call generate_test_from_recording next to produce Appium, Maestro, or Detox test code.
generate_test_from_recording5 of 5 parameters describedConvert the most recent recording into a test file. Supports three formats: appium (WebdriverIO + Mocha), maestro (YAML), and detox (Jest). Call stop_test_recording first.
generate_wdio_config17 of 18 parameters describedGenerate a minimal but runnable wdio.conf.ts for Appium + React Native testing, along with the npm install command.
add_recording_annotation1 of 1 parameter describedAdd a human-readable annotation (comment marker) to the current recording. Useful for labelling major flow checkpoints like "reached checkout", "error appeared here", "navigated to payment". Annotations appear as code comments in generated tests.
save_test_recording1 of 1 parameter describedSave the current recording events to disk as JSON so they can be reloaded later. Useful for regenerating the same flow in a different test format without re-recording. Files are saved to ~/.metro-mcp/recordings/<filename>.json.
load_test_recording1 of 1 parameter describedLoad a previously saved recording from disk and make it available for test generation. After loading, call generate_test_from_recording with any format to regenerate the test. Use list_test_recordings to see available files.
list_test_recordingsno parametersList all previously saved test recordings in ~/.metro-mcp/recordings/. Returns filenames and sizes. Use load_test_recording to load one for test generation.
start_profiling1 of 1 parameter describedStart profiling the running React Native app. Primary path: injects into the React DevTools hook (__REACT_DEVTOOLS_GLOBAL_HOOK__) via evalInApp — captures all component render durations without requiring <Profiler> wrappers, works on all architectures. Fallback (legacy arch only): CDP Profiler domain for JS CPU call-graph sampling. Perform the interaction you want to measure, then call stop_profiling.
stop_profiling2 of 2 parameters describedStop profiling and return an analysis of the captured data. DevTools hook mode: returns top components by total render duration across all commits. CDP mode: returns top JS functions by self time and total time. Must call start_profiling first.
get_profile_statusno parametersCheck whether profiling is active, which mode is in use, and whether a previous profile is available.
get_flamegraphno parametersReturn the current profiling results as a human-readable text chart. Shows React DevTools component profile (if captured), CPU flamegraph (if CDP profile captured), and React render data from <Profiler> components (if set up). Call stop_profiling first to populate the profile data.
get_react_renders1 of 1 parameter describedRead React render timing data collected via <Profiler onRender={trackRender}>. Returns all recorded renders sorted by actualDuration descending, with memoization savings from baseDuration. Requires importing trackRender from metro-mcp/client. Use clear=true to reset the buffer.
get_memory_infono parametersGet current JavaScript heap memory usage from the running app. Returns used heap, total heap, and heap size limit (when available). Call repeatedly to track memory growth over time or to detect leaks.
profile_action3 of 3 parameters describedProfile a specific JavaScript expression or code path in a single call. Starts profiling, evaluates the expression, waits for it to complete (plus optional extra duration), then stops and returns the top functions by self time. Use instead of calling start_profiling / stop_profiling manually for focused measurements.
start_heap_sampling1 of 1 parameter describedStart Hermes heap allocation sampling via CDP HeapProfiler. Records memory allocation call stacks to identify where objects are being allocated. Call stop_heap_sampling to retrieve the top allocation sites.
stop_heap_sampling1 of 1 parameter describedStop heap allocation sampling and return the top allocation sites. Shows which functions are allocating the most memory, useful for diagnosing memory leaks. Must call start_heap_sampling first.
wait_for_element5 of 5 parameters describedPoll the component tree until an element matching the given testID or accessibilityLabel appears. Returns element info on success. Use after tap_element, navigate(), or any action that triggers async screen transitions or data loading — instead of immediately calling the next tool. Returns traversal metadata immediately when the bounded search is incomplete.
wait_for_condition3 of 3 parameters describedPoll a JavaScript expression in the app until it returns a truthy value, then return that value. Useful for waiting on state changes, loading flags, API responses, or any async condition. Example: wait for globalThis.myStore?.isLoaded === true.
wait_for_navigation2 of 2 parameters describedPoll the active navigation route until it matches the expected route name, then return. Requires the navigation plugin to be set up (get_current_route must work). Use after tap_element on a link or after dispatching a navigate() action.
setup_statuslineno parametersWrites the Metro CDP connection status script to ~/.claude/metro-mcp-statusline.sh. Does not modify settings.json — tell the user to add it to their status line themselves (e.g. ask Claude: "/statusline add the script at ~/.claude/metro-mcp-statusline.sh"). Only works with Claude Code.
list_debug_globals1 of 1 parameter describedAuto-discover well-known global debugging objects (Redux stores, Apollo Client, Expo Router, React DevTools hook, etc.) available in the app runtime.
inspect_at_point3 of 5 parameters describedInspect the smallest measured host component at screen coordinates. Uses awaited Fabric/Paper measurement and returns traversal completeness metadata.
open_devtools1 of 1 parameter describedOpen the React Native DevTools debugger panel in Chrome. Connects through the CDP proxy so DevTools and the MCP can share the same Hermes connection.
get_app_directories1 of 2 parameters describedGet known app sandbox directory paths (documents, cache, temp, library). Returns absolute paths usable with list_directory and read_file.
list_directory3 of 4 parameters describedList files and directories in an app sandbox path. Call get_app_directories first to obtain the root path.
read_file4 of 5 parameters describedRead the contents of a file from the app sandbox. Enforces a configurable size cap (default 50 KB, max 1 MB) to avoid flooding context.
get_file_info2 of 3 parameters describedGet file or directory metadata: size, modification date, and whether it is a directory.
delete_file3 of 4 parameters describedDelete a file from the app sandbox. Requires confirm: true to prevent accidental deletion.
get_build_infono parametersReturn build-time and runtime flags for the running React Native app: __DEV__, platform, OS version, RN version, Hermes engine, New Architecture, and expo-application fields if available.
get_env_vars2 of 2 parameters describedReturn a filtered subset of process.env from the running app. Credential-like keys (SECRET, KEY, TOKEN, PASSWORD, etc.) are redacted by default. Use filter to search by key name substring.
get_platform_constantsno parametersReturn the full Platform.constants object from React Native, including OS-specific build details.
get_expo_configno parametersReturn expo-constants manifest/expoConfig fields if the app uses Expo, otherwise null.
Tested in a sandbox with an empty environment: no API keys, a throwaway folder, nothing from a real account. A passing test shows the server runs and responds. It is not a security audit.