FastAPI server implementing MCP protocol Browser automation via browser-use library.
If you already use W/ Browser Use, the w/ browser use mcp server is the piece that lets your assistant work with it directly. FastAPI server implementing MCP protocol Browser automation via browser-use library.
This repository provides a production-ready wrapper around the browser-use automation engine. It exposes a single MCP tool (run_browser_agent) that orchestrates a browser session, executes the browser-use agent, and returns the final result back to the client. The refactored layout focuses on keeping configuration in one place, improving testability, and keeping browser-use upgrades isolated from MCP specific code.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Optional — Claude Desktop or another MCP-compatible client for integration testingProvider — specific API keys and endpoints (ANTHROPIC_API_KEY, OPENAI_API_KEY, DEEPSEEK_API_KEY, GOOGLE_API_KEY, AZURE_OPENAI_API_KEY, etc.)Requirements — The Requirements tool exposed by this serverInstallation — Copy sample.env to .env (or export the variables in another way) and update the values for the providers you plan to useDebugging — For interactive debugging, use the MCP Inspector:Configuration is passed through the environment: MCP_MODEL_PROVIDER, MCP_MODEL_NAME, ANTHROPIC_API_KEY, OPENAI_API_KEY, DEEPSEEK_API_KEY, GOOGLE_API_KEY, AZURE_OPENAI_API_KEY, BROWSER_USE_PROXY_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
uv for dependency management (recommended) - Optional: Claude Desktop or another MCP-compatible client for integration testingInstallation goes through your MCP client rather than a global install: point it at @modelcontextprotocol/inspector on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Among the browser automation options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. W/ Browser Use's toolset — Optional, Provider, Requirements and 2 more — is a fair guide to whether it matches your workflow. It is maintained by JovaniPink; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Optional | Claude Desktop or another MCP-compatible client for integration testing |
| Provider | specific API keys and endpoints (ANTHROPIC_API_KEY, OPENAI_API_KEY, DEEPSEEK_API_KEY, GOOGLE_API_KEY, AZURE_OPENAI_API_KEY, etc.). |
| Requirements | The Requirements tool exposed by this server. |
| Installation | Copy sample.env to .env (or export the variables in another way) and update the values for the providers you plan to use. |
| Debugging | For interactive debugging, use the [MCP Inspector](https://github.com/modelcontextprotocol/inspector): |
{
"mcpServers": {
"browser-use-jovanipink": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/inspector"],
"env": {
"MCP_MODEL_PROVIDER": "your-value",
"MCP_MODEL_NAME": "your-value",
"ANTHROPIC_API_KEY": "your-value",
"OPENAI_API_KEY": "your-value",
"DEEPSEEK_API_KEY": "your-value",
"GOOGLE_API_KEY": "your-value",
"AZURE_OPENAI_API_KEY": "your-value",
"BROWSER_USE_PROXY_URL": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
uv for dependency management (recommended) - Optional: Claude Desktop or another MCP-compatible client for integration testing| Variable | Description | Required |
|---|---|---|
| MCP_MODEL_PROVIDER | Configuration value read at startup. | Optional |
| MCP_MODEL_NAME | Configuration value read at startup. | Optional |
| ANTHROPIC_API_KEY | Credential the server authenticates with. | Yes |
| OPENAI_API_KEY | Credential the server authenticates with. | Yes |
| DEEPSEEK_API_KEY | Credential the server authenticates with. | Yes |
| GOOGLE_API_KEY | Credential the server authenticates with. | Yes |
| AZURE_OPENAI_API_KEY | Credential the server authenticates with. | Yes |
| BROWSER_USE_PROXY_URL | Endpoint or connection string the server talks to. | Yes |
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
Industrial-strength web extraction — render, scrape, crawl and search entire sites into clean markdown.
The original Chromium automation reference server — simple, screenshot-driven browser control.
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Puppeteer-powered browser control that drives pages from the accessibility tree instead of pixels.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.