The short answer: on a Mac, for an iPhone or iPad simulator only, a local option is quickest. That means ios-simulator-mcp, XcodeBuildMCP or Claude Code Desktop's simulator pane. On your own machine, agent-device, mobile-mcp and Argent drive both iOS and Android, and agent-device and Argent also drive Apple TV and Android TV. If you have no Mac, your agent runs in the cloud, or you test on Roku, pick a server backed by hosted devices. That is the part VibeView covers, so we start there. Jump to the table or how to choose.

VibeView: cloud devices behind a local MCP server

Disclosure: this section is about our own product. The rest of the page draws only on each project's own docs. The Sources list at the end has every link and the date we read it.

  • Devices. iPhone and iPad simulators, Android phone and tablet emulators, Apple TV, Android TV and Roku, all in the cloud. Roku is physical hardware; the rest are simulators and emulators.
  • Connection. A local stdio MCP server. Your client runs npx -y vibeview mcp on your machine, and that server talks to our cloud devices. Claude Code, Cursor, Codex, Claude Desktop and VS Code all point at the same local command.
  • No Mac needed. The server needs Node, not Xcode, so it works from Windows, Linux or a Mac. Cloud builds can also build the simulator or emulator app for you.
  • The full loop. The agent uploads a build, starts a device and reads the screen as a tree of element references. It taps, types and presses remote buttons, then stops the device. It can save what it checked as a test to rerun later. Test runs that use AI are in beta. On Roku it can repackage and reload the channel after an edit.
  • Human takeover. Each session has a live page where you watch the agent and drive the device yourself, for example to enter a 2FA code or solve a CAPTCHA.

Our limits: we do not offer a hosted MCP URL, so an agent in a cloud sandbox needs Node and network access there. Sessions use your plan's streaming minutes. Free sessions end after 5 minutes each. No phone or tablet is a physical handset.

Local or hosted: the choice that matters most

Every MCP server on this list speaks the same protocol. They differ in where the device lives and where the server process runs.

  • Local server, local devices. The server runs on your computer and drives simulators and emulators you installed. Most are open source and install with one command. iOS needs a Mac with Xcode, because Apple's simulator runs only on macOS. Android needs the Android SDK. Each device uses your own CPU and memory.
  • Local server, cloud devices. The server still runs on your computer, but the devices are rented. VibeView works this way, and so does agent-device with its cloud backends. Mobile Next Cloud (mobile-mcp's "same tools, no local setup") and Argent Cloud (hosted iOS simulators) also rent devices.
  • Hosted server. You add a URL to your client and sign in. Limrun, BrowserStack and Sauce Labs offer this, and so does Expo, though its device tools still run locally. It suits agents that run in a cloud sandbox and can't start a local process.

The list at a glance

ServerWhere it runsDevices it drivesTVNeeds a MacPrice
VibeView (ours)Local stdio server, cloud devicesiOS simulators, Android emulatorsApple TV, Android TV, RokuNoFree tier, then plans
mobile-mcpLocal (stdio or HTTP); optional Mobile Next Cloud devicesiOS simulators and iPhones, Android emulators and phonesNone listedFor Apple targetsOpen source (Apache-2.0)
ios-simulator-mcpLocaliOS simulatorsNoYesOpen source (MIT)
XcodeBuildMCP (MobileBuildMCP)Local stdioApple simulators (UI automation off by default)None listed (builds tvOS apps)YesOpen source (MIT)
agent-deviceLocal stdio; optional device cloudsiOS, Android and HarmonyOS simulators, emulators and devices; web; desktopApple TV, Android TV, Fire TV, VegaFor Apple targetsOpen source (MIT)
ArgentLocal; optional Argent CloudiOS simulators and iPhones, Android emulators and devicesApple TV, Android TV, Fire TV (Vega)For Apple targetsOpen source (Apache-2.0, some binaries proprietary); Argent Cloud $299/month per runner
Expo MCPHosted (OAuth); device tools localYour running app on a simulator or emulator, through your dev serverNone listedFor iOS device toolsExpo account; one tool needs a paid plan
LimrunHosted, plus one server per deviceCloud iOS simulators, Android emulatorsNone listedNoCredits; $20/month entry plan
BrowserStack MCPHosted or localPhysical phones and tabletsNone listedNoBrowserStack plan
Sauce MCPHostedPhysical phones and tablets (Private Devices only)None listedNoPaid add-on
Claude Code Desktop paneBuilt into the desktop app (not an MCP server)iPhone and iPad simulatorsNoYesPaid Claude plans

Servers that drive devices on your own machine

mobile-mcp

Mobile Next's server drives iOS simulators, Android emulators and physical phones on both platforms. It runs over stdio by default and can also listen over HTTP. It needs Xcode command line tools for iOS and Android Platform Tools for Android, and its README lists Android emulators on Linux, Windows and macOS. No TV device is listed. Mobile Next Cloud offers physical iOS and Android devices with the same tools and "no local setup".

ios-simulator-mcp

Joshua Yoes's small, focused server for iOS simulators. It reads the screen's accessibility tree, taps, swipes, types, takes screenshots and records video. It needs macOS, Xcode and Facebook's IDB. Update to 1.3.3 or later: older versions had a command-injection bug.

XcodeBuildMCP (now MobileBuildMCP)

Sentry's server is about the build, not just the screen. It builds, runs, tests and debugs Xcode projects for iOS, iPadOS, macOS, watchOS, tvOS and visionOS. Its UI automation workflow inspects the app and performs gestures on a simulator, but it is off by default: only the simulator workflow is on until you enable more. It needs macOS 14.5 or later and Xcode 16 or later. You can pair it with ios-simulator-mcp: this one to build and debug, the other to tap through the app.

agent-device

Callstack's agent-device is a command-line tool with an MCP server built in. It drives iOS, Android and HarmonyOS simulators, emulators and devices, plus Apple TV, Android TV, Fire TV and Amazon's Vega Virtual Device. It needs Xcode for iOS and the Android SDK for Android and Android TV. It can also drive cloud devices from BrowserStack, AWS Device Farm, TestMu AI and Limrun, whose devices are iOS simulators and Android emulators. It does not cover Roku.

Argent

Software Mansion's MCP server drives iOS simulators, physical iPhones, Android emulators and devices, Apple TV, Android TV and Fire TV. Roku is not listed. Its source is Apache-2.0, but some bundled binaries are proprietary. Argent Cloud rents iOS simulators only: $299 a month per runner, and each runner runs up to six simulators at once.

Hosted servers and cloud devices

Expo MCP

Expo's server is hosted: you add its URL and sign in with your Expo account. The hosted tools cover docs, builds and workflows on Expo's build service (EAS), TestFlight crashes and store reviews. The tools that tap and screenshot a device are local. They need Expo SDK 54 or later and a running dev server. On iOS they work on simulators only, and only on a Mac. Expo doesn't document TV testing for these tools. Expo marks one tool, documentation search, as needing a paid EAS plan.

Limrun

Each Limrun iOS simulator and Android emulator runs its own MCP server. A remote server for your organization, which you sign in to with OAuth, can create and delete those devices. Its device tools take a batch of actions in one call. Pricing is in credits: a trial gives 120, and the Entry plan is $20 a month for 500. An iOS minute costs 2 credits and an Android minute 1. No TV device is listed.

BrowserStack MCP

BrowserStack runs a remote server and also ships a local one. It reaches physical phones and tablets for App Automate (automated app tests) and App Profiling. The remote server can't reach apps behind a firewall or on localhost; that needs the local server. You need a BrowserStack account. No TV device is listed.

Sauce MCP

Sauce Labs hosts its server. An agent can start physical-device sessions, install and launch apps, take screenshots and read the UI. Sauce's docs say mobile device features currently work only with Private Devices through its Access API, a paid add-on to its physical-device cloud. No TV device is listed.

Two that aren't MCP servers

Claude Code Desktop's iOS Simulator pane. For Mac users, it is the simplest alternative to installing a server. It is a public beta, in Claude Code Desktop on macOS only. It needs Xcode, drives iPhone and iPad simulators, and works in local sessions only, not cloud or SSH sessions. Claude can tap, type and take screenshots once you allow it. From the CLI, Claude reaches the simulator through computer use instead.

Appetize. Appetize, which streams simulators in the browser, gives agents a command-line tool (in beta) and an agent skill. Its AI agent docs don't mention an MCP server.

How to choose

  1. A Mac, iOS only, working at your desk: the Claude Code Desktop pane, or ios-simulator-mcp with XcodeBuildMCP.
  2. A Mac, iOS and Android, devices you run yourself: agent-device, mobile-mcp or Argent.
  3. Linux or Windows, Android only, on your own machine: mobile-mcp documents both.
  4. Apple TV or Android TV on your own machine: agent-device or Argent (Apple TV needs a Mac).
  5. No Mac but you need iOS, or your agent runs in the cloud: a server backed by cloud devices, such as VibeView or Limrun, or Argent Cloud for hosted iOS simulators.
  6. Physical phones you don't have on hand: BrowserStack, Sauce Labs or Mobile Next Cloud. For phones on your desk, mobile-mcp drives them over USB, and agent-device and Argent also list physical devices.
  7. Roku, or TV without setting up simulators yourself: VibeView.

Sources

Each page below was opened on October 23, 2026.

Published October 23, 2026 · Third-party details checked against each project's own pages on October 23, 2026