Related Pages

Related topics: Entrypoints and Runtime Surface, Architecture Evidence Map, Operations and Verification Boundaries

Repository Overview

This page is generated from repository evidence because the Human Wiki provider was unavailable. It intentionally limits itself to README and file-tree facts.

README Evidence

Browser MCP by Agent360

     

Control your real Chrome from Claude Code — with your logins, cookies, and 2FA.

!Browser MCP Demo

The only browser MCP with multi-session support (10 concurrent AI sessions), human-in-the-loop (2FA, CAPTCHA, credentials), and built-in provider integrations (Stripe, HubSpot, Slack, and 6 more). 33 tools total.

Install — 2 steps (~60 seconds)

Step 1: Configure the MCP server

npx @agent360/browser-mcp install

This copies the Chrome extension files to ~/.browser-mcp/extension/ and adds the MCP server to your Claude Code config. You'll see the path to the extension folder printed in the terminal — copy it.

Step 2: Load the extension in Chrome

Chrome won't let extensions install themselves from npm — you have to load it manually one time. After that, it auto-updates whenever you re-run the install command.

1. Open Chrome and type chrome://extensions in the address bar
2. Toggle "Developer mode" ON (top right corner)
3. Click "Load unpacked" (top left, next to "Pack extension")
4. Navigate to ~/.browser-mcp/extension/ and click "Select"

• On Mac: Press Cmd+Shift+G in the file picker, paste ~/.browser-mcp/extension/, press Enter
• On Windows: Paste %USERPROFILE%\.browser-mcp\extension\ in the address bar
• On Linux: Type ~/.browser-mcp/extension/ in the path field

1. Restart Claude Code so it picks up the new MCP server

That's it. The Browser MCP icon will appear in your toolbar, and 33 browser tools are now available in Claude Code.

Alternative: Manual zip download (no npm)

If you don't

[excerpt truncated]

Selected Source Inventory

• README.md
• demo-video-src/package.json
• mcp-server/README.md
• mcp-server/package.json
• demo-video-src/src/Composition.tsx
• demo-video-src/src/Demo.tsx
• demo-video-src/src/Root.tsx
• demo-video-src/src/index.css
• demo-video-src/src/index.ts
• demo-video-src/src/components/Browser.tsx
• demo-video-src/src/components/Effects.tsx
• demo-video-src/src/components/MorePages.tsx

Source: README.md:1-120

Related Pages

Related topics: Repository Overview, Architecture Evidence Map, Operations and Verification Boundaries

Entrypoints and Runtime Surface

The files below are the highest-signal candidates for how the project is installed, started, configured, or embedded. Treat this as an evidence map, not an inferred API contract.

Source: README.md:1-120

Related Pages

Related topics: Repository Overview, Entrypoints and Runtime Surface, Operations and Verification Boundaries

Architecture Evidence Map

This section maps source paths into likely architectural areas based on repository layout only. Claims that require execution are intentionally not made here.

• .: README.md
• demo-video-src: demo-video-src/package.json, demo-video-src/src/Composition.tsx, demo-video-src/src/Demo.tsx, demo-video-src/src/Root.tsx, demo-video-src/src/index.css, demo-video-src/src/index.ts
• mcp-server: mcp-server/README.md, mcp-server/package.json

Source: demo-video-src/package.json:1-120

Related Pages

Related topics: Repository Overview, Entrypoints and Runtime Surface, Architecture Evidence Map

Operations and Verification Boundaries

Operational guidance is limited to files that are present in the repository. Before using this project in an agent workflow, verify install, quickstart, and runtime behavior in a sandbox.

• Documentation signal: README.md
• Runtime/package signal: demo-video-src/package.json
• Documentation signal: mcp-server/README.md
• Runtime/package signal: mcp-server/package.json
• Source inspection signal: demo-video-src/src/Composition.tsx
• Source inspection signal: demo-video-src/src/Demo.tsx
• Source inspection signal: demo-video-src/src/Root.tsx
• Source inspection signal: demo-video-src/src/index.css
• Source inspection signal: demo-video-src/src/index.ts
• Source inspection signal: demo-video-src/src/components/Browser.tsx

Source: mcp-server/README.md:1-120

Doramagic Pitfall Log

Doramagic extracted 9 source-linked risk signals. Review them before installing or handing real data to the project.

1. Installation risk: Using browser-mcp remotely (linux + systemd solution)

• Severity: high
• Finding: Installation risk is backed by a source signal: Using browser-mcp remotely (linux + systemd solution). Treat it as a review item until the current version is checked.
• User impact: First-time setup may fail or require extra isolation and rollback planning.
• Recommended check: Open the linked source, confirm whether it still applies to the current version, and keep the first run isolated.
• Evidence: Source-linked evidence: https://github.com/Agent360dk/browser-mcp/issues/1

2. Installation risk: Developers should check this installation risk before relying on the project: Using browser-mcp remotely (linux + systemd solution)

• Severity: medium
• Finding: Developers should check this installation risk before relying on the project: Using browser-mcp remotely (linux + systemd solution)
• User impact: Developers may fail before the first successful local run: Using browser-mcp remotely (linux + systemd solution)
• Recommended check: Before packaging this project, run the relevant install/config/quickstart check for: Using browser-mcp remotely (linux + systemd solution). Context: Observed when using linux
• Evidence: failure_mode_cluster:github_issue | fmev_9bfdeebbaac14508096abe351728049c | https://github.com/Agent360dk/browser-mcp/issues/1 | Using browser-mcp remotely (linux + systemd solution)

3. Configuration risk: Configuration risk needs validation

• Severity: medium
• Finding: Configuration risk is backed by a source signal: Configuration risk needs validation. Treat it as a review item until the current version is checked.
• User impact: Users may get misleading failures or incomplete behavior unless configuration is checked carefully.
• Recommended check: Open the linked source, confirm whether it still applies to the current version, and keep the first run isolated.
• Evidence: capability.host_targets | mcp_registry:io.github.Agent360dk/browser-mcp:1.16.1 | https://registry.modelcontextprotocol.io/v0.1/servers/io.github.Agent360dk%2Fbrowser-mcp/versions/1.16.1 | host_targets=mcp_host, claude, claude_code

4. Capability assumption: README/documentation is current enough for a first validation pass.

• Severity: medium
• Finding: README/documentation is current enough for a first validation pass.
• User impact: The project should not be treated as fully validated until this signal is reviewed.
• Recommended check: Open the linked source, confirm whether it still applies to the current version, and keep the first run isolated.
• Evidence: capability.assumptions | mcp_registry:io.github.Agent360dk/browser-mcp:1.16.1 | https://registry.modelcontextprotocol.io/v0.1/servers/io.github.Agent360dk%2Fbrowser-mcp/versions/1.16.1 | README/documentation is current enough for a first validation pass.

5. Maintenance risk: Maintainer activity is unknown

• Severity: medium
• Finding: Maintenance risk is backed by a source signal: Maintainer activity is unknown. Treat it as a review item until the current version is checked.
• User impact: Users cannot judge support quality until recent activity, releases, and issue response are checked.
• Recommended check: Open the linked source, confirm whether it still applies to the current version, and keep the first run isolated.
• Evidence: evidence.maintainer_signals | mcp_registry:io.github.Agent360dk/browser-mcp:1.16.1 | https://registry.modelcontextprotocol.io/v0.1/servers/io.github.Agent360dk%2Fbrowser-mcp/versions/1.16.1 | last_activity_observed missing

6. Security or permission risk: no_demo

• Severity: medium
• Finding: no_demo
• User impact: The project may affect permissions, credentials, data exposure, or host boundaries.
• Recommended check: Open the linked source, confirm whether it still applies to the current version, and keep the first run isolated.
• Evidence: downstream_validation.risk_items | mcp_registry:io.github.Agent360dk/browser-mcp:1.16.1 | https://registry.modelcontextprotocol.io/v0.1/servers/io.github.Agent360dk%2Fbrowser-mcp/versions/1.16.1 | no_demo; severity=medium

7. Security or permission risk: no_demo

• Severity: medium
• Finding: no_demo
• User impact: The project may affect permissions, credentials, data exposure, or host boundaries.
• Recommended check: Open the linked source, confirm whether it still applies to the current version, and keep the first run isolated.
• Evidence: risks.scoring_risks | mcp_registry:io.github.Agent360dk/browser-mcp:1.16.1 | https://registry.modelcontextprotocol.io/v0.1/servers/io.github.Agent360dk%2Fbrowser-mcp/versions/1.16.1 | no_demo; severity=medium

8. Maintenance risk: issue_or_pr_quality=unknown

• Severity: low
• Finding: issue_or_pr_quality=unknown。
• User impact: Users cannot judge support quality until recent activity, releases, and issue response are checked.
• Recommended check: Open the linked source, confirm whether it still applies to the current version, and keep the first run isolated.
• Evidence: evidence.maintainer_signals | mcp_registry:io.github.Agent360dk/browser-mcp:1.16.1 | https://registry.modelcontextprotocol.io/v0.1/servers/io.github.Agent360dk%2Fbrowser-mcp/versions/1.16.1 | issue_or_pr_quality=unknown

9. Maintenance risk: release_recency=unknown

• Severity: low
• Finding: release_recency=unknown。
• User impact: Users cannot judge support quality until recent activity, releases, and issue response are checked.
• Recommended check: Open the linked source, confirm whether it still applies to the current version, and keep the first run isolated.
• Evidence: evidence.maintainer_signals | mcp_registry:io.github.Agent360dk/browser-mcp:1.16.1 | https://registry.modelcontextprotocol.io/v0.1/servers/io.github.Agent360dk%2Fbrowser-mcp/versions/1.16.1 | release_recency=unknown

Community Discussion Evidence

Doramagic exposes project-level community discussion separately from official documentation. Review these links before using browser-mcp with real data or production workflows.

• Using browser-mcp remotely (linux + systemd solution) - github / github_issue
• Configuration risk needs validation - GitHub / issue