Browsentic

io.github.imshaikotPublished by GitHub account imshaikotv0.9.2Updated Nov 11, 2026

Agentic browser harness: your agent CLI in your real, signed-in browser, from a side panel or MCP.

VerifiedSTDIODesktop onlyBrowser Automation AI & ML

Server details

Identifier: io.github.imshaikot/browsentic
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 26, 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 imshaikot 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.imshaikot%2Fbrowsentic.svg)](https://sourceweft.com/mcp/io.github.imshaikot%2Fbrowsentic?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Browsentic Bridge lets an MCP client drive your real, signed-in browser through a local agent CLI, with no API key or account.

What you can do: Drive the browser you are already signed in to from an MCP client over stdio, sharing the same paired browser with the side panel
Run an agent CLI (Claude Code, Codex and others) against your open tabs instead of a headless browser
Set up and pair the browser extension, list available browsers and issue single-use pairing codes
Check Bridge, paired-browser and agent status, list paired browsers, and revoke one or all of them
Choose which agent CLI runs the side panel, tail the Bridge log, and update the Bridge
When to use it: Use it when you want an assistant to act inside your logged-in browser sessions rather than a fresh headless one, and you already use a supported agent CLI. It is optional for the side panel, which works without MCP.
Requirements: Runs locally over stdio as an npm package (browsentic mcp); Node.js 20 or newer; a Chromium browser or Firefox 140 or newer with the Browsentic extension installed and paired; one supported agent CLI on your PATH, logged in (claude, codex, agy, vibe, grok, cursor-agent, qwen, opencode or dsh). A global install is recommended over npx.

Before you install

The agent works inside your real, signed-in browser tabs, so it can act with your existing sessions and accounts; review what you ask it to do. Pairing codes are single-use and should not be shared, and browsers can be unpaired with the revoke command. Installing via npx can silently start a different Bridge than the one you set up.

Installation

In SourceWeft

Open Browsentic 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

browsentic

This is Browsentic Bridge, the half of Browsentic that runs on your computer.

Browsentic is your browser's superpower: an agentic browser harness that runs the agent CLI you already use from a side panel in your real, logged-in browser. The side panel opens beside whatever tab you are on; the Bridge runs on loopback and starts your agent CLI when you give it work. It is free and open source, with no hosted relay, no API key, no account and no headless browser: the agent works in the tabs you are already signed in to.

Install

One command sets everything up, the extension included:

It starts Browsentic Bridge, asks which browser you use, opens the extension's store page there and waits for the browser to connect. Press Add to Chrome (Add in Firefox; Edge first asks you to allow extensions from other stores), and the extension connects by itself; if it asks for a code, enter the one setup prints. On macOS and Windows an app does the same from a window: see browsentic.com/install.

The extension is on the Chrome Web Store for Chrome, Brave, Arc, Vivaldi and Opera, on Edge Add-ons for Edge, and Firefox gets an add-on signed by Mozilla. The side panel runs on an agent CLI you are signed in to: Claude Code, Codex, or another supported one.

Then open the side panel and type or speak an instruction.

To update later:

The extension updates itself from its store, and the two do not have to be the same version.

Requirements

Node.js 20 or newer
Chrome, Edge, Brave, Arc, Vivaldi, Opera or another Chromium browser, or Firefox 140 or newer
One agent CLI on your PATH, logged in: claude, codex, agy, vibe, grok, cursor-agent, qwen, opencode or dsh

Commands


`browsentic setup`	start the Bridge, add the extension to a browser and pair it
`browsentic update`	update the Bridge and restart it
`browsentic browsers`	the browsers on this computer and where each gets the extension
`browsentic pair`	issue a fresh single-use code
`browsentic status`	the Bridge, each paired browser and the agent
`browsentic sessions`	list paired browsers
`browsentic revoke`	unpair one browser, or all of them
`browsentic agent`	choose which agent runs the side panel
`browsentic logs`	tail the Bridge's log
`browsentic mcp`	serve MCP over stdio

browsentic help lists the rest. A browser that cannot reach a store can load the extension from a folder this package carries: browsentic setup --unpacked.

Using it from an MCP client

Optional, and the side panel needs none of it. Registering Browsentic with an MCP client lets that client drive the same browser from a terminal.

Any MCP client works: Claude Code, Codex, Cursor, Zed, Claude Desktop. One Bridge owns the browser link, so several can share the same paired browser at once.

Prefer a global install over npx here. An npx command re-resolves on every client start and can quietly start a different Bridge than the one you set up.

Documentation

Full documentation lives at browsentic.com/docs, including the security model, the tool reference and the architecture.

Source: github.com/imshaikot/browsentic · Apache 2.0

Source: src/daemon/README.md at commit f323a0d

Tools

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

Version history

v0.9.2LatestNov 11, 2026
v0.9.0Oct 18, 2026
v0.8.9Oct 12, 2026
v0.8.1Oct 9, 2026
v0.8.0Oct 4, 2026
v0.7.15Oct 1, 2026
v0.7.14Sep 30, 2026
v0.7.11Sep 27, 2026
v0.7.6Sep 26, 2026

Score

50% 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
License10 pts