Is io.github.codeChap/agent-browser safe to use?

io.github.codeChap/agent-browser has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.

How do I install io.github.codeChap/agent-browser?

io.github.codeChap/agent-browser supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.

What AI clients work with io.github.codeChap/agent-browser?

io.github.codeChap/agent-browser is compatible with claude-desktop, cursor, claude-code. It uses stdio and http transport.

Is io.github.codeChap/agent-browser actively maintained?

io.github.codeChap/agent-browser is actively maintained — last commit was 28 days ago. It has 1 GitHub stars.

io.github.codeChap/agent-browser

MCP server for browser automation via Vercel's agent-browser CLI

1 GitHub

No known CVEs

No license

Actively maintained

Last commit 28d ago

Works with most clients

Transport: stdio, http

0 tools

Grade F

MCPpedia last refreshed this data 9h ago

Edit this pageView history

io.github.codeChap/agent-browser is an MCP server that MCP server for browser automation via Vercel's agent-browser CLI. Its tool list has not been published yet over stdio and http, requires no API key, and scores 37/100 on MCPpedia's security, maintenance and efficiency rubric.

Browser

Step 1

Install in your client

Config is the same across clients — only the file and path differ.

Supported in Claude Desktopstdio, http · Node 18+

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "agent-browser": {
      "command": "/path/to/mcp-server-agent-browser"
    }
  }
}

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/io-github-codechap-agent-browser)](https://mcppedia.org/s/io-github-codechap-agent-browser)

Read me

What io.github.codeChap/agent-browser does

Status: Testing — Functional but still being validated. Expect rough edges.

Test This Server

No automated test available for this server. Check the GitHub README for setup instructions.

Loading README…

Scored, not listed

Why this score

Five weighted categories — click any category to see the underlying evidence.

Score breakdown

37/100across 5 weighted dimensions

How we score →

0255075100

−63

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

No known CVEs.

No package registry to scan.

Community

Reviews

Be the first to review

Have you used this server?

Share your experience — it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is io.github.codeChap/agent-browser safe to use?: io.github.codeChap/agent-browser has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.
How do I install io.github.codeChap/agent-browser?: io.github.codeChap/agent-browser supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.
What AI clients work with io.github.codeChap/agent-browser?: io.github.codeChap/agent-browser is compatible with claude-desktop, cursor, claude-code. It uses stdio and http transport.
Is io.github.codeChap/agent-browser actively maintained?: io.github.codeChap/agent-browser is actively maintained — last commit was 28 days ago. It has 1 GitHub stars.

Similar servers

Others in browser

View all →

Chrome Devtools Mcp96

Chrome DevTools for coding agents

49.6k 10

Browser Tools Mcp96

Monitor browser logs directly from Cursor and other MCP compatible IDEs.

7.3k 7

Firecrawl Mcp Server95

🔥 Official Firecrawl MCP Server - Adds powerful web scraping and search to Cursor, Claude and any other LLM clients.

7.3k 4

Browser Control Mcp95

MCP server paired with a browser extension that enables AI agents to control the user's browser.

316 2

MCP Security Weekly

Get CVE alerts and security updates for io.github.codeChap/agent-browser and similar servers.

Community

Discussion

Start a conversation

Ask a question, share a tip, or report an issue.

Has anyone used this with Cursor?How do you handle auth?Any alternatives?

Edit this pageView history

Browser

Step 1

Install in your client

Config is the same across clients — only the file and path differ.

Supported in Claude Desktopstdio, http · Node 18+

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "agent-browser": {
      "command": "/path/to/mcp-server-agent-browser"
    }
  }
}

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/io-github-codechap-agent-browser)](https://mcppedia.org/s/io-github-codechap-agent-browser)

Read me

What io.github.codeChap/agent-browser does

Status: Testing — Functional but still being validated. Expect rough edges.

Test This Server

No automated test available for this server. Check the GitHub README for setup instructions.

README

mcp-server-agent-browser

Status: Testing — Functional but still being validated. Expect rough edges.

Let LLMs drive a real browser. This MCP server wraps agent-browser (by Vercel Labs) so any MCP-compatible client — Claude Desktop, Claude Code, or others — can navigate pages, fill forms, click buttons, take screenshots, and more.

Prerequisites

Install the agent-browser CLI:

cargo install agent-browser
agent-browser install

Build

cargo build --release

Binary: target/release/mcp-server-agent-browser

Configuration

Add to your MCP client config (example for Claude Desktop / Claude Code):

{
  "mcpServers": {
    "agent-browser": {
      "command": "/path/to/mcp-server-agent-browser"
    }
  }
}

The server communicates over stdio using JSON-RPC 2.0 — it works with any MCP client.

Environment Variable	Description	Default
`AGENT_BROWSER_PATH`	Path to the `agent-browser` binary	`agent-browser` (via `$PATH`)

What it can do

The server exposes 35+ tools covering:

Navigation — open URLs, go back/forward, reload
Interaction — click, type, fill, press keys, hover, scroll, drag, select, check/uncheck, upload, download
Reading — get page text, HTML, attributes, URL, title
Accessibility — browser_snapshot returns an accessibility tree with @ref identifiers that can be used as selectors in subsequent calls
State — check if elements are visible, enabled, or checked
Capture — screenshots (with optional annotation for vision models) and PDF export
Sessions — create isolated browser sessions with independent cookies/storage/viewport
Cookies — get, set, clear
JavaScript — evaluate arbitrary JS in the page context
DevTools — read console logs, inspect network requests, connect via CDP

Each tool is self-documented with parameter schemas — your MCP client will discover them automatically.

How it works

A typical AI-driven interaction follows this pattern:

browser_navigate — open a page
browser_snapshot — get the accessibility tree to understand the page structure
browser_click / browser_fill — interact using @ref selectors from the snapshot
browser_screenshot — visually verify the result

The agent decides which tools to call and in what order. You just describe what you want done.

Sessions

All tools accept an optional session_id. Create isolated sessions with browser_new_session and pass the returned ID to subsequent calls. Each session has its own cookies, storage, and viewport. Without a session ID, commands use the default session.

Timeouts

Commands time out after 60 seconds by default. The browser_wait tool adjusts its timeout automatically based on the wait duration you specify.

Limitations

Requires the Rust toolchain to build, and Node.js for the agent-browser daemon
Chromium only — agent-browser uses Playwright under the hood
Headless by default — no visible browser window
The 60-second default timeout may not be enough for slow pages or complex interactions
No built-in authentication persistence — cookies reset between server restarts unless managed via the cookie tools
File upload/download paths are validated but restricted from system directories

License

MIT

Loading README…

Scored, not listed

Why this score

Five weighted categories — click any category to see the underlying evidence.

Score breakdown

37/100across 5 weighted dimensions

How we score →

0255075100

−63

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

No known CVEs.

No package registry to scan.

Community

Reviews

Be the first to review

Have you used this server?

Share your experience — it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is io.github.codeChap/agent-browser safe to use?: io.github.codeChap/agent-browser has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.
How do I install io.github.codeChap/agent-browser?: io.github.codeChap/agent-browser supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.
What AI clients work with io.github.codeChap/agent-browser?: io.github.codeChap/agent-browser is compatible with claude-desktop, cursor, claude-code. It uses stdio and http transport.
Is io.github.codeChap/agent-browser actively maintained?: io.github.codeChap/agent-browser is actively maintained — last commit was 28 days ago. It has 1 GitHub stars.