Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
To use Agent360 Browser MCP with Claude Code, install both parts of the setup: the Browser MCP Chrome extension and the local @agent360/browser-mcp server. Register the server with Claude Code, restart Claude Code, then ask it to take a screenshot of your current Chrome tab. A screenshot returned by that request is the vendor-documented connection check.
What Agent360 Browser MCP does—and what it needs
“Browser MCP” can refer to different projects. This guide is for Agent360’s @agent360/browser-mcp package and its Chrome extension, not the separate Chrome DevTools for agents project. Agent360 describes its Browser MCP as a local MCP server that communicates with a Chrome extension to control the Chrome session you already have open.
![Claude AI for Beginners Bible: [5 in 1] The Ultimate Guide to Automate Your Work, Save Hours Every Week, and Use AI for Real-World Results](https://m.media-amazon.com/images/I/415+fSJacsL._SL160_.jpg)
The two components do different jobs: the extension connects to and drives Chrome; the local server gives Claude Code a way to call browser tools. Installing only one leaves the setup incomplete. Agent360’s installation guide describes both halves as required.
Agent360 lists capabilities including navigation, page content, screenshots, interaction, tabs and frames, browser data, and handing control back to the user. The vendor advertises 40 browser tools as of 2026; that is a vendor-stated count, not an independent measurement. Browser actions happen in the connected session, so an agent may see content available there and act on your behalf.
Install the Chrome extension
Choose one installation method. For most users, the Chrome Web Store version is the simpler choice; Agent360 says that version updates through Chrome. The unpacked installation is useful if you specifically want to load extension files copied by the package command.
Option 1: Chrome Web Store
- Install the Agent360 Browser MCP extension from the Chrome Web Store. Search for the Agent360 Browser MCP extension and confirm that it is the intended extension before adding it.
- Keep Chrome open. You will need the extension installed and available in the browser session Claude Code is meant to operate.
Option 2: Unpacked extension
- Run
npx @agent360/browser-mcp installin a terminal. The command copies the extension files to~/.browser-mcp/extension/. This installs extension files; it does not register the MCP server with Claude Code. - In Chrome, open
chrome://extensions. - Turn on Developer mode, choose Load unpacked, and select
~/.browser-mcp/extension/. - Confirm that the extension appears in Chrome’s extensions list and is enabled.
With an unpacked install, updates to the copied extension files require you to reload the extension manually in Chrome. Do not assume this install follows the Chrome Web Store’s automatic update path.
Register the local server in Claude Code
Run the following command in a terminal where Claude Code is installed:
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Rank #2
claude mcp add --scope user browser-mcp -- npx @agent360/browser-mcp@latestHere, browser-mcp is the server name Claude Code will display. The --scope user option makes the server available across your projects, according to Agent360’s instructions. The command runs the package through npx; the @latest tag asks for the latest package when the command is invoked. It does not install the Chrome extension for you.
Manual configuration alternative
If you prefer to configure the server manually, Agent360 documents adding this entry to ~/.claude.json:
{
"mcpServers": {
"browser-mcp": {
"command": "npx",
"args": ["@agent360/browser-mcp@latest"]
}
}
}Use either the CLI command or the manual configuration method; they serve the same registration purpose. Anthropic’s Claude Code user FAQ also recommends registering MCP servers with claude mcp add or a project .mcp.json, then restarting Claude Code and checking /mcp. If you use a project-level configuration instead, make sure the project contains the entry you intend to use.
Restart and verify the connection
- After registering the server, restart Claude Code so it reloads the MCP configuration.
- In Claude Code, run
/mcpto inspect MCP status. - Make sure Chrome is open and the Browser MCP extension is loaded.
- Ask Claude Code: “Take a screenshot of my current Chrome tab.”
- Check that Claude Code returns a screenshot. Agent360 documents this request as a success check. The extension may not display a connected indicator until a browser tool is used for the first time.
If the screenshot request fails, treat the result as a connection or browser-state issue to investigate rather than proof that the server was registered correctly. Check the extension, server entry, and Claude Code’s MCP status before trying the verification prompt again.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Use the browser with appropriate limits
Agent360 gives examples such as working with a logged-in dashboard, navigating a site behind sign-in, and pausing for user input during credential or challenge steps. These are vendor-documented use cases, not a guarantee that every site or challenge will work. Do not give an agent passwords or payment details. For sensitive steps, tell it to stop and ask you before proceeding, and review the action before it is submitted.
Agent360 describes information moving locally between its server, extension, and browser, while also noting that content the agent reads is sent to the AI client and its model provider. That is the vendor’s description, not an independent privacy audit. Chrome for Developers likewise warns that browser-control tools can expose browser content to an agent and allow it to act through an authenticated session.
- Use a dedicated Chrome profile or a session with only the access needed for the task when practical.
- Avoid connecting sensitive pages that the task does not require.
- Watch what the agent reads and submits, especially on account, credential, and payment screens.
- Require human confirmation before consequential actions such as changing account settings or submitting a transaction.
The reviewed sources do not establish a particular compliance certification or independent security assessment for Agent360 Browser MCP. Treat access to an authenticated browser as sensitive regardless of the local-server design.
Agent360 Browser MCP and Chrome DevTools for agents are different tools
Chrome DevTools for agents is a separate MCP-based option that supports Claude Code. Chrome’s documentation describes developer-focused browser inspection, including performance traces. Agent360 positions Browser MCP around operating the existing Chrome session. Choose based on the workflow you need, not the shared phrase “Browser MCP.”
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitches| Consideration | Agent360 Browser MCP | Chrome DevTools for agents |
|---|---|---|
| Documented focus | Interaction with the existing Chrome session, according to Agent360. | Browser inspection and developer workflows such as performance traces, according to Chrome for Developers. |
| Claude Code setup documented by the vendor | Install the Chrome extension and register @agent360/browser-mcp as a local server. |
Use Claude Code’s plugin marketplace commands. |
| Example installation commands | claude mcp add --scope user browser-mcp -- npx @agent360/browser-mcp@latest |
/plugin marketplace add ChromeDevTools/chrome-devtools-mcp/plugin install chrome-devtools-mcp@chrome-devtools-plugins |
Before choosing either, compare the exact browser workflow and capabilities you need, its installation style, and the permissions it receives. Both can give an agent access to browser content or actions, so apply the same care to authenticated sessions.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Troubleshoot “Not connected” and failed browser requests
The extension says “Not connected”
- Check both components. Confirm that the Chrome extension is installed and enabled, and that the server is registered in Claude Code. Neither half installs the other.
- Restart Claude Code. Do this after registering the server so it reloads the configuration.
- Check the extension in Chrome. For an unpacked install, open
chrome://extensionsand make sure the extension is loaded and enabled. - Try Reconnect. Open the extension and select Reconnect, then allow a few seconds for its connection scan, as Agent360 instructs.
- Use a browser tool once. The connection indicator may not appear until the first browser tool is used. Try the documented screenshot request.
Claude Code cannot find the server
Run /mcp and check whether browser-mcp appears. If it does not, confirm that the command or JSON entry was added to the configuration you intended, that the package name is exactly @agent360/browser-mcp@latest, and that Claude Code was restarted after the change. If you edited ~/.claude.json, ensure the JSON is valid and the entry is nested under mcpServers.
The unpacked extension stops working after an update
The package installer copies extension files, while Chrome Web Store distribution has its own update path. If you update the copied files, reload the unpacked extension in chrome://extensions. The server’s @latest tag and an unpacked extension are separate update mechanisms; do not assume invoking the server command reloads the extension.
The screenshot request does not return a screenshot
First verify that Chrome is open, the intended extension is enabled, Claude Code reports the MCP server, and you have restarted after registration. If those checks pass, reconnect the extension and retry the screenshot request. A connected indicator by itself is not the documented success check; the returned screenshot is.
Recommended Free Tools
Or skip the browser setup
If what you need is a screenshot of a public URL—not Claude Code control of your current Chrome tab or an authenticated session—ScreenshotNeo offers a one-request screenshot API. It is not a replacement for Browser MCP: it takes a URL as input and returns an image or PDF, rather than connecting Claude Code to your open browser.
For example, save a WebP capture of Stripe with cURL:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpSee the ScreenshotNeo API documentation for setup and request options. ScreenshotNeo says it removes cookie banners, newsletter popups, and chat widgets before capture; bot checks, blank pages, and failed loads are never billed; and its MCP server lets AI agents use screenshot tools. The free plan includes 1,000 screenshots per month with no card, and paid plans start at $5 for 3,000. Those URL-based captures do not give an agent access to your existing logged-in Chrome session.
Sign up for ScreenshotNeo’s free plan to get 1,000 screenshots a month with no card.
Free tools Windows power users keep installed
One-click scans. No signup required.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
