All servers / Developer / MetaMask Device MCP server
MetaMask Device MCP server
MCP server for mobile device interaction — iOS (IDB), Android (ADB), and Appium/BrowserStack
Tested by ConnectATDScore 94 out of 100. Tested 2026-11-18 on package version 0.8.0. Package: @metamask/device-mcp · source
Score breakdown
| Runs | 18 / 20 | |
|---|---|---|
| Tool descriptions | 20 / 20 | |
| Package safety | 20 / 20 | |
| Maintenance | 20 / 20 | |
| Adoption | 16 / 20 |
What we saw
- Starts and answers the MCP handshake: yes (11.7 seconds including download)
- Tools offered: 29
- Last published: 2026-11-13
- Weekly downloads (npm): 52,444
- License: (MIT OR Apache-2.0) · Direct dependencies: 2
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.
device_snapshotno parametersCapture the current UI hierarchy from the device. Returns all visible elements with their types, labels, identifiers, values, frames, and enabled state. Call this FIRST to see what is on screen before interacting.
device_screenshot1 of 1 parameter describedCapture a screenshot of the current device screen. Returns base64-encoded PNG data. Optionally saves to a file path.
device_infono parametersGet information about the connected device: platform, name, OS version, device ID.
device_tap_element4 of 4 parameters describedFind an element in the UI hierarchy by query and tap its center. Specify at least one of: label, identifier, text, type. Call device_snapshot first to see available elements.
device_tap_coordinates2 of 2 parameters describedTap at exact screen coordinates. Use as a last resort when an element cannot be found by label/identifier/text. Get coordinates from device_snapshot frame data.
device_type1 of 1 parameter describedType text into the currently focused input field. Tap an input element first to focus it, then call this. The field is cleared before typing on all backends.
device_swipe4 of 4 parameters describedSwipe on the device screen. Use natural scrolling: swipe "up" to scroll down. Optionally specify start coordinates and distance. Coordinates are logical points, not screenshot pixels. The gesture runs with a fixed 0.3s duration; command completion does not verify that content moved — confirm with a screenshot or snapshot.
device_long_press5 of 5 parameters describedLong press an element. Used for context menus, drag initiation, and other long-press interactions. Default duration is 1000ms.
device_wait_for5 of 5 parameters describedPoll the UI hierarchy until an element matching the query appears (and, when it appears during the wait, stops moving). Useful for waiting on transitions, loading states, or navigation.
device_app_state1 of 1 parameter describedGet the current state of an app by bundle ID. Returns whether the app is running, installed, or not found.
device_open_app1 of 1 parameter describedLaunch or bring to foreground an app by bundle ID. iOS: bundle ID (e.g. io.metamask). Android: package name (e.g. io.metamask).
device_close_app1 of 1 parameter describedForce-stop an app by bundle ID. The app process is terminated.
device_press_button1 of 1 parameter describedPress a device button. "enter" sends the Return key and can submit a form. iOS has no back button: "back" fails with UNSUPPORTED_ON_IOS; tap the screen's back control instead.
device_dismiss_keyboardno parametersHide the on-screen keyboard. Call after typing to reveal elements that may be obscured by the keyboard. On iOS this presses Return when a keyboard is shown (which can submit a single-field form) and does nothing otherwise.
device_dismiss_alert1 of 1 parameter describedAccept or dismiss a system alert or permission dialog. Use accept=true for "Allow"/"OK", accept=false for "Deny"/"Cancel". Check device_snapshot first to confirm an alert is present.
device_logs2 of 2 parameters describedCapture recent device logs. iOS: system log via IDB. Android: logcat. Optionally filter by text pattern.
device_scroll_to_element6 of 6 parameters describedSwipe until an element matching the query is inside the viewport (being in the UI tree is not enough), and report how many swipes it took. Fails when the element is not in view after maxAttempts swipes or the screen stops moving. Specify at least one of: label, identifier, text, type.
device_get_alert_textno parametersGet the text content of the currently displayed system alert or dialog. Call this before device_dismiss_alert to understand what the alert says.
device_get_window_sizeno parametersGet the width and height of the device screen in pixels (Android) or points (iOS).
device_context2 of 2 parameters describedList or switch between app contexts (NATIVE_APP, WEBVIEW, etc.). Use action=list to see available contexts, action=switch to change. On Android (adb), WEBVIEW appears when a debuggable in-app WebView is open; use webview_cdp to drive its DOM. On iOS, WebView contexts require the Appium backend.
device_clipboard2 of 2 parameters describedRead or write the device clipboard. Use action=get to read clipboard text, action=set to write. On Android (adb), only action=set is supported; reading requires the Appium backend.
device_screen_recording2 of 2 parameters describedStart or stop recording the device screen as an MP4 video. Call with action=start to begin, action=stop to end and save. Returns the file path on stop.
device_generate_locatorsno parametersGenerate ranked locator suggestions for all interactive elements on the current screen. Each element gets a prioritized list: identifier (testID/resource-id) > label > text > type. Use this after healing to find the correct selector for updating test source code.
device_get_element_text4 of 4 parameters describedFind an element in the UI hierarchy by query and return its text content (label or value). Specify at least one of: label, identifier, text, type. Call device_snapshot first to see available elements.
device_list_devicesno parametersList all connected devices and simulators/emulators.
device_select_device1 of 1 parameter describedSelect a device to use for this session. Call device_list_devices first to see available devices.
hermes_cdp6 of 6 parameters describedSpeak raw Chrome DevTools Protocol (CDP) to the React Native Hermes JS runtime of a running app via Metro’s inspector proxy (iOS and Android). Requires a DEBUG build with Metro running; release builds expose no inspector. Blocked methods (for safety): Runtime.terminateExecution, Inspector.detached. Node 20 must be launched with NODE_OPTIONS="--experimental-websocket" (Node 22+ works out of the box). Example: method "Runtime.evaluate" with params {"expression":"1+1","returnByValue":true} — the raw response nests the value at result.result.value.
hermes_targets3 of 3 parameters describedList and diagnose the debuggable React Native Hermes targets that Metro’s inspector proxy currently exposes (iOS and Android). Reports each candidate (id / title / appId / logicalDeviceId / nativePageReloads / wsUrl) plus which target would be chosen or why it is ambiguous. Use it to confirm Metro is running and your app is registered. Requires a DEBUG build with Metro running.
webview_cdp4 of 4 parameters describedSpeak raw Chrome DevTools Protocol (CDP) to a debuggable in-app Android WebView — the web page inside the app’s in-app browser. Unlike hermes_cdp (React Native JS engine, no DOM), this targets the Chromium page and exposes the full Chrome surface (Runtime, DOM, Page, Network, Input). Android only; the app must call WebView.setWebContentsDebuggingEnabled(true). Blocked methods (for safety): Browser.close, Target.closeTarget, Target.disposeBrowserContext, Browser.crashGpuProcess. Node 20 must be launched with NODE_OPTIONS="--experimental-websocket" (Node 22+ works out of the box). Example: method "Runtime.evaluate" with params {"expression":"document.querySelector('#submit').click()"}.
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.