MCP Browser Dev Tools vs Agent Webbridge

A side-by-side look at the MCP Browser Dev Tools and Agent Webbridge 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 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 MCP Browser Dev Tools 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?

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

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.

SpecMCP Browser Dev Tools logoMCP Browser Dev ToolsAgent Webbridge logoAgent Webbridge
CategoryBrowser AutomationBrowser Automation
Quality signal53/100 · Good59/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 stars112
Directory activity 1 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
Tools4515

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

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.

MCP Browser Dev Tools

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

Agent Webbridge

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

Frequently asked questions

MCP Browser Dev Tools is categorized under Browser Automation and uses a local stdio subprocess. Agent Webbridge belongs to Browser Automation and uses a local stdio subprocess. Pick MCP Browser Dev Tools 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.

MCP Browser Dev Tools 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 mcp-browser-dev-tools and agent-webbridge 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. Agent Webbridge has 59/100 (Good) with 1 views, 0 installs and 12 GitHub stars.