Chrome Devtools MCP vs Openbrowser AI

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

Chrome Devtools MCP logoChrome Devtools MCPBrowser Automation · Local subprocess (stdio)Chrome DevTools for coding agents65GreatAuth: no auth requiredOpenbrowser AI logoOpenbrowser AIBrowser Automation · Local subprocess (stdio)AI browser automation. Write async Python to navigate, click, type, and extract data.47FairAuth: not declared

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

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

Openbrowser AI logoChoose Openbrowser AI when

  • You need dedicated capabilities in the Browser Automation domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: GOOGLE_API_KEY, OPENAI_API_KEY, ANTHROPIC_API_KEY, GROQ_API_KEY, AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_DEFAULT_REGION, AZURE_OPENAI_API_KEY.
Explore Openbrowser AI

Feature & specification comparison

Rows where the two servers differ are marked.

SpecChrome Devtools MCP logoChrome Devtools MCPOpenbrowser AI logoOpenbrowser AI
CategoryBrowser AutomationBrowser Automation
Quality signal65/100 · Great47/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNo auth requiredNot declared
PricingFreeNot declared
Required env varsNone listedGOOGLE_API_KEYOPENAI_API_KEYANTHROPIC_API_KEYGROQ_API_KEYAWS_ACCESS_KEY_IDAWS_SECRET_ACCESS_KEYAWS_DEFAULT_REGIONAZURE_OPENAI_API_KEY
Verified ownerCommunity listingCommunity listing
GitHub stars53,900277
Directory activity 6 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
Tools56Not listed

Tools & capabilities

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

Openbrowser AI tools

No tool names declared yet. Check the project README from 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.

Chrome Devtools MCP

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

Openbrowser AI

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "openbrowser-ai": {
      "command": "uvx",
      "args": [
        "openbrowser-ai"
      ],
      "env": {
        "GOOGLE_API_KEY": "YOUR_GOOGLE_API_KEY_HERE",
        "OPENAI_API_KEY": "YOUR_OPENAI_API_KEY_HERE",
        "ANTHROPIC_API_KEY": "YOUR_ANTHROPIC_API_KEY_HERE",
        "GROQ_API_KEY": "YOUR_GROQ_API_KEY_HERE",
        "AWS_ACCESS_KEY_ID": "YOUR_AWS_ACCESS_KEY_ID_HERE",
        "AWS_SECRET_ACCESS_KEY": "YOUR_AWS_SECRET_ACCESS_KEY_HERE",
        "AWS_DEFAULT_REGION": "YOUR_AWS_DEFAULT_REGION_HERE",
        "AZURE_OPENAI_API_KEY": "YOUR_AZURE_OPENAI_API_KEY_HERE"
      }
    }
  }
}

Frequently asked questions

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

Chrome Devtools MCP is listed as free. Auth: no auth required. Openbrowser AI 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 chrome-devtools-mcp and openbrowser-ai as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Chrome Devtools MCP has a quality signal of 65/100 (Great) with 6 views, 0 installs and 53,900 GitHub stars. Openbrowser AI has 47/100 (Fair) with 1 views, 0 installs and 277 GitHub stars.