An MCP server for Chrome, over plain HTTP
Beacon exposes Chrome as a remote MCP server. Your client talks to a hosted HTTP endpoint with a Bearer key, and the Chrome extension carries out the actions in your browser.
How it works
- Your MCP client sends tool calls to the Beacon MCP endpoint.
- The hosted relay forwards them to the extension linked to your account.
- The extension acts in Chrome and sends what the page returned back through the relay.
Which clients work
Any MCP client that supports remote MCP over HTTP with a Bearer header. That includes Claude Code and Cursor. You paste the same JSON config into your client's MCP settings, or use the one-line command for Claude Code.
What the relay carries
The agent's commands, and what the page sends back, pass through the hosted relay to the extension. Treat it like any hosted service, and read the privacy policy for the details.