Browser control MCP: MCP server, setup and security

What Browser control MCP does

According to its repository: “Control the user's Firefox browser via a companion extension.”

An MCP server gives an AI agent extra tools it calls during the conversation: the agent reads their description, decides to use them and gets the result back. Browser control MCP is listed under Browser automation, a category of 109 servers in the directory, where it ranks #35 by stars.

Topics declared by the repository: browser-extension, firefox.

Installing and connecting Browser control MCP

No package or remote server is declared in the official MCP registry: you install it from source, following the repository README.

Like any MCP server, you declare it in your client's configuration (Claude Desktop, Claude Code, Cursor, VS Code, Codex…): a name, the command that starts it or its URL, and any environment variables. The client then starts it and lists its tools. Project language: TypeScript.

Security: what to check

An MCP server runs code with the rights you give it, and the model reads its tool descriptions: a malicious or compromised server can hijack the agent. Read the code, or pick a maintained and widely used server, before connecting it.

Points found for Browser control MCP:

• System access: the Browser automation category gives the agent control over files, a terminal, code or a browser. A booby-trapped instruction in content the agent reads (prompt injection) can then turn into an action.

Good practice: grant only the rights needed (least privilege), require human approval for irreversible actions, and run the AI agent security check.

Project activity and maintenance

Created on March 27, 2025, the eyalzh/browser-control-mcp repository has 337 stars and 81 forks, with 10 open issues. It has more stars than 84% of the servers in the directory. Last change 2 months ago.

Stars measure attention, not quality: a recent, heavily promoted project can collect them fast, while a useful but niche server will have few.