Agent Webbridge vs Chrome Devtools MCP

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

Agent 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 declaredChrome Devtools MCP logoChrome Devtools MCPBrowser Automation · Local subprocess (stdio)Chrome DevTools for coding agents65GreatAuth: no auth required

Verdict: choose Agent Webbridge for browser automation work as a local process; choose Chrome Devtools 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?

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

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

Feature & specification comparison

Rows where the two servers differ are marked.

SpecAgent Webbridge logoAgent WebbridgeChrome Devtools MCP logoChrome Devtools MCP
CategoryBrowser AutomationBrowser Automation
Quality signal59/100 · Good65/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 stars1253,900
Directory activity 1 views 0 installs 0 upvotes 6 views 0 installs 0 upvotes
Tools1556

Tools & capabilities

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

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

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.

Agent Webbridge

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

Chrome Devtools MCP

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

Frequently asked questions

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

Agent Webbridge has no declared pricing — check the project's own site. Chrome Devtools 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 agent-webbridge and chrome-devtools-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Agent Webbridge has a quality signal of 59/100 (Good) with 1 views, 0 installs and 12 GitHub stars. Chrome Devtools MCP has 65/100 (Great) with 6 views, 0 installs and 53,900 GitHub stars.