MCP · Chrome · stable ids

Signal for your browser.

Beacon connects Cursor to Chrome — observe the page, act by stable ids, verify the result.

Extension + relay. Sign up, paste one key, keep a tab open.

Why

Browser tools break when names lie.

Pages change. Labels duplicate. “Click Submit” hits the wrong Submit. One id per control in every observe dump. Your agent uses that id — not a guess from visible text.

How it works

Three steps out of the fog

01

Install the extension

Load the Chrome extension and sign in at trybeacon.space.

02

Add MCP to Cursor

Paste your one-time key into mcp.json. Bearer auth. No query hacks.

03

Observe, then act

observe returns controls with ids. click, type, and run use those ids on your open tab.

Cursorapi.trybeacon.spaceYour Chrome tab

MCP

Built for MCP

Tools: observe, click, type, press, scroll, navigate, run. Multi-step run executes without an LLM between steps. The extension is the hands; the server is the relay.

mcp.json
{
  "mcpServers": {
    "beacon": {
      "url": "https://api.trybeacon.space/mcp",
      "headers": { "Authorization": "Bearer bcn_…" }
    }
  }
}

Security

Your browser. Your key.

  • MCP keys are generated once; we store a hash, not the secret.
  • Passwords hashed with bcrypt.
  • Relay does not replace your login to sites — you stay logged in as you normally are.
  • Rotate your key anytime from account.

Still in the fog?