Browsentic

Name: Browsentic
Author: imshaikot

Local

browsentic.comBrowser Automation247Updated 2d ago

Repository Visit website

About Browsentic

Browsentic Bridge runs an agent CLI from a browser side panel and lets it work in the user's already signed-in tabs. It is for people who want to direct browser tasks through their existing agent CLI, with an optional MCP connection for terminal-based control.

Key features

01Browser side panel for agent tasks
02Uses existing signed-in browser tabs
03Local loopback Bridge
04Supports multiple agent CLIs
05Pair and revoke browsers
06MCP over stdio

Use cases

01Ask an agent to work in an open signed-in tab
02Run browser tasks from a terminal MCP client
03Share one paired browser across MCP clients
04Pair or revoke browser access

MCP support

Browsentic can serve MCP over stdio so MCP clients can drive the same paired browser. One Bridge can serve several clients using that browser link.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config

{
  "mcpServers": {
    "imshaikot-browsentic": {
      "command": "npx",
      "args": [
        "-y",
        "browsentic"
      ]
    }
  }
}

Run commandnpx -y browsentic

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages

npmbrowsentic0.9.0stdio

Tools

Saved tool list · updated 1w ago

Parameter	Type	Required	Description
geometry	boolean	No	Add each element’s "bounds" in document pixels. Off by default: a selector or visible text is what the other tools target by, so ask only when you need coordinates — a point for page.trustedClick or page.dragElement.
maxPerKind	integer	No	Cap on links, buttons, fields, and forms listed per kind

Details

From the project 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:

npx browsentic@latest setup

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:

npx browsentic@latest update

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.

npm i -g browsentic
claude mcp add browsentic -- browsentic mcp

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

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

Read the getting-started guide

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.