Log inSubmit server
MCP Browser Agent logo

MCP Browser Agent

by imprvhub

Automates browser interactions and HTTP requests through MCP tools for Claude Desktop.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install MCP Browser Agent

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "imprvhub-mcp-browser-agent": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-browser-agent"
      ],
      "env": {
        "MCP_BROWSER_TYPE": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

We couldn’t confirm it starts correctly

The install command installed and started the server, which then stopped for configuration (such as an API key) that our sandbox does not have — expected for servers that connect to your account.

npx -y mcp-browser-agent

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 16d ago.

Overview

The imprvhub/mcp-browser-agent MCP server gives Claude Desktop browser automation and HTTP request tools through the Model Context Protocol. It runs a persistent Playwright browser session, supports navigation, screenshots, DOM interactions, JavaScript execution, and common HTTP methods. Choose it for multi-step web tasks, form workflows, visual capture, or direct API calls where browser control is needed. It requires Node.js, Playwright dependencies, and a locally configured browser.

Use cases

  • Automate multi-step website navigation
  • Complete web forms and dropdowns
  • Capture full-page or element screenshots
  • Execute JavaScript while inspecting console logs
  • Send HTTP requests to JSON APIs

Key features

  • Playwright browser automation
  • Persistent headful browser session
  • DOM interaction and JavaScript execution
  • Screenshot and console-log MCP resources
  • GET, POST, PUT, PATCH, and DELETE requests
  • Configurable Chrome, Firefox, WebKit, or Edge support

Tools12

What MCP Browser Agent lets your agent do. Expand a tool for its parameters.

Self-reported~81 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

18/18 checks healthy over the last 85d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 16d ago via OSV.dev · mcp-browser-agent (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars43Stargazers on the source repository.
npm downloads52Package downloads in the last 30 days.
Last commit12d agoMost recent push to the default branch.
Install checkRunsOur sandbox started it; it then asked for an API key or config.
Tools exposed12Callable tools this server registers over MCP.
Directory activity8 viewsConfig copies, upvotes, and views on AllMCPs.

How MCP Browser Agent works

What imprvhub/mcp-browser-agent MCP server does

The imprvhub/mcp-browser-agent MCP server exposes browser control and HTTP request operations to an MCP client, with Claude Desktop as the documented client. Browser tools can navigate to URLs, capture screenshots, click elements, fill form fields, choose dropdown options, hover over elements, and execute JavaScript in the browser context. The JavaScript capability also captures console logs.

Separate API tools send GET, POST, PUT, PATCH, and DELETE requests. Requests can include headers and body content, and responses are processed with JSON formatting and error feedback. This combination supports workflows that move between a rendered website and an endpoint exposed by the same or another service.

How it works

The project uses Playwright for browser automation and maintains a persistent, headful browser session. An MCP client sends tool calls to the local process, which performs the requested browser or HTTP operation and returns the result. Screenshots and browser console logs can also be accessed through MCP resources.

The browser can be selected as Chrome, Firefox, WebKit, or Edge. Chrome is the default. WebKit is the rendering engine used in place of direct Safari support. Playwright may install the relevant browser driver when that browser type is first used, or the drivers can be installed manually.

The imprvhub/mcp-browser-agent MCP server is suited to chained tasks such as opening a page, completing a form, submitting it, and capturing the resulting page.

Setup and configuration

The documented prerequisites are Node.js 16 or newer, Claude Desktop, and Playwright dependencies. Installation requires cloning the repository, running npm install, and building with npm run build. The server can then be started from the project directory with node dist/index.js.

Claude Desktop can start the process through its claude_desktop_config.json file. The configuration uses node as the command and points its arguments to the built dist/index.js file, with an optional browser argument such as --browser chrome. The configuration path differs by macOS, Windows, and Linux, so the repository directory must be supplied as an absolute path.

Browser selection is also configurable through .mcp_browser_agent_config.json in the home directory or through the MCP_BROWSER_TYPE environment variable. Supported values are chrome, firefox, webkit, and edge. A command-line --browser option is another supported method.

Tools and capabilities

The imprvhub/mcp-browser-agent MCP server provides these browser tools:

  • browser_navigate for opening a URL with configurable load behavior.
  • browser_screenshot for full-page or element-specific captures.
  • browser_click, browser_fill, browser_select, and browser_hover for DOM interactions.
  • browser_evaluate for running JavaScript in the page and collecting console logs.

Its HTTP tools are api_get, api_post, api_put, api_patch, and api_delete. These support request headers and body content and return formatted response data with error details. MCP resources expose console logs and screenshots.

Limitations and notes

Safari is not directly supported; selecting webkit uses Playwright’s WebKit engine instead. The Edge option launches Microsoft Edge through Playwright’s Edge channel rather than providing a separate browser engine. Browser drivers and the target browser must be available or installed before the corresponding automation can run.

The documented client is Claude Desktop, and the server runs locally rather than through a hosted endpoint.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about MCP Browser Agent

Clone the repository, run npm install, and build it with npm run build. Start the built server with node dist/index.js from the project directory.

Yes.

It supports Chrome, Firefox, WebKit, and Microsoft Edge. WebKit is used instead of direct Safari support, and Chrome is the default.

Set the browser in .mcp_browser_agent_config.json, pass the --browser command-line option, use the MCP_BROWSER_TYPE environment variable, or configure the Claude Desktop arguments.

Yes. It provides tools for GET, POST, PUT, PATCH, and DELETE requests, including configurable headers and request bodies.

Related MCP servers

All in Browser Automation All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewMCP Browser Agent AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/imprvhub-mcp-browser-agent?style=directory)](https://allmcps.com/mcp/imprvhub-mcp-browser-agent)
HTML Embed
<a href="https://allmcps.com/mcp/imprvhub-mcp-browser-agent"><img src="https://allmcps.com/api/badge/imprvhub-mcp-browser-agent?style=directory" alt="MCP Browser Agent on AllMCPs" /></a>