Brave DevTools MCP vs MCP Server Browser

A side-by-side look at the Brave DevTools MCP and MCP Server Browser 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 declaredMCP Server Browser logoMCP Server BrowserBrowser Automation · Local subprocess (stdio)Browser automation capabilities using Puppeteer, both support local and remote browser connection.67GreatAuth: no auth required

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

MCP Server Browser logoChoose MCP Server Browser 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 browser_click, browser_close, browser_close_tab.
Explore MCP Server Browser

Feature & specification comparison

Rows where the two servers differ are marked.

SpecBrave DevTools MCP logoBrave DevTools MCPMCP Server Browser logoMCP Server Browser
CategoryBrowser AutomationBrowser Automation
Quality signal67/100 · Great67/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 stars4539,379
Directory activity 0 views 0 installs 0 upvotes 6 views 0 installs 0 upvotes
Tools3223

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

MCP Server Browser tools 23

  • browser_clickClick an element on the page, before using the tool, use `browser_get_clickable_elements` to get the index of the element, but not call `browser_get_clickable_elements` multiple times
  • browser_closeClose the browser when the task is done and the browser is not needed anymore
  • browser_close_tabClose the current tab
  • browser_evaluateExecute JavaScript in the browser console
  • browser_form_input_fillFill out an input field, before using the tool, Either 'index' or 'selector' must be provided
  • browser_get_clickable_elementsGet the clickable or hoverable or selectable elements on the current page, don't call this tool multiple times
  • browser_get_download_listGet the list of downloaded files
  • browser_get_markdownGet the markdown content of the current page
  • browser_get_textGet the text content of the current page
  • browser_go_backGo back to the previous page
  • browser_go_forwardGo forward to the next page
  • browser_hoverHover an element on the page, Either 'index' or 'selector' must be provided
  • +11 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"
      ]
    }
  }
}

MCP Server Browser

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "agent-infra-mcp-server-browser": {
      "command": "npx",
      "args": [
        "-y",
        "@agent-infra/mcp-server-browser"
      ]
    }
  }
}

Frequently asked questions

Brave DevTools MCP is categorized under Browser Automation and uses a local stdio subprocess. MCP Server Browser belongs to Browser Automation and uses a local stdio subprocess. Pick Brave DevTools MCP for browser automation work and MCP Server Browser 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. MCP Server Browser 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 brave-devtools-mcp and agent-infra-mcp-server-browser 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. MCP Server Browser has 67/100 (Great) with 6 views, 0 installs and 39,379 GitHub stars.