Browser Mcp

io.github.mrfentmenPublished by GitHub account mrfentmenv1.0.1Updated Oct 24, 2026

Control a local headless Chrome browser: open pages, read titles, and take screenshots.

VerifiedSTDIODesktop onlyBrowser Automation

Server details

Identifier: io.github.mrfentmen/browser-mcp
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 22, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account mrfentmen for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.mrfentmen%2Fbrowser-mcp.svg)](https://sourceweft.com/mcp/io.github.mrfentmen%2Fbrowser-mcp?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

A local MCP server that lets an assistant drive a headless Chrome browser: open pages, read their titles, and capture screenshots.

What you can do: Open web pages in a local headless Chrome browser and navigate to given addresses. Read the title of the currently loaded page. Capture screenshots of pages the browser has loaded.
When to use it: Useful when an assistant needs to load a web page locally and check what it shows, for example grabbing a screenshot or confirming a page title, without a full browser-automation suite.
Requirements: Runs as a local process on the user's machine via the npm package, so Node.js and a local Chrome installation are needed. Desktop only; no authentication, environment variables or headers are declared.

Before you install

The browser fetches whatever pages the assistant is asked to open, so page content and addresses go to those remote sites. Screenshots may capture sensitive on-screen content; review where they are stored or shared.

Installation

In SourceWeft

Open Browser Mcp in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v1.0.1LatestSep 22, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
License10 pts
Declare a license in the repository or the registry entry.