Browser Control MCP
@eyalzh
About Browser Control MCP
MCP server paired with a browser extension that enables AI agents to control the user's browser.
Basic information
Config
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"browser-control": {
"command": "node",
"args": [
"/path/to/repo/mcp-server/dist/server.js"
],
"env": {
"EXTENSION_SECRET": "<secret_on_firefox_extension_options_page>",
"EXTENSION_PORT": "8089"
}
}
}
}Tools
No tools detected
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
Overview
What is Browser Control MCP?
Browser Control MCP is an MCP server paired with a Firefox browser extension that gives AI assistants access to tab management, browsing history, and webpage text content. It provides a secure alternative to web automation MCP servers for controlling the user’s personal browser.
How to use Browser Control MCP?
Install the Firefox add-on from addons.mozilla.org or as a temporary add-on, then configure the MCP server in your mcpServers config (e.g., claude_desktop_config.json) with the EXTENSION_SECRET and optional EXTENSION_PORT. Alternatively, build from source or use the provided Docker image.
Key features of Browser Control MCP
- Open and close browser tabs
- Get a list of opened tabs
- Create tab groups with name and color
- Reorder opened tabs
- Read and search browser history
- Read webpage text content and links (requires user consent)
- Find and highlight text in a browser tab (requires user consent)
Use cases of Browser Control MCP
- Manage tabs: close, group, or rearrange tabs by command.
- Search browser history for specific articles or pages.
- Automate research: open search results, read pages, and summarize.
FAQ from Browser Control MCP
How does Browser Control MCP differ from web automation MCP servers?
It is designed to be more secure: it does not support page modification, page interactions, or arbitrary scripting. Reading webpage content requires explicit user consent per domain, and the connection is local-only with a shared secret. No remote data collection or tracking occurs.
What are the runtime requirements?
You need Firefox (or Firefox Developer Edition) and the Browser Control MCP browser extension. The MCP server runs locally and communicates with the extension via a configurable port (default 8089).
How is security handled?
User consent is enforced for reading webpage content and highlighting text. The extension provides an audit log of tool calls and tool enable/disable configuration. The MCP server uses a local-only connection with a shared secret. No third-party runtime dependencies are included in the extension.
Is Browser Control MCP stable?
It is marked as experimental. Use at your own risk, and exercise caution when authorizing or monitoring tool calls.
Which browsers are supported?
Only Firefox is supported (including Firefox Developer Edition). The extension is available via addons.mozilla.org or as a temporary add-on.
More Browser Automation MCP servers
Fetch
modelcontextprotocolModel Context Protocol Servers
BrowserTools MCP
AgentDeskAIMonitor browser logs directly from Cursor and other MCP compatible IDEs.
Browserbase MCP Server
browserbaseAllow LLMs to control a browser with Browserbase and Stagehand
Fastcrw
usFast, lightweight Firecrawl/Tavily alternative in Rust. Web scraper, crawler & search API with MCP server for AI agents. Drop-in Firecrawl-compatible API (/scrape, /crawl, /search). 2.3x faster than Tavily, 1.5x faster than Firecrawl in 1K-URL benchmarks. 6 MB RAM, single binary.
Comments