Brave DevTools MCP vs Agent Webbridge

A side-by-side look at the Brave DevTools MCP and Agent Webbridge 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 declaredAgent Webbridge logoAgent WebbridgeBrowser Automation · Local subprocess (stdio)Drive your real, logged-in Chrome (many profiles, parallel tabs) from any MCP client. Local only.59GoodAuth: not declared

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

Agent Webbridge logoChoose Agent Webbridge when

  • You need dedicated capabilities in the Browser Automation domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like navigate, find_tab, evaluate.
Explore Agent Webbridge

Feature & specification comparison

Rows where the two servers differ are marked.

SpecBrave DevTools MCP logoBrave DevTools MCPAgent Webbridge logoAgent Webbridge
CategoryBrowser AutomationBrowser Automation
Quality signal67/100 · Great59/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 stars4512
Directory activity 0 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
Tools3215

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

Agent Webbridge tools 15

  • navigateOpen a URL in a new or existing tab
  • find_tabLocate a tab by URL / title
  • evaluateRun JavaScript in the page, return the result
  • snapshotAccessibility tree with stable `@e` element refs
  • clickClick an element by `@e` ref (synthetic DOM click)
  • trusted_clickReal mouse click (CDP, `isTrusted`) for pages that ignore `click
  • fillSet native inputs **and** `contenteditable` rich text fields
  • uploadProgrammatically assign files to `<input type="file">
  • file_chooser_interceptSuppress native OS file picker dialogs (Finder/Explorer) during programmatic upload
  • screenshotCapture full-page or element screenshot directly to disk
  • save_as_pdfSave the page as a PDF
  • networkCapture network requests (`start`, `stop`, `list`, `detail`)
  • +3 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"
      ]
    }
  }
}

Agent Webbridge

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

Frequently asked questions

Brave DevTools MCP is categorized under Browser Automation and uses a local stdio subprocess. Agent Webbridge belongs to Browser Automation and uses a local stdio subprocess. Pick Brave DevTools MCP for browser automation work and Agent Webbridge 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. Agent Webbridge 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 agent-webbridge 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. Agent Webbridge has 59/100 (Good) with 1 views, 0 installs and 12 GitHub stars.