get_planner_stateLABSCO SUMMARY
Two tools, because seeing and acting are separate decisions.
Splitting state from execution means the model commits to a plan against a page it has actually read, rather than firing a click and hoping. That is a small surface — this is a hackathon project and it shows in the setup, which wants macOS, a specific Python, and Chrome closed before you begin. Recordings land under ./tmp/recordings, which is the fastest way to see what a run actually did.
What it is
A browser automation server built on Browser-Use. It drives Google Chrome and splits the loop in two — one call to see where things stand, another to act on it.
What you get
get_planner_statereturns the current browser state and planning contextexecute_actionsruns the actions you planned in the browser- Interactive element detection and manipulation on the live page
- Configurable browser contexts, with session recordings written to ./tmp/recordings
Requirements
macOS, Python 3.12 or higher, the uv package manager, and Google Chrome — closed before you start a task, since the server drives your installed browser. Clone the repository, uv venv and uv sync, then point your client at browser-use.py with uv --directory <YOUR_PATH_TO_MCP> run. It runs non-headless by default at a 1280x1100 window, which is intentional for development.
Setup effort
Build from source
USE CASES
Automating a flow on a site with no API
Read the page, decide the steps, and execute them against the real browser.
Checking what the page looks like right now
Pull the current state and planning context before deciding anything.
Reviewing what the run did
Watch the session recording rather than reconstructing it from logs.
2 tools
Listed in project docs. Your client may show a different list.
execute_actionsBEFORE YOU INSTALL
What to know first
Tools you get
2 tools named in the project's documentation.
Requires
Python 3.12 or later
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
MCP Clients
Claude Desktop
{
"mcpServers": {
"browser-use": {
"command": "uv",
"args": [
"--directory",
"<YOUR_PATH_TO_MCP>",
"run",
"browser-use.py"
]
}
}
}