Agent360 Browser MCP

Checking…

Already registered the server? Then this is normal: the server only takes a port the first time your agent actually uses the browser. Ask it for a screenshot once, and this turns into "Connected".

Otherwise: this extension is only half of Browser MCP. It needs a local MCP server to talk to - the Chrome Web Store cannot install that part. Register it once, then restart your agent. Claude Code:

claude mcp add --scope user browser-mcp -- npx @agent360/browser-mcp@latest

Codex: codex mcp add browser-mcp -- npx @agent360/browser-mcp@latest
Cursor, VS Code and the rest: run npx @agent360/browser-mcp install - it registers with the clients you have.

Setup guide

Connected - you're ready. Nothing happens until you ask your agent for something. Try saying:

"Take a screenshot of my current Chrome tab." "Open my Gmail tab and tell me who sent my last 3 emails." More things to try
Pairing (optional)

Two Chrome profiles, two agents? Give each profile a key, and each server the same one. Then a profile only takes commands from its own server. Leave empty for the default: no key, no setup.

Sessions
No tabs claimed yet
Action Log
No actions yet