Repository navigation
Connect an Agent
Mustapha Zoghlami edited this page Nov 4, 2026
·
1 revision
BrowserForge speaks MCP over HTTP on http://127.0.0.1:7345/mcp, with the MCP token as a Bearer token. Any MCP client works; these two are tested.
claude mcp add --transport http browserforge http://127.0.0.1:7345/mcp --header "Authorization: Bearer $(cat ~/.config/browserforge/mcp-token)"codex mcp add browserforge --url http://127.0.0.1:7345/mcp --bearer-token-env-var BROWSERFORGE_MCP_TOKEN
export BROWSERFORGE_MCP_TOKEN="$(cat ~/.config/browserforge/mcp-token)"browserforge print-config claude and browserforge print-config codex print these with your paths and port.
Ask your agent: "Call system_status, then open a page and describe it." system_status shows whether a browser is connected.
- Page content is untrusted data to the agent; approvals are answered by you in the extension popup.
- The Ask the agent button in the popup hands the agent the page you are looking at (docs).
- Three different tokens exist on purpose: extension token (popup), MCP token (agent), dashboard token (Dashboard). Never paste the MCP token into a web page.
Guides: Claude Code · Codex. Problems: Troubleshooting.
MIT licensed · Repository · Issues · Releases · Privacy
Use it
Grow it
Trust it
Help
Project