Skip to directory

Browser MCP

BrowserMCP (community-maintained)

stdio1 documented tools7

About Browser MCP

Browser MCP connects an AI client to a local browser through a Chrome extension, letting the agent automate pages in the user's existing browser profile.

What you can use it for

  • Navigate and inspect web pages
  • Automate user-approved browser tasks
  • Run UI checks using the user's existing browser profile
Connection and setup
Hosting
local
Transport
stdio
Endpoint
Local process; no hosted endpoint documented
Authentication
No separate MCP credential; the local extension/background process pairs with the client and uses the user’s browser profile.

Requirements

  • Node.js and npx.
  • A Chrome browser with the Browser MCP extension installed and connected.
  • An MCP-compatible client.

Setup steps

  1. Install the Browser MCP extension from the official Chrome Web Store: https://chromewebstore.google.com/detail/browser-mcp-automate-your/bjfgambnhccakkhmkepdoekmckoijdlc.
  2. Configure the MCP client to run `npx` with args [`@browsermcp/mcp@latest`] using stdio.
  3. Start or reload the MCP server in the client, then open the browser extension and click Connect.
  4. Confirm the client reports the server connected and inspect its tools/list. A harmless check is to navigate to a public page and request a page snapshot.
  5. If the client reports `Client closed`, the official troubleshooting guide suggests removing `@latest` from the package argument and retrying.
Tools 1

Official reference says the MCP server exposes exactly one tool named browser; its arguments are command lines.

  • browser

    Run browser command lines to navigate, interact with page elements, inspect page content, manage tabs, and read diagnostics.

    01
Limitations and notes
  • Browser automation can access websites where the user's browser is logged in; review the current tab and approve sensitive actions before use.
  • The browser extension must be connected to the local MCP process; an enabled MCP server alone is insufficient.
  • The Chrome Web Store listing reports 100,000 users and 746 ratings, but its shown extension version was updated May 7, 2025; this is usage evidence, not a guarantee of current connection reliability.
  • No MCP initialization, tools/list, or representative tool call was performed for this catalog entry.
Original sources
  • official server setup documentation

    Documents Node.js requirement, exact npx package command, supported client setup, and client-side reload action.

  • official troubleshooting documentation

    Explains that both the MCP process and browser extension connection are required, and documents an @latest workaround for Client closed errors.

  • official product site

    Describes local browser automation through the user's logged-in profile and product capabilities; does not publish exact protocol tool names.

  • official extension listing

    Official Chrome Web Store listing corroborates publisher site and reports 100,000 users and 746 ratings; displayed extension version 1.3.4 was updated May 7, 2025.

  • verified repository owner avatar

    Verified BrowserMCP GitHub organization avatar, decoded and visually reviewed on light and dark contact sheets. Selection tier D: repository owner avatar.

  • official publisher documentation

    Official docs state the server exposes exactly one MCP tool named browser and document its command set.

Documentation checked 2026-10-28T20:30:00.000Z. Connection has not been runtime tested.