Brave DevTools MCP vs Webdriverio MCP

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

Brave DevTools MCP logoBrave DevTools MCPBrowser Automation · Local subprocess (stdio)Full Chrome DevTools MCP parity, rebuilt for Brave. Browser automation and debugging for Claude, Codex, Cursor, and OpenCode.67GreatAuth: not declaredWebdriverio MCP logoWebdriverio MCPBrowser Automation · Local subprocess (stdio)Browser and mobile app automation using WebdriverIO, enabling AI agents to control browsers, interact with web elements, and automate native Android and iOS apps via the WebDriver and Appium protocols.64GoodAuth: not declared

Verdict: choose Brave DevTools MCP for browser automation work as a local process; choose Webdriverio 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?

Brave DevTools MCP logoChoose Brave DevTools MCP when

  • You need dedicated capabilities in the Browser Automation domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like click, close_page, drag.
Explore Brave DevTools MCP

Webdriverio MCP logoChoose Webdriverio MCP when

  • You need dedicated capabilities in the Browser Automation domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like enable_tools, start_session, attach_session.
Explore Webdriverio MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecBrave DevTools MCP logoBrave DevTools MCPWebdriverio MCP logoWebdriverio MCP
CategoryBrowser AutomationBrowser Automation
Quality signal67/100 · Great64/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars4543
Directory activity 0 views 0 installs 0 upvotes 3 views 0 installs 0 upvotes
Tools3240

Tools & capabilities

Brave DevTools MCP tools 32

  • clickClicks on the provided element
  • close_pageCloses the page by its index. The last open page cannot be closed.
  • dragDrag an element onto another element
  • emulateEmulates various features on the target page. Each call replaces all emulation settings (except extraHttpHeaders), so pass all desired settings in a single call.
  • evaluate_scriptEvaluate JavaScript inside the target page. The source can be provided inline or loaded from a local file. Returns the response as JSON, so returned values have to be JSON-serializable.
  • fillType text into an input, text area or select an option from a <select> element.
  • fill_formFill out multiple form elements (inputs, selects, checkboxes, radios) at once. ALWAYS prefer this tool over multiple individual 'fill' or 'click' calls when interacting with forms. It is significantly faster, more reliable, and reduces turn count. Example: Fill username, password, and check "Remember Me" in one call.
  • get_console_messageGets a console message by its ID. You can get all messages by calling list_console_messages.
  • get_css_stylesRetrieve matched CSS rules, inline styles (element.style), inherited styles, custom properties, and cascade wrappers (@layer, @media, @container, @scope) for an element identified by its UID. Rules are ordered from highest to lowest cascade precedence and include source line numbers (e.g. index:196). Active (winning) declarations have no prefix tag, while (losing) overridden declarations are prefixed with [overloaded]. Treat the output as authoritative and complete. Results are paginated (10 rules per page by default); use pageIdx to page through the remaining rules. Requires a UID from take_snapshot.
  • get_network_requestGets a network request by an optional reqid, if omitted returns the currently selected request in the DevTools Network panel. Useful for inspecting request headers (including 'Cookie') and response headers (including 'Set-Cookie' and directives).
  • handle_dialogIf a browser dialog was opened, use this command to handle it
  • hoverHover over the provided element
  • +20 more on the listing page

Webdriverio MCP tools 40

  • enable_toolsAdd a group of tools: `mocks`, `cookies`, `device`, `extensions`, `attach`, `elements`, `cloud-apps
  • start_sessionStart a browser, local Electron application, or mobile app session; `attach: true` retains the existing Chrome CDP connection mode
  • attach_sessionAttach to an existing remote WebDriver/Appium session by ID without creating a new session
  • launch_chromeLaunch a new Chrome instance with remote debugging enabled (for use with `start_session({ attach: true })`)
  • close_sessionClose or detach from the current session (supports `detach: true` to disconnect without terminating)
  • emulate_deviceEmulate a mobile/tablet device preset (viewport, DPR, UA, touch); requires BiDi session
  • open_web_extensionInstall a web extension through WebDriver BiDi and open one of its extension pages so normal page tools can drive its UI
  • navigateNavigate to a URL. In browsers the result shows the new page's interactive elements with refs
  • snapshotThe page as an accessibility tree with refs (`button "Save" [ref=e3]`), interactive elements by default (plain text is dropped, `full: true` shows it); pass refs to `perform_actions` for several steps; `find` returns only the parts containing a text (link targets included), `full: true` adds all te…
  • get_elementsGet visible, interactable elements with bounds. Supports `inViewportOnly` (default: true) and `includeContainers` (default: false). Mobile and Electron; listed after `enable_tools({ groups: ['elements'] })`, use `snapshot` first
  • get_accessibility_treeGet the accessibility tree with roles, names, and selectors. Electron-only; browsers use `snapshot
  • get_screenshotTake a screenshot of the current page or screen (base64-encoded, auto-resized to max 2000px / 1MB)
  • +28 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.

Brave DevTools MCP

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

Webdriverio MCP

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

Frequently asked questions

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

Brave DevTools MCP has no declared pricing — check the project's own site. Webdriverio MCP 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 brave-devtools-mcp and webdriverio-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Brave DevTools MCP has a quality signal of 67/100 (Great) with 0 views, 0 installs and 45 GitHub stars. Webdriverio MCP has 64/100 (Good) with 3 views, 0 installs and 43 GitHub stars.