Supports browser automation in Firefox, allowing for navigation, DOM manipulation, form filling, and JavaScript execution through Playwright.
Demonstrated capability to navigate to Google, perform searches, and interact with search results through browser automation.
Enables execution of arbitrary JavaScript code in browser context, with the ability to capture console logs and return results.
Click on any timestamp to jump to that section of the video
00:00 - Google Search for MCP
Navigation to Google homepage and search for "Model Context Protocol". Demonstration of Claude Desktop using the MCP integration to perform a basic web search and process the results.
00:33 - Screenshot Capture
Taking a screenshot of the search results with a custom filename and showcasing it in Finder. Shows how Claude can capture and save visual content from web pages during browser automation.
01:00 - Wikipedia Search
Navigation to Wikipedia.org and search for "Model Context Protocol". Illustrates Claude's ability to interact with different websites and their search functionality through the MCP integration.
01:38 - Dropdown Menu Interaction I
Navigation to a test website (the-internet.herokuapp.com/dropdown) and selection of "Option 1" from a dropdown menu. Demonstrates Claude's capability to interact with form elements and make selections.
01:56 - Dropdown Menu Interaction II
Changing the selection to "Option 2" from the same dropdown menu. Shows Claude's ability to manipulate the same form element multiple times and make different selections.
02:09 - Login Form Completion
Navigation to a login page (the-internet.herokuapp.com/login) and filling in the username field with "tomsmith" and password field with "SuperSecretPassword!". Demonstrates form filling automation.
02:28 - Login Submission
Submitting the login credentials and completing the authentication process. Shows Claude's ability to trigger form submissions and navigate through multi-step processes.
02:36 - API Request Execution
Performing a GET request to JSONPlaceholder API endpoint. Demonstrates Claude's capability to make direct API calls and process the returned data through the MCP integration.
This package includes Playwright and the necessary dependencies for running browser automation. When you run npm install, the required Playwright dependencies will be installed. The package supports the following browsers:
When you first use a browser type, Playwright will automatically install the corresponding browser drivers as needed. You can also install them manually with the following commands:
Note about Safari: Playwright doesn't provide direct support for Safari browser. Instead, it uses WebKit, which is the browser engine that powers Safari.
Note about Edge: When selecting Edge as the browser type, the agent will actually launch Microsoft Edge (not Chromium). Technically, in Playwright, Edge is launched using the Chromium browser instance with the 'msedge' channel parameter because Microsoft Edge is based on Chromium.
There are two ways to run the MCP server:
Keep this terminal window open while using Claude Desktop. The server will run until you close the terminal.
The Claude Desktop can automatically start the MCP server when needed. To set this up:
The Claude Desktop configuration file is located at:
~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.json~/.config/Claude/claude_desktop_config.jsonEdit this file to add the Browser Agent MCP configuration. If the file doesn't exist, create it:
Important: Replace ABSOLUTE_PATH_TO_DIRECTORY with the complete absolute path where you installed the MCP
/Users/username/mcp-browser-agentC:\\Users\\username\\mcp-browser-agentIf you already have other MCPs configured, simply add the "browserAgent" section inside the "mcpServers" object. Here's an example of a configuration with multiple MCPs:
The MCP Browser Agent supports multiple browser types. By default, it uses Chrome, but you can specify a different browser in several ways:
Create or edit the file .mcp_browser_agent_config.json in your home directory:
Supported values for browserType are:
chrome - Uses installed Chrome (default)firefox - Uses Firefox 'Nightly' browserwebkit - Uses WebKit engine (Note: This is not Safari itself but the WebKit rendering engine that powers Safari)edge - Uses Microsoft EdgeNote about Safari: Playwright doesn't provide direct support for Safari browser. Instead, it uses WebKit, which is the browser engine that powers Safari. The WebKit implementation in Playwright provides similar functionality but is not identical to the Safari browser experience.
When starting the MCP server manually, you can specify the browser type:
Set the MCP_BROWSER_TYPE environment variable:
When configuring the MCP in Claude Desktop's claude_desktop_config.json, you can specify the browser type:
MCP Browser Agent is built on the Model Context Protocol, enabling Claude to interact with a headful browser through Playwright. The implementation consists of four main components:
Unlike basic integrations, MCP Browser Agent functions as a true AI agent by:
| Tool Name | Description | Parameters |
|---|---|---|
browser_navigate | Navigate to a URL | url (required), timeout, waitUntil |
browser_screenshot | Capture screenshot | name (required), selector, fullPage, mask, savePath |
browser_click | Click element | selector (required) |
browser_fill | Fill form input | selector (required), value (required) |
browser_select | Select dropdown option | selector (required), value (required) |
browser_hover | Hover over element | selector (required) |
browser_evaluate | Execute JavaScript | script (required) |
| Tool Name | Description | Parameters |
|---|---|---|
api_get | GET request | url (required), headers |
api_post | POST request | url (required), data (required), headers |
api_put | PUT request | url (required), data (required), headers |
api_patch | PATCH request | url (required), data (required), headers |
api_delete | DELETE request | url (required), headers |
The MCP Browser Agent exposes the following resources:
browser://logs - Access browser console logsscreenshot://[name] - Access screenshots by nameHere are some realistic examples of how to use the MCP Browser Agent with Claude:
These examples represent the actual capabilities of the MCP Browser Agent and are more realistic about what it can accomplish in its current state.
If you see the error "MCP Browser Agent: Server disconnected" in Claude Desktop:
node dist/index.js from the project directoryclaude_desktop_config.json is correct for your system\\) for Windows pathsIf the browser doesn't launch or you don't see it:
There are known issues with Chromium and Chrome browsers where the process sometimes doesn't terminate properly after use. If you experience this issue:
ps aux | grep chrome or ps aux | grep chromium to find the process, then kill <PID> to terminate itCaution
This MCP integration is built on Playwright, which has known issues and bugs that may affect its operation. Please report any issues you encounter with the browser automation to Playwright's GitHub issues. The Playwright team is continuously working to address these issues, but this agent provides a foundation for browser automation capabilities with Claude Desktop despite these limitations.
src/index.ts: Main entry point and MCP server initializationsrc/tools.ts: Tool schemas and registrationsrc/handlers.ts: MCP request handlers for tools and resourcessrc/executor.ts: Tool implementation logic using PlaywrightThe project includes tests to verify core functionality and browser handling.
Tests verify configuration integrity, browser automation features, error handling, and process cleanup. The test suite focuses particularly on ensuring proper handling of browser processes due to known issues with Chrome/Chromium termination.
Caution
This MCP integration provides Claude with autonomous browser control capabilities. Please review our Security Policy for important information about prohibited uses, security implications, and best practices.
The MCP Browser Agent is designed for legitimate automation tasks but could potentially be misused. Users are responsible for ensuring their use complies with all applicable laws, terms of service, and ethical guidelines. See our detailed Security Policy for more information.
Contributions to the MCP Browser Agent are welcome! Here are some areas where you can help:
This project is licensed under the Mozilla Public License 2.0 - see the LICENSE file for details.
This server cannot be installed
local-only server
The server can only run on the client's local machine because it depends on local resources.
A Model Context Protocol (MCP) integration that provides Claude Desktop with autonomous browser automation capabilities. This agent enables Claude to interact with web content, manipulate DOM elements, execute JavaScript, and perform API requests.