Guides

Short guides on using AI agents in your own signed-in Chrome with Beacon. Ready to try it? Go to setup.

• A browser MCP that works in your own Chrome

  Beacon is a browser MCP: a Chrome extension and hosted relay that let any MCP client read and act on pages in your own signed-in Chrome.

• An MCP server for Chrome, over plain HTTP

  How Beacon exposes Chrome to MCP clients over remote HTTP with a Bearer key, using a Chrome extension and a hosted relay.

• How to let an AI agent use your logged-in Chrome

  How to let an AI agent work in your signed-in Chrome with Beacon, and what limits keep it inside its own tab group.

• Browser automation for Claude Code

  Add Beacon to Claude Code with one command and let it automate pages in your own signed-in Chrome.

• A browser MCP for Cursor

  Connect Cursor to your own signed-in Chrome with Beacon: install the extension, paste an mcp.json entry, and ask the agent.

• How to run multiple AI agents in Chrome

  Run several AI agents in one Chrome with Beacon: each agent gets its own lane, a colour-coded tab group, and cannot act on another lane's tabs.

• AI agent tab groups: one colour per agent

  How Beacon uses Chrome tab groups as lanes: one colour-coded group per agent, so you can see whose tab is whose.

• Browser automation that uses your own login

  Automate sites you are already signed into: Beacon works in your own Chrome, so there is no re-login and no fresh browser to configure.

• Beacon and Playwright for logged-in sessions

  How Beacon differs from Playwright for tasks behind a login: your own Chrome and sessions versus a browser launched fresh.

• Parallel browser agents, without the collisions

  Run parallel browser agents across Chrome profiles with Beacon: separate lanes, a shared Agent Board, and agents that ask when stuck.