ERIUS PHONE vs Oswright
A side-by-side look at the ERIUS PHONE and Oswright MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose ERIUS PHONE for os automation work as a local process; choose Oswright for os automation as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose ERIUS PHONE when
- You need dedicated capabilities in the OS Automation domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
ERIUS_PHONE_API_KEY, ERIUS_PHONE_DEFAULT_DEVICE, ERIUS_PHONE_API_URL, ERIUS_PHONE_TIMEOUT. - You want tools like
list_devices, whoami, get_device.
Choose Oswright when
- You need dedicated capabilities in the OS Automation domain.
- You prefer a local stdio subprocess transport.
- You want tools like
screenshot, get_screen_info, find_text_on_screen.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | OS Automation | OS Automation |
| Quality signal | 60/100 · Good | 59/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | ERIUS_PHONE_API_KEYERIUS_PHONE_DEFAULT_DEVICEERIUS_PHONE_API_URLERIUS_PHONE_TIMEOUT | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2 | 4 |
| Directory activity | 1 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 21 | 43 |
| Full listing | View ERIUS PHONE | View Oswright |
Tools & capabilities
ERIUS PHONE tools 21
list_devicesList every Android device your API key can access, with live status (booted, Android version, screen size). Call this first to get device ids.whoamiShow which ERIUS PHONE account (tenant) and key id this server is using, and the device ids it can access. Handy to check the API key works.get_deviceGet full status of one device: boot state, Android version, screen size, and the app currently in the foreground. Omit `device` to use the default.snapshotGet an accessibility-tree snapshot of the current screen: every visible element with its text, role, and a `ref` id you can pass to tap/type/scroll. This is how the agent 'sees' the phone — read it before acting, and take a fresh one after any action since refs reset on every snapshot.screenshotTake a screenshot of the device screen right now and return it as an image you can look at, plus one line of text with the image size and the device's real screen size. The default is a JPEG whose longest side is 1024 px (tens of KB). A full-size PNG of a 1440x3120 phone is about 3 MB, which is more than many MCP clients accept in a tool result, so ask for it only when you need it: format="png", max_side=None. `format` is "jpeg", "webp" or "png"; `quality` is 1-100 (jpeg/webp); `max_side` caps the longest side in pixels (64-8192); `scale` (0.1-1) shrinks by a factor instead. When the image is smaller than the screen, pass its size as image_width/image_height to tap(), long_press() or swipe() so x,y are read in the image's pixels. Prefer snapshot() when you only need text and refs: it's far smaller.foregroundGet just the foreground app: package, activity, and whether a crash dialog is showing. Cheaper than a full snapshot when you only need this.tapTap an element. Prefer `ref` from a snapshot(), or `text`/`content_desc` to tap by visible label. Falls back to raw `x`,`y` pixel coordinates: in device pixels, or, with `image_width` and `image_height`, in the pixels of a screenshot of that size (the API maps the point to the screen).long_pressLong-press an element (e.g. to open a context menu or start a drag). Targets work like tap(): `ref`, `text`/`content_desc`, or raw `x`,`y` (with `image_width`/`image_height` when they come from a scaled screenshot). `ms` (hold time, default 800) only applies to the x,y form.type_textType text into a field. Optionally tap a `ref` or `text_target` label first to focus the field, `clear` the existing value, or press Enter after. Keystrokes sent while the field is still opening are lost, so if tapping the field opens a new screen (e.g. a search page), tap it first, wait for it with snapshot() or wait_for_text(), then type with no target. Check the result with snapshot(). Only printable ASCII is supported (adb limitation).press_keyPress a hardware/navigation key: back, home, enter, delete, tab, escape, up, down, left, right, space, power, volup, voldown, recent, menu, wakeup.swipeSwipe from one point to another: in device pixel coordinates, or, with `image_width` and `image_height`, in the pixels of a screenshot of that size.scrollScroll a list/container up, down, left, or right. `ref` must be the ref of the scrollable container itself (a ScrollView or List line in the snapshot), not of a row inside it: scrolling a single row does nothing. If the container has no ref, use swipe() instead.- +9 more on the listing page
Oswright tools 43
screenshotTake a screenshot of the screen or a region. Returns the image as native MCP image content. Optionally saves to a file path. Args: save_path: Optional file path to save the screenshot. region_left: Left coordinate for a sub-region capture. region_top: Top coordinate for a sub-region capture. region_width: Width of the sub-region. region_height: Height of the sub-region. monitor: Monitor index (0 = all monitors, 1 = primary, etc.).get_screen_infoGet screen dimensions and monitor count. Args: monitor: Monitor index (0 = all monitors combined).find_text_on_screenFind all occurrences of text on screen using OCR. Returns a list of matches with coordinates and confidence. Coordinates are absolute screen coordinates, ready to pass straight to mouse_click. Args: text: The text to search for on screen. exact: If True, requires exact match. If False, substring match. region_left: Optional left bound to restrict search area. region_top: Optional top bound to restrict search area. region_width: Optional width to restrict search area. region_height: Optional height to restrict search area. monitor: Monitor index.read_screen_textRead ALL visible text on the screen using OCR. Returns every detected text element with its position, in absolute screen coordinates that are ready to click. Args: region_left: Optional left bound to restrict OCR area. region_top: Optional top bound to restrict OCR area. region_width: Optional width to restrict OCR area. region_height: Optional height to restrict OCR area. monitor: Monitor index.find_image_on_screenFind all occurrences of a template image on screen. Coordinates are absolute screen coordinates, ready to pass to mouse_click. Args: template_path: Absolute path to the template image file to find. threshold: Minimum match confidence (0.0-1.0, default 0.8). monitor: Monitor index.mouse_clickClick the mouse at coordinates or current position. Returns action result and a screenshot of current screen state. Args: x: X screen coordinate. If not provided, clicks at current position. y: Y screen coordinate. If not provided, clicks at current position. button: Mouse button - 'left', 'right', or 'middle'. clicks: Number of clicks (2 for double-click).mouse_double_clickDouble-click at coordinates or current position. Returns action result and a screenshot of current screen state. Args: x: X screen coordinate. y: Y screen coordinate.mouse_moveMove the mouse cursor to screen coordinates. Args: x: X screen coordinate. y: Y screen coordinate.mouse_scrollScroll the mouse wheel. Returns action result and a screenshot of current screen state. Args: amount: Scroll amount. Positive = up, negative = down. x: Optional X coordinate to scroll at. y: Optional Y coordinate to scroll at.mouse_dragDrag from one point to another. Returns action result and a screenshot of current screen state. Args: start_x: Starting X coordinate. start_y: Starting Y coordinate. end_x: Ending X coordinate. end_y: Ending Y coordinate. button: Mouse button to hold ('left' or 'right'). duration: Duration of the drag in seconds.get_mouse_positionGet the current mouse cursor position.type_textType text using the keyboard (character by character). Returns action result and a screenshot of current screen state. Args: text: The text to type. delay: Delay in seconds between each character.- +31 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
ERIUS PHONE
{
"mcpServers": {
"erius-phone": {
"command": "uvx",
"args": [
"erius-phone-mcp"
],
"env": {
"ERIUS_PHONE_API_KEY": "YOUR_ERIUS_PHONE_API_KEY_HERE",
"ERIUS_PHONE_DEFAULT_DEVICE": "YOUR_ERIUS_PHONE_DEFAULT_DEVICE_HERE",
"ERIUS_PHONE_API_URL": "YOUR_ERIUS_PHONE_API_URL_HERE",
"ERIUS_PHONE_TIMEOUT": "YOUR_ERIUS_PHONE_TIMEOUT_HERE"
}
}
}
}
Oswright
{
"mcpServers": {
"oswright": {
"command": "uvx",
"args": [
"oswright"
]
}
}
}
Frequently asked questions
ERIUS PHONE is categorized under OS Automation and uses a local stdio subprocess. Oswright belongs to OS Automation and uses a local stdio subprocess. Pick ERIUS PHONE for os automation work and Oswright for os automation.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
ERIUS PHONE has no declared pricing — check the project's own site. Oswright has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add erius-phone and oswright as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, ERIUS PHONE has a quality signal of 60/100 (Good) with 1 views, 0 installs and 2 GitHub stars. Oswright has 59/100 (Good) with 2 views, 0 installs and 4 GitHub stars.