Browser MCP Server
An MCP server that connects an AI assistant to a Chrome extension running on the user's own browser profile, so it can navigate, click and read pages while keeping existing logins and avoiding bot-detection friction.
Browser MCP Server is a Model Context Protocol server that bridges AI assistants such as Cursor, Claude Desktop, VS Code and Windsurf to a local browser, through a Chrome extension talking to the server over a WebSocket. Because it operates on the user's existing browser profile rather than launching a separate instance, it preserves login sessions and reduces the friction that headless automation usually triggers.
Its tools cover navigation, such as going to a URL or waiting for a page; interaction, such as clicking, typing, hovering, dragging and pressing keys; and inspection, such as taking an accessibility snapshot, a screenshot or reading console logs. An optional Redis-backed store can persist session and tool-call metadata, and the server logs its own activity with configurable levels.
It requires Node.js 18 or newer, the matching Chrome extension, and optionally Redis 6 or newer for session persistence.