Browse projects/Automation/Give your agent a browser/agent-browser
Give your agent a working browser
Read websites, interact with pages and capture screenshots in a separate local browser.
Your agent gets agent-browser’s MCP tools for opening pages, reading their contents and interacting with buttons and forms. The browser stays open between tools for the life of that connection.
For a first result, supply a page address and get its screenshot and readable accessibility snapshot. This browser has its own session: it does not inherit your usual browser’s accounts, extensions or saved passwords.
You bring
- a JSON object with url and optional width, height, full_page and wait_selector
page.json
You get
- a screenshot at the selected viewport or full page height
page.png - the page's readable accessibility tree
snapshot.txt - the page address, title, capture options and output checksums
page.json - agent-browser's navigation, page interaction and capture tools; browser state lasts for this MCP connection
Good to know
- This is a headless CPU browser, not a connection to your signed-in desktop browser. Sites may require login or block automation.
- Closing the MCP connection ends this browser process. Do not use it as persistent storage for an account or assume a new connection resumes an earlier page.
More setup notes
- Chromium's sandbox is disabled inside the container. UGT's container boundary still applies; do not expose this MCP server as an unauthenticated public service.
Your files & access
- The separate browser loads websites and the resources they request.
Licences & source
agent-browser Apache-2.0, with bundled notices; Chromium and its Debian dependencies retain their distribution notices. UGT's driver and checks are Apache-2.0.
What UGT sets up for you
- agent-browser at commit
e7519957b906
How was it tested?
Run on clean x86-64 (Intel/AMD) and ARM64 machines on 10 Nov 2026. Its check passed on a known sample and rejected deliberately broken results.
This checks the job this page describes, not every feature of the original project.
Automation
Watch for changes and send useful notifications.
- Sherlocksherlock-project
☆
Archived on GitHub
Find where a username is used
Check the sites you choose and save a spreadsheet-friendly report of matches and failed checks.
- ntfybinwiederhier
☆
Archived on GitHub
Send local notifications
Send messages from your local tools to named topics you can read in your browser.
- changedetection.iodgtlmoon
☆
Archived on GitHub
Track changes to web pages
Follow web pages and review changes to their text in a local dashboard.



