Web & SearchMCP RegistrymcpbB · 64

agent-in-browser MCP server

Name: agent-in-browser
Author: Gwakko

io.github.Gwakko · Updated 3d ago

Real browser for any agent: Chrome/Edge/Brave via CDP, Firefox via BiDi. Refs, forms, console, net.

At a glance

agent-in-browser is an MCP server in the Web & Search category. It runs locally over stdio via `npx -y https://github.com/Gwakko/agent-in-browser/releases/download/v0.1.2/agent-in-browser-0.1.2.mcpb`, and declares no required credentials. It scores B (64/100) on the MCP Skills Hub health score as of Oct 27, 2026.

Source 0

One-click install

VS Code VS Code Insiders Cursor

Opens your editor and pre-fills the config. Your editor will ask before adding it.

How to install agent-in-browser in your AI client

Setup for Claude Code, Claude Desktop, Cursor, Codex, Windsurf, Cline and VS Code — copy-paste ready.

How to install agent-in-browser in Claude CodeAnthropic's agentic CLI

Add the server

bash

claude mcp add agent-in-browser -- npx -y https://github.com/Gwakko/agent-in-browser/releases/download/v0.1.2/agent-in-browser-0.1.2.mcpb

2
Verify it's connected
bash
```
claude mcp list
```
Sharing it with your team?
Add `--scope project` to write it to .mcp.json in the repository root, which you can commit (with the secrets left as environment variables).
Use it in a session
Ask Claude to use the tools this server exposes. It discovers them automatically.

How to install agent-in-browser in Claude DesktopDesktop app (MCP config)

Open your MCP config
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

Add this server

json

{
  "mcpServers": {
    "agent-in-browser": {
      "command": "npx",
      "args": [
        "-y",
        "https://github.com/Gwakko/agent-in-browser/releases/download/v0.1.2/agent-in-browser-0.1.2.mcpb"
      ]
    }
  }
}

Restart Claude Desktop
The tools appear under the 🔌 menu once the app reloads.

How to install agent-in-browser in CursorAI-first code editor

Create / edit .cursor/mcp.json in your project

json

{
  "mcpServers": {
    "agent-in-browser": {
      "command": "npx",
      "args": [
        "-y",
        "https://github.com/Gwakko/agent-in-browser/releases/download/v0.1.2/agent-in-browser-0.1.2.mcpb"
      ]
    }
  }
}

Enable it
Cursor Settings → MCP → toggle the server on. Tools become available to the Composer/Agent.

How to install agent-in-browser in Codex CLIOpenAI coding agent

Add to ~/.codex/config.toml

toml

[mcp_servers.agent-in-browser]
command = "npx"
args = ["-y", "https://github.com/Gwakko/agent-in-browser/releases/download/v0.1.2/agent-in-browser-0.1.2.mcpb"]

Run Codex
Codex loads MCP servers from config.toml on startup and exposes their tools to the agent.

How to install agent-in-browser in WindsurfCodeium's agentic IDE

Edit ~/.codeium/windsurf/mcp_config.json

json

{
  "mcpServers": {
    "agent-in-browser": {
      "command": "npx",
      "args": [
        "-y",
        "https://github.com/Gwakko/agent-in-browser/releases/download/v0.1.2/agent-in-browser-0.1.2.mcpb"
      ]
    }
  }
}

Reload
Windsurf → Cascade → refresh MCP servers. Cascade can now call the tools.

How to install agent-in-browser in ClineVS Code autonomous agent

Open Cline → MCP Servers → Configure
Adds to cline_mcp_settings.json.

Add the server

json

{
  "mcpServers": {
    "agent-in-browser": {
      "command": "npx",
      "args": [
        "-y",
        "https://github.com/Gwakko/agent-in-browser/releases/download/v0.1.2/agent-in-browser-0.1.2.mcpb"
      ]
    }
  }
}

How to install agent-in-browser in VS CodeCopilot / MCP support

Create .vscode/mcp.json

json

{
  "servers": {
    "agent-in-browser": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "https://github.com/Gwakko/agent-in-browser/releases/download/v0.1.2/agent-in-browser-0.1.2.mcpb"
      ]
    }
  }
}

Start it
VS Code shows a ▶ Start action above the server entry. Agent mode (Copilot Chat) can then use the tools.

What tools does agent-in-browser expose?

This server runs as a local package. We only query remote servers for their tool list — asking this one would mean executing it, so its tools are listed in the documentation below.

What the code can do

The published package could not be downloaded or read for analysis.

Before you install

Signals gathered from the source repo and package registry — not a safety verdict.

What it can reach

Runs code on your machine — Executes as a local process with your user's permissions, including filesystem access.
Downloads at launch — The package is fetched from its registry each run unless you pin a version.

Last commit 3 days ago — Actively maintained.
Repository created 7 days ago — Very new project with little track record yet.
0 GitHub stars — Very little community usage so far.

Client compatibility

Claude Code: NativeClaude Desktop: NativeCursor: NativeCodex CLI: NativeWindsurf: NativeCline: NativeVS Code: Native

Health score

B · 64

Maintenance, adoption, transparency and packaging — not a safety audit. How this is calculated

Maintenance30%100%
Last commit 3 days ago.
Adoption20%0%
0 stars.
Transparency20%75%
3/4: ✓ public source repo, ✓ declared license, ✓ documentation, ✗ discoverable tool list.
Provenance15%75%
Links to its own repository; package linkage unverified.
Packaging15%50%
No pinned version — installs resolve to whatever is latest at launch.

Documentation

Full README

agent-in-browser

A real browser for any AI agent, any model, and any test runner — one dependency-free binary.

<sub>Real recording, not a mock-up. The agent reads the page as a snapshot with element refs, types, fills the form and clicks, first in Chrome (CDP), then in Firefox (WebDriver BiDi). Regenerate it with task demo.</sub>

agent-in-browser is an open take on "Claude in Chrome". It doesn't need an extension or a vendor-specific runtime. It drives the browsers you already have through their native automation protocols:

| Browser | Protocol | Status | |---|---|---| | Chrome, Chrome Beta/Canary, Chromium, Edge, Brave, Vivaldi, Opera | Chrome DevTools Protocol (CDP) | ✅ | | Firefox, Firefox Developer Edition / Nightly | WebDriver BiDi | ✅ | | Safari | WebDriver (safaridriver) | 🛣 detected, roadmap |

It's available three ways, all backed by the same tool catalogue:

MCP server (agent-in-browser mcp): plugs into Claude Code, Claude Desktop, Cursor, Codex, Gemini CLI, Windsurf, VS Code/Copilot, Zed, opencode and any other MCP client, whatever model sits behind it.
Shell CLI (agent-in-browser call <tool> …): for agents without MCP, for scripts, and for humans. Calls share one persistent browser.
Scenario runner (agent-in-browser run test.yaml --browser chrome,firefox): replays tool calls as automated tests across a browser matrix, with JUnit/JSON reports.

An agent skill (`skills/agent-in-browser/SKILL.md`) ships inside the binary and teaches agents the workflow.

Install

bash

# macOS / Linux
curl -fsSL https://raw.githubusercontent.com/Gwakko/agent-in-browser/main/scripts/install.sh | sh

# Windows (PowerShell)
irm https://raw.githubusercontent.com/Gwakko/agent-in-browser/main/scripts/install.ps1 | iex

# Homebrew (macOS / Linux)
brew install gwakko/tap/agent-in-browser

# With Go
go install github.com/gwakko/agent-in-browser/cmd/agent-in-browser@latest

# From a checkout (needs Task: https://taskfile.dev)
task install            # → ~/.local/bin/agent-in-browser + alias `aib`

Connect your agent

bash

agent-in-browser setup claude-code --write    # runs `claude mcp add --scope user …`
agent-in-browser setup cursor --write         # merges ~/.cursor/mcp.json (a .bak is kept)
agent-in-browser setup codex --write          # appends to ~/.codex/config.toml
agent-in-browser setup gemini --write         # ~/.gemini/settings.json
agent-in-browser setup vscode                 # prints the snippet for .vscode/mcp.json
agent-in-browser skill install --for claude   # ~/.claude/skills/agent-in-browser (also: codex, agents, --dir)

Claude Desktop, one click: download agent-in-browser-<version>.mcpb from the latest release and open it. It also appears in the MCP Registry as io.github.Gwakko/agent-in-browser.

Without --write, setup only prints the config. Pass browser options through with --args "--browser firefox --headless". See docs/integrations.md for every client.

Excerpt — the full document is on GitHub.

Alternatives to agent-in-browser

Maintain agent-in-browser? Add a badge to your README

Shows its health grade, and links readers to install steps for every client.

markdown

[![agent-in-browser on MCP Skills Hub](https://mcp-skills-hub.vercel.app/badge/io-github-gwakko-agent-in-browser)](https://mcp-skills-hub.vercel.app/mcps/io-github-gwakko-agent-in-browser)

Catalog data refreshed Oct 27, 2026. Something wrong? Report it.