Browser MCP vs browsermcp.io

We are Browser MCP by Agent360 (@agent360/browser-mcp, browsermcp.dev) - a separate, unaffiliated project that happens to solve the same problem with a nearly identical name: a standard stdio MCP server that gives any MCP client - Claude Code, Cursor, VS Code agent mode, or anything else that speaks the protocol, not just those three - control of your real, already-logged-in Chrome instead of a fresh headless session.

The two projects, side by side

Every number below was measured on 2026-09-18, both columns on the same day, from the GitHub API, the npm registry API and the two store pages. Open issues exclude pull requests.

All figures above were re-pulled live on 2026-09-18. npm's public download API reports some days as zero for every package, including both of these, so the 30-day totals understate both projects equally. Originally pulled via the GitHub REST API, the public npm registry API, and the Chrome Web Store listing pages for both extensions (bjfgambnhccakkhmkepdoekmckoijdlc and jdehgalffmffhfhmmhaokfbfnafnmgcl). See "How we verified this" below.

The one thing that actually matters here: maintenance

Scale metrics aside, there's one number in that table that decides whether a tool is safe to build a workflow on: when did the code last change.

browsermcp.io's repository has not had a commit since April 24, 2025. Not a bug fix, not a dependency bump, not a README typo fix - nothing, for more than 16 months as of this writing. Its npm package has been on version 0.1.3 since April 11, 2025, and it has zero published GitHub releases. Its 130 open issues have had no code response in that window, because there hasn't been a commit to respond with. Browser MCP by Agent360 was last pushed to on 2026-09-13 and has shipped eight GitHub releases, the latest v1.29.1 on 2026-09-13.

That's the entire pitch of this page, stated as plainly as we can: actively maintained - not silent since April 2025. We're not implying anything about why browsermcp.io went quiet - we don't know who runs it or what happened, and we haven't tried to find out. We're only reporting what the commit history, release history, and npm registry actually show, with the dates attached, so you can weigh it yourself.

Where browsermcp.io genuinely wins

Being honest about the maintenance gap doesn't mean pretending the rest of the table doesn't exist:

• 100,000 Chrome Web Store users vs. our 973. It has a real, large, established user base. We don't.
• 4.8/5 from 718 ratings. People who installed it and stuck around like it.
• 7,107 GitHub stars vs. our 44. It's the far more visible project if you're browsing GitHub or an "awesome MCP servers" list.
• It has a real npm package and a one-click Chrome Web Store listing - for the record, this corrects an old claim in our own README, which described it as "manual clone only." That hasn't been accurate for a while; it installs about as easily as ours does.

If you install it and it does what you need, there is no reason to switch. A tool that already works for you, with 100k other people behind it, is a perfectly reasonable choice - we're not going to manufacture a reason to distrust something that's genuinely serving people well. The only thing we'd flag is: if you hit a bug, a Chrome API change, or a Manifest V3 deprecation that needs a code fix, there's no evidence anyone is currently shipping fixes for it.

Where the maintenance gap shows up in practice

Chrome ships changes to extension APIs, debugger protocols, and Manifest V3 behavior regularly. A project frozen since April 2025 will, over time, accumulate the kind of breakage that only a live commit history fixes - new Chrome versions changing debugger-attach behavior, CAPTCHA providers updating their challenge markup, sites adding new anti-automation detection. We can't tell you which of browsermcp.io's 130 open issues are that kind of drift versus something else, because we haven't audited them - but the count is public and the "zero commits since April 2025" fact means none of them have been closed by a code change in that time.

Frequently asked questions

Are these the same product? No. Two separate teams, two separate GitHub orgs (BrowserMCP vs. Agent360dk), two separate npm packages (@browsermcp/mcp vs. @agent360/browser-mcp), two separate Chrome extensions. The name overlap ("Browser MCP") is coincidental, not a rebrand or a fork of each other.

Which one has more users? browsermcp.io, by a wide margin - 100,000 Chrome Web Store users vs. our 973, as of 2026-09-18.

Which one is actively maintained? Browser MCP by Agent360. Last push 2026-09-13 vs. browsermcp.io's last commit on 2025-04-24.

Should I uninstall browsermcp.io and switch? Not automatically. If it's working for your workflow, keep using it. Consider trying ours if you specifically need multi-session support (20 concurrent, color-coded tab groups), a human-in-the-loop tool for 2FA codes and credential prompts (browser_ask_user), or you want a project that's currently shipping fixes.

Is one of them free and the other paid? Both are free. browsermcp.io is Apache-2.0 licensed; Browser MCP by Agent360 is MIT licensed. Both permit commercial use.

Is this page trying to make browsermcp.io look bad? No - read the "Where browsermcp.io genuinely wins" section above. The scale numbers favor them and we've published them as-is. The only claim we're making is about commit/release dates, which are objectively checkable by anyone in about two minutes.

Try it yourself

# 1. the Chrome extension: chromewebstore.google.com - search "Agent360 Browser MCP"
# 2. the MCP server (Claude Code):
claude mcp add --scope user browser-mcp -- npx @agent360/browser-mcp@latest

Two parts, both required. MIT licensed, 40 tools, runs on your own machine. Full install guide → · Or install browsermcp.io if that's the right call for you - we mean that.

How we verified this (dated, so it can be re-checked)

All figures on this page were pulled directly on 2026-09-18, from primary sources only - no secondhand blog posts or aggregator sites:

• GitHub stars, push dates, release counts, license, open issues: api.github.com/repos/BrowserMCP/mcp and api.github.com/repos/Agent360dk/browser-mcp, fetched directly. Issue counts come from the search API with is:issue, so pull requests are excluded from both columns.
• npm download counts: api.npmjs.org/downloads/range/<start>:<end>/<package> for the last 30 days, fetched directly for both packages. The API reports some days as zero for every package; both totals include the same zero days.
• npm version + publish dates: registry.npmjs.org/<package>, dist-tags.latest and the corresponding time entry, fetched directly.
• Chrome Web Store users and rating: the live public listing pages for extension IDs bjfgambnhccakkhmkepdoekmckoijdlc (browsermcp.io) and jdehgalffmffhfhmmhaokfbfnafnmgcl (Agent360). Chrome blocks extensions from scripting the store, so the user count was read out of the page's raw HTML rather than the rendered DOM.

This table will go stale - that's the nature of a dated comparison. We'll refresh it when either project's numbers move meaningfully. If you're reading this significantly after September 2026 and want current numbers, the four sources above take about five minutes to re-check yourself.

Not verified on this page: who maintains browsermcp.io or why its commits stopped, and whether it has undocumented equivalents of our multi-session or human-in-the-loop features.