MCP Browser Dev Tools vs Scrcpy MCP

A side-by-side look at the MCP Browser Dev Tools and Scrcpy MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

MCP Browser Dev Tools logoMCP Browser Dev ToolsBrowser Automation · Local subprocess (stdio)Browser MCP server for AI agents: batch actions, waits, and checks into one call on Chrome, Edge, or Firefox (CDP and WebDriver BiDi)53GoodAuth: not declaredScrcpy MCP logoScrcpy MCPBrowser Automation · Local subprocess (stdio)MCP server for Android device control via ADB and scrcpy69GreatAuth: no auth required

Verdict: choose MCP Browser Dev Tools for browser automation work as a local process; choose Scrcpy 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?

MCP Browser Dev Tools logoChoose MCP Browser Dev Tools when

  • You need dedicated capabilities in the Browser Automation domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like browser_status, ensure_browser, launch_browser.
Explore MCP Browser Dev Tools

Scrcpy MCP logoChoose Scrcpy 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 start_session, stop_session, version.
Explore Scrcpy MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecMCP Browser Dev Tools logoMCP Browser Dev ToolsScrcpy MCP logoScrcpy MCP
CategoryBrowser AutomationBrowser Automation
Quality signal53/100 · Good69/100 · Great
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars1122
Directory activity 1 views 0 installs 0 upvotes 6 views 0 installs 0 upvotes
Tools4539

Tools & capabilities

MCP Browser Dev Tools tools 45

  • browser_status
  • ensure_browser
  • launch_browser
  • list_tabs
  • new_tab
  • close_tab
  • attach_tab
  • detach_tab
  • list_sessions
  • navigate
  • reload
  • click
  • +33 more on the listing page

Scrcpy MCP tools 39

  • start_sessionStart a scrcpy session for fast input control and screenshots. When a session is active, tap/swipe/text/screenshot are 10-50x faster. Requires scrcpy-server to be installed.
  • stop_sessionStop the active scrcpy session. Tools will fall back to ADB commands.
  • versionReport which scrcpy version is being used by the MCP server. The version always describes the scrcpy-server file the session pushes: it comes from the SCRCPY_SERVER_VERSION environment variable, or from the scrcpy client belonging to the same install as that server, or a built-in default.
  • device_listList all connected Android devices with their serial numbers, state, and model
  • device_infoGet detailed info about a device: model, Android version, screen size, SDK level, battery level
  • screen_onWake the device screen (turn screen on)
  • screen_offTurn the device screen off
  • connect_wifiEnable WiFi ADB and connect to the device wirelessly. Returns the connection address.
  • disconnect_wifiDisconnect from a wireless ADB device
  • rotate_deviceRotate the device screen (requires active scrcpy session)
  • expand_notificationsExpand the notification panel (requires active scrcpy session)
  • expand_settingsExpand the quick settings panel (requires active scrcpy session)
  • +27 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.

MCP Browser Dev Tools

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

Scrcpy MCP

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

Frequently asked questions

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

MCP Browser Dev Tools has no declared pricing — check the project's own site. Scrcpy 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 mcp-browser-dev-tools and scrcpy-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, MCP Browser Dev Tools has a quality signal of 53/100 (Good) with 1 views, 0 installs and 1 GitHub stars. Scrcpy MCP has 69/100 (Great) with 6 views, 0 installs and 122 GitHub stars.