
browsentic
Lets an agent CLI drive your own signed-in browser from a side panel, locally
The repository was last updated 9 days ago and is published under Apache-2.0.
- Pricing
- Open source
- Platforms
- Chrome extension, firefox-extension, macOS
- GitHub stars
- 297
- Last commit
- 9 days ago
- Language
- TypeScript
- License
- Apache-2.0
Similar MCP servers
About browsentic
browsentic is an open-source MCP server for browser automation. It is available on Chrome extension, firefox-extension, macOS, Windows, Linux, Android, CLI, self-hosted and API.
Browsentic runs the agent CLI you already use, such as Claude Code or Codex, against the real browser tab you have open. Instructions go in through a side panel or by voice, and a small local program called Browsentic Bridge connects the extension to the agent, so the work happens with your existing cookies, sessions and extensions rather than in a throwaway profile.
The README describes a few mechanics worth knowing: jobs can be scheduled to run in background tabs, a recorded job can be replayed without spending agent tokens, and an experimental Android mode drives Chrome on a phone over adb. Consequential actions such as submitting a form or uploading a file wait for approval, and sites on a block list are off-limits to the agent.
It suits people who already pay for an agent CLI and want it to handle repetitive work inside accounts they are logged into. Because it works in a live browser, it is not a headless or cloud automation service, and the project notes that a hostile page can still mislead the agent.
What it does
- Real signed-in browser
- The agent works in your actual tab, using your existing cookies, two-factor state and extensions.
- No API key needed
- It runs on the agent CLI login you already have rather than asking for a separate model key.
- Scheduled background jobs
- Instructions or recordings can run at set times, each in its own background tab with a one-line result.
- Recorded job replay
- A job you perform once can be replayed later, with steps checked against the live page.
- Approval before consequential actions
- Form submissions, uploads and leaving the site wait for your confirmation.
- Experimental Android control
- Drives Chrome on an Android phone through adb over USB or Wi-Fi, without installing an app on the phone.
Good for
- Summarise pull requests or messages on a schedule inside your own accounts
- Apply for jobs or fill forms from a résumé while you stay in control of submission
- Turn a table on a web page into charts without leaving the browser
- Send invoice reminders or payment requests from web apps you are logged into
- Test a logged-in web app on a desktop or Android phone with an agent
Pricing
Open source
Free and open source under Apache 2.0; no account or subscription.
Prices change. Check browsentic.com before you buy.
browsentic FAQ
Do I need an API key to use it?
No. It runs on the agent CLI login you already have, such as Claude Code, Codex or Cursor CLI, and the README says there is no API client in the repository.
Is it a headless browser?
No. It drives the real tab in front of you, with your sessions, cookies, extensions and two-factor state.
Can it run jobs on a schedule?
Yes. Schedules run once at a set time, on chosen days, or repeatedly, each in a background tab. Runs need the browser open, and a run that falls due while it is closed runs once when the browser returns.
What does it cost and what license is it under?
The site and README describe it as free and open source under Apache 2.0, with no account or subscription.
Is browsentic free?
Yes. browsentic is open source, so you can use and self-host it for free.
What are the best alternatives to browsentic?
The closest alternatives to browsentic are Agent360 Browser MCP, Agentic Browser, Usable Browser Agent, Browsa and Browz.
Where this comes from
- Description: written from the project's README and the project's website.