Chrome Devtools MCP vs Ios Simulator MCP

A side-by-side look at the Chrome Devtools MCP and Ios Simulator MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Chrome Devtools MCP logoChrome Devtools MCPBrowser Automation · Local subprocess (stdio)Chrome DevTools for coding agents65GreatAuth: no auth requiredIos Simulator MCP logoIos Simulator MCPBrowser Automation · Local subprocess (stdio)A Model Context Protocol (MCP) server for interacting with iOS simulators. This server allows you to interact with iOS simulators by getting information about them, controlling UI interactions, and inspecting UI elements.71GreatAuth: no auth required

Verdict: choose Chrome Devtools MCP for browser automation work as a local process; choose Ios Simulator MCP for browser automation as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Chrome Devtools MCP logoChoose Chrome Devtools MCP when

  • You need dedicated capabilities in the Browser Automation domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
  • You want tools like click, drag, fill.
Explore Chrome Devtools MCP

Ios Simulator MCP logoChoose Ios Simulator MCP when

  • You need dedicated capabilities in the Browser Automation domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
  • You want tools like get_booted_sim_id, open_simulator, ui_describe_all.
Explore Ios Simulator MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecChrome Devtools MCP logoChrome Devtools MCPIos Simulator MCP logoIos Simulator MCP
CategoryBrowser AutomationBrowser Automation
Quality signal65/100 · Great71/100 · Great
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNo auth requiredNo auth required
PricingFreeFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars53,9002,193
Directory activity 6 views 0 installs 0 upvotes 4 views 0 installs 0 upvotes
Tools5617

Tools & capabilities

Chrome Devtools MCP tools 56

  • click
  • drag
  • fill
  • fill_form
  • handle_dialog
  • hover
  • press_key
  • type_text
  • upload_file
  • click_at
  • close_page
  • list_pages
  • +44 more on the listing page

Ios Simulator MCP tools 17

  • get_booted_sim_idGet the ID of the currently booted iOS simulator
  • open_simulatorOpens the iOS Simulator application
  • ui_describe_allDescribes accessibility information for the entire screen in the iOS Simulator
  • ui_tapTap on the screen in the iOS Simulator
  • ui_typeInput text into the iOS Simulator
  • ui_swipeSwipe on the screen in the iOS Simulator
  • ui_describe_pointReturns the accessibility element at given co-ordinates on the iOS Simulator's screen
  • ui_find_elementSearches the accessibility tree and returns elements matching the given criteria
  • ui_viewGet the image content of a compressed screenshot of the current simulator view
  • screenshotTakes a screenshot of the iOS Simulator
  • record_videoRecords a video of the iOS Simulator using simctl directly
  • stop_recordingStops the simulator video recording using killall
  • +5 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.

Chrome Devtools MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "chrome-devtools-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "chrome-devtools-mcp"
      ]
    }
  }
}

Ios Simulator MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "ios-simulator-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "ios-simulator-mcp"
      ]
    }
  }
}

Frequently asked questions

Chrome Devtools MCP is categorized under Browser Automation and uses a local stdio subprocess. Ios Simulator MCP belongs to Browser Automation and uses a local stdio subprocess. Pick Chrome Devtools MCP for browser automation work and Ios Simulator MCP for browser 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.

Chrome Devtools MCP is listed as free. Auth: no auth required. Ios Simulator MCP is listed as free. Auth: no auth required. 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 chrome-devtools-mcp and ios-simulator-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Chrome Devtools MCP has a quality signal of 65/100 (Great) with 6 views, 0 installs and 53,900 GitHub stars. Ios Simulator MCP has 71/100 (Great) with 4 views, 0 installs and 2,193 GitHub stars.