Browser-Use MCP Server
The Browser-Use MCP Server enables AI-driven browser automation and web research via natural language commands using the Model Context Protocol (MCP).
Browser Automation: Execute tasks like navigation, form filling, and element interaction through natural language (
run_browser_agenttool).Deep Web Research: Perform multi-step research and generate detailed reports (
run_deep_researchtool).Visual Understanding: Analyze screenshots for vision-capable LLMs.
Multi-LLM Support: Integrates with OpenAI, Anthropic, Google, Mistral, Ollama, and other providers.
State Persistence: Manage browser sessions across multiple MCP calls or connect to user's browser via CDP.
CLI Interface: Access core functionalities directly for testing and scripting.
Artifact Management: Save agent history, browser traces, research reports, and downloaded files.
Environment Configuration: Fully configurable via environment variables using a structured Pydantic model.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
mcp-server-browser-use
MCP server that gives AI assistants the power to control a web browser.
Table of Contents
Related MCP server: jev-browser
What is this?
This wraps browser-use as an MCP server, letting Claude (or any MCP client) automate a real browserβnavigate pages, fill forms, click buttons, extract data, and more.
Why HTTP instead of stdio?
Browser automation tasks take 30-120+ seconds. The standard MCP stdio transport has timeout issues with long-running operationsβconnections drop mid-task. HTTP transport solves this by running as a persistent daemon that handles requests reliably regardless of duration.
Installation
Claude Code Plugin (Recommended)
Install as a Claude Code plugin for automatic setup:
# Install the plugin
/plugin install browser-use/mcp-browser-useThe plugin automatically:
Installs Playwright browsers on first run
Starts the HTTP daemon when Claude Code starts
Registers the MCP server with Claude
Set your API key (the browser agent needs an LLM to decide actions):
# Set API key (environment variable - recommended)
export GEMINI_API_KEY=your-key-here
# Or use config file
mcp-server-browser-use config set -k llm.api_key -v your-key-hereThat's it! Claude can now use browser automation tools.
Manual Installation
For other MCP clients or standalone use:
# Clone and install
git clone https://github.com/Saik0s/mcp-browser-use.git
cd mcp-server-browser-use
uv sync
# Install browser
uv run playwright install chromium
# Start the server
uv run mcp-server-browser-use serverAdd to Claude Desktop (~/Library/Application Support/Claude/claude_desktop_config.json):
{
"mcpServers": {
"browser-use": {
"type": "streamable-http",
"url": "http://localhost:8383/mcp"
}
}
}For MCP clients that don't support HTTP transport, use mcp-remote as a proxy:
{
"mcpServers": {
"browser-use": {
"command": "npx",
"args": ["mcp-remote", "http://localhost:8383/mcp"]
}
}
}Web UI
Access the task viewer at http://localhost:8383 when the daemon is running.
Features:
Real-time task list with status and progress
Task details with execution logs
Server health status and uptime
Running tasks monitoring
The web UI provides visibility into browser automation tasks without requiring CLI commands.
Web Dashboard
Access the full-featured dashboard at http://localhost:8383/dashboard when the daemon is running.
Features:
Tasks Tab: Complete task history with filtering, real-time status updates, and detailed execution logs
Skills Tab: Browse, inspect, and manage learned skills with usage statistics
History Tab: Historical view of all completed tasks with filtering by status and time
Key Capabilities:
Run existing skills directly from the dashboard with custom parameters
Start learning sessions to capture new skills
Delete outdated or invalid skills
Monitor running tasks with live progress updates
View full task results and error details
The dashboard provides a comprehensive web interface for managing all aspects of browser automation without CLI commands.
Configuration
Settings are stored in ~/.config/mcp-server-browser-use/config.json.
View current config:
mcp-server-browser-use config viewChange settings:
mcp-server-browser-use config set -k llm.provider -v openai
mcp-server-browser-use config set -k llm.model_name -v gpt-4o
# Note: Set API keys via environment variables (e.g., ANTHROPIC_API_KEY) for better security
# mcp-server-browser-use config set -k llm.api_key -v sk-...
mcp-server-browser-use config set -k browser.headless -v false
mcp-server-browser-use config set -k agent.max_steps -v 30Settings Reference
Key | Default | Description |
|
| LLM provider (anthropic, openai, google, azure_openai, groq, deepseek, cerebras, ollama, bedrock, browser_use, openrouter, vercel) |
|
| Model for the browser agent |
| - | API key for the provider (prefer env vars: GEMINI_API_KEY, ANTHROPIC_API_KEY, etc.) |
|
| Run browser without GUI |
| - | Connect to existing Chrome (e.g., http://localhost:9222) |
| - | Chrome profile directory for persistent logins/cookies |
|
| Enable Chromium sandboxing for security |
|
| Max steps per browser task |
|
| Enable vision capabilities for the agent |
|
| Max searches per research task |
| - | Timeout for individual searches |
|
| Server bind address |
|
| Server port |
| - | Directory to save results |
| - | Auth token for non-localhost connections |
|
| Enable skills system (beta - disabled by default) |
|
| Skills storage location |
|
| Validate skill execution results |
Config Priority
Environment Variables > Config File > DefaultsEnvironment variables use prefix MCP_ + section + _ + key (e.g., MCP_LLM_PROVIDER).
Using Your Own Browser
Option 1: Persistent Profile (Recommended)
Use a dedicated Chrome profile to preserve logins and cookies:
# Set user data directory
mcp-server-browser-use config set -k browser.user_data_dir -v ~/.chrome-browser-useOption 2: Connect to Existing Chrome
Connect to an existing Chrome instance (useful for advanced debugging):
# Launch Chrome with debugging enabled
google-chrome --remote-debugging-port=9222
# Configure CDP connection (localhost only for security)
mcp-server-browser-use config set -k browser.cdp_url -v http://localhost:9222CLI Reference
Server Management
mcp-server-browser-use server # Start as background daemon
mcp-server-browser-use server -f # Start in foreground (for debugging)
mcp-server-browser-use status # Check if running
mcp-server-browser-use stop # Stop the daemon
mcp-server-browser-use logs -f # Tail server logsCalling Tools
mcp-server-browser-use tools # List all available MCP tools
mcp-server-browser-use call run_browser_agent task="Go to google.com"
mcp-server-browser-use call run_deep_research topic="quantum computing"Configuration
mcp-server-browser-use config view # Show all settings
mcp-server-browser-use config set -k <key> -v <value>
mcp-server-browser-use config path # Show config file locationObservability
mcp-server-browser-use tasks # List recent tasks
mcp-server-browser-use tasks --status running
mcp-server-browser-use task <id> # Get task details
mcp-server-browser-use task cancel <id> # Cancel a running task
mcp-server-browser-use health # Server health + statsSkills Management
mcp-server-browser-use call skill_list
mcp-server-browser-use call skill_get name="my-skill"
mcp-server-browser-use call skill_delete name="my-skill"Tip: Skills can also be managed through the web dashboard at http://localhost:8383/dashboard for a visual interface with one-click execution and learning sessions.
MCP Tools
These tools are exposed via MCP for AI clients:
Tool | Description | Typical Duration |
| Execute browser automation tasks | 60-120s |
| Multi-search research with synthesis | 2-5 min |
| List learned skills | <1s |
| Get skill definition | <1s |
| Delete a skill | <1s |
| Server status and running tasks | <1s |
| Query task history | <1s |
| Get full task details | <1s |
run_browser_agent
The main tool. Tell it what you want in plain English:
mcp-server-browser-use call run_browser_agent \
task="Find the price of iPhone 16 Pro on Apple's website"The agent launches a browser, navigates to apple.com, finds the product, and returns the price.
Parameters:
Parameter | Type | Description |
| string | What to do (required) |
| int | Override default max steps |
| string | Use a learned skill |
| JSON | Parameters for the skill |
| bool | Enable learning mode |
| string | Name for the learned skill |
run_deep_research
Multi-step web research with automatic synthesis:
mcp-server-browser-use call run_deep_research \
topic="Latest developments in quantum computing" \
max_searches=5The agent searches multiple sources, extracts key findings, and compiles a markdown report.
Deep Research
Deep research executes a 3-phase workflow:
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
β Phase 1: PLANNING β
β LLM generates 3-5 focused search queries from topic β
βββββββββββββββββββββββββββββββ¬ββββββββββββββββββββββββββββ
βΌ
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
β Phase 2: SEARCHING β
β For each query: β
β β’ Browser agent executes search β
β β’ Extracts URL + summary from results β
β β’ Stores findings β
βββββββββββββββββββββββββββββββ¬ββββββββββββββββββββββββββββ
βΌ
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
β Phase 3: SYNTHESIS β
β LLM creates markdown report: β
β 1. Executive Summary β
β 2. Key Findings (by theme) β
β 3. Analysis and Insights β
β 4. Gaps and Limitations β
β 5. Conclusion with Sources β
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββReports can be auto-saved by configuring research.save_directory.
Observability
All tool executions are tracked in SQLite for debugging and monitoring.
Task Lifecycle
PENDING βββΊ RUNNING βββΊ COMPLETED
β
ββββΊ FAILED
ββββΊ CANCELLEDTask Stages
During execution, tasks progress through granular stages:
INITIALIZING β PLANNING β NAVIGATING β EXTRACTING β SYNTHESIZINGQuerying Tasks
List recent tasks:
mcp-server-browser-use tasksββββββββββββββββ¬ββββββββββββββββββββ¬ββββββββββββ¬βββββββββββ¬βββββββββββ
β ID β Tool β Status β Progress β Duration β
ββββββββββββββββΌββββββββββββββββββββΌββββββββββββΌβββββββββββΌβββββββββββ€
β a1b2c3d4 β run_browser_agent β completed β 15/15 β 45s β
β e5f6g7h8 β run_deep_research β running β 3/7 β 2m 15s β
ββββββββββββββββ΄ββββββββββββββββββββ΄ββββββββββββ΄βββββββββββ΄βββββββββββGet task details:
mcp-server-browser-use task a1b2c3d4Server health:
mcp-server-browser-use healthShows uptime, memory usage, and currently running tasks.
MCP Tools for Observability
AI clients can query task status directly:
health_check- Server status + list of running taskstask_list- Recent tasks with optional status filtertask_get- Full details of a specific task
Storage
Database:
~/.config/mcp-server-browser-use/tasks.dbRetention: Completed tasks auto-deleted after 7 days
Format: SQLite with WAL mode for concurrency
Skills System (Super Alpha)
Warning: This feature is experimental and under active development. Expect rough edges.
Skills are disabled by default. Enable them first:
mcp-server-browser-use config set -k skills.enabled -v trueSkills let you "teach" the agent a task once, then replay it 50x faster by reusing discovered API endpoints instead of full browser automation.
The Problem
Browser automation is slow (60-120 seconds per task). But most websites have APIs behind their UI. If we can discover those APIs, we can call them directly.
The Solution
Skills capture the API calls made during a browser session and replay them directly via CDP (Chrome DevTools Protocol).
Without Skills: Browser navigation β 60-120 seconds
With Skills: Direct API call β 1-3 secondsLearning a Skill
mcp-server-browser-use call run_browser_agent \
task="Find React packages on npmjs.com" \
learn=true \
save_skill_as="npm-search"What happens:
Recording: CDP captures all network traffic during execution
Analysis: LLM identifies the "money request"βthe API call that returns the data
Extraction: URL patterns, headers, and response parsing rules are saved
Storage: Skill saved as YAML to
~/.config/browser-skills/npm-search.yaml
Using a Skill
mcp-server-browser-use call run_browser_agent \
skill_name="npm-search" \
skill_params='{"query": "vue"}'Two Execution Modes
Every skill supports two execution paths:
1. Direct Execution (Fast Path) ~2 seconds
If the skill captured an API endpoint (SkillRequest):
Initialize CDP session
β
Navigate to domain (establish cookies)
β
Execute fetch() via Runtime.evaluate
β
Parse response with JSONPath
β
Return data2. Hint-Based Execution (Fallback) ~60-120 seconds
If direct execution fails or no API was found:
Inject navigation hints into task prompt
β
Agent uses hints as guidance
β
Agent discovers and calls API
β
Return dataSkill File Format
Skills are stored as YAML in ~/.config/browser-skills/:
name: npm-search
description: Search for packages on npmjs.com
version: "1.0"
# For direct execution (fast path)
request:
url: "https://www.npmjs.com/search?q={query}"
method: GET
headers:
Accept: application/json
response_type: json
extract_path: "objects[*].package"
# For hint-based execution (fallback)
hints:
navigation:
- step: "Go to npmjs.com"
url: "https://www.npmjs.com"
money_request:
url_pattern: "/search"
method: GET
# Auth recovery (if API returns 401/403)
auth_recovery:
trigger_on_status: [401, 403]
recovery_page: "https://www.npmjs.com/login"
# Usage stats
success_count: 12
failure_count: 1
last_used: "2024-01-15T10:30:00Z"Parameters
Skills support parameterized URLs and request bodies:
request:
url: "https://api.example.com/search?q={query}&limit={limit}"
body_template: '{"filters": {"category": "{category}"}}'Parameters are substituted at execution time from skill_params.
Auth Recovery
If an API returns 401/403, skills can trigger auth recovery:
auth_recovery:
trigger_on_status: [401, 403]
recovery_page: "https://example.com/login"
max_retries: 2The system will navigate to the recovery page (letting you log in) and retry.
Limitations
API Discovery: Only works if the site has an API. Sites that render everything server-side won't yield useful skills.
Auth State: Skills rely on browser cookies. If you're logged out, they may fail.
API Changes: If a site changes their API, the skill breaks. Falls back to hint-based execution.
Complex Flows: Multi-step workflows (login β navigate β search) may not capture cleanly.
REST API Reference
The server exposes REST endpoints for direct HTTP access. All endpoints return JSON unless otherwise specified.
Base URL
http://localhost:8383Health & Status
GET /api/health
Server health check with running task information.
curl http://localhost:8383/api/healthResponse:
{
"status": "healthy",
"uptime_seconds": 1234.5,
"memory_mb": 256.7,
"running_tasks": 2,
"tasks": [...],
"stats": {...}
}Tasks
GET /api/tasks
List recent tasks with optional filtering.
# List all tasks
curl http://localhost:8383/api/tasks
# Filter by status
curl http://localhost:8383/api/tasks?status=running
# Limit results
curl http://localhost:8383/api/tasks?limit=50GET /api/tasks/{task_id}
Get full details of a specific task.
curl http://localhost:8383/api/tasks/abc123GET /api/tasks/{task_id}/logs (SSE)
Real-time task progress stream via Server-Sent Events.
const events = new EventSource('/api/tasks/abc123/logs');
events.onmessage = (e) => console.log(JSON.parse(e.data));Skills
GET /api/skills
List all available skills.
curl http://localhost:8383/api/skillsResponse:
{
"skills": [
{
"name": "npm-search",
"description": "Search for packages on npmjs.com",
"success_rate": 92.5,
"usage_count": 15,
"last_used": "2024-01-15T10:30:00Z"
}
],
"count": 1,
"skills_directory": "/Users/you/.config/browser-skills"
}GET /api/skills/{name}
Get full skill definition as JSON.
curl http://localhost:8383/api/skills/npm-searchDELETE /api/skills/{name}
Delete a skill.
curl -X DELETE http://localhost:8383/api/skills/npm-searchPOST /api/skills/{name}/run
Execute a skill with parameters (starts background task).
curl -X POST http://localhost:8383/api/skills/npm-search/run \
-H "Content-Type: application/json" \
-d '{"params": {"query": "react"}}'Response:
{
"task_id": "abc123...",
"skill_name": "npm-search",
"message": "Skill execution started",
"status_url": "/api/tasks/abc123..."
}POST /api/learn
Start a learning session to capture a new skill (starts background task).
curl -X POST http://localhost:8383/api/learn \
-H "Content-Type: application/json" \
-d '{
"task": "Search for TypeScript packages on npmjs.com",
"skill_name": "npm-search"
}'Response:
{
"task_id": "def456...",
"learning_task": "Search for TypeScript packages on npmjs.com",
"skill_name": "npm-search",
"message": "Learning session started",
"status_url": "/api/tasks/def456..."
}Real-Time Updates
GET /api/events (SSE)
Server-Sent Events stream for all task updates.
const events = new EventSource('/api/events');
events.onmessage = (e) => {
const data = JSON.parse(e.data);
console.log(`Task ${data.task_id}: ${data.status}`);
};Event format:
{
"task_id": "abc123",
"full_task_id": "abc123-full-uuid...",
"tool": "run_browser_agent",
"status": "running",
"stage": "navigating",
"progress": {
"current": 5,
"total": 15,
"percent": 33.3,
"message": "Loading page..."
}
}Architecture
High-Level Overview
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
β MCP CLIENTS β
β (Claude Desktop, mcp-remote, CLI call) β
βββββββββββββββββββββββββββββββββββ¬ββββββββββββββββββββββββββββββββββββββββ
β HTTP POST /mcp
βΌ
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
β FastMCP SERVER β
β ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ β
β β MCP TOOLS β β
β β β’ run_browser_agent β’ skill_list/get/delete β β
β β β’ run_deep_research β’ health_check/task_list/task_get β β
β ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ β
ββββββββββ¬βββββββββββββββ¬ββββββββββββββββββ¬βββββββββββββββββ¬βββββββββββββββ
β β β β
βΌ βΌ βΌ βΌ
βββββββββββββββ βββββββββββββββ βββββββββββββββ βββββββββββββββββββββββ
β CONFIG β β PROVIDERS β β SKILLS β β OBSERVABILITY β
β Pydantic β β 12 LLMs β β Learn+Run β β Task Tracking β
βββββββββββββββ βββββββββββββββ βββββββββββββββ βββββββββββββββββββββββ
β
βΌ
βββββββββββββββββββββββββββ
β browser-use β
β (Agent + Playwright) β
βββββββββββββββββββββββββββModule Structure
src/mcp_server_browser_use/
βββ server.py # FastMCP server + MCP tools
βββ cli.py # Typer CLI for daemon management
βββ config.py # Pydantic settings
βββ providers.py # LLM factory (12 providers)
β
βββ observability/ # Task tracking
β βββ models.py # TaskRecord, TaskStatus, TaskStage
β βββ store.py # SQLite persistence
β βββ logging.py # Structured logging
β
βββ skills/ # Machine-learned browser skills
β βββ models.py # Skill, SkillRequest, AuthRecovery
β βββ store.py # YAML persistence
β βββ recorder.py # CDP network capture
β βββ analyzer.py # LLM skill extraction
β βββ runner.py # Direct fetch() execution
β βββ executor.py # Hint injection
β
βββ research/ # Deep research workflow
βββ models.py # SearchResult, ResearchSource
βββ machine.py # Plan β Search β SynthesizeFile Locations
What | Where |
Config |
|
Tasks DB |
|
Skills |
|
Server Log |
|
Server PID |
|
Supported LLM Providers
OpenAI
Anthropic
Google Gemini
Azure OpenAI
Groq
DeepSeek
Cerebras
Ollama (local)
AWS Bedrock
OpenRouter
Vercel AI
License
MIT
Available Tools
1 toolrun_browser_agentD
Handle run-browser-agent tool calls.
Inputs: task (required), add_infos.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelogβ¦
This server cannot be deployed
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'run_browser_agent' has a clearly distinct purpose with no other tools to confuse it with.
The naming pattern cannot be inconsistent with only one tool. The tool name 'run_browser_agent' follows a clear verb_noun pattern, and there are no other tools to deviate from this convention.
A single tool is too few for a server named 'Browser-Use MCP Server', which suggests a broader scope for browser automation. One tool feels thin and inadequate for handling various browser-related tasks like navigation, clicking, or form filling.
The tool set is severely incomplete for browser automation. With only a 'run_browser_agent' tool, there are obvious gaps in basic operations such as opening pages, interacting with elements, or retrieving content, making it impossible for agents to perform typical browser tasks.
Maintenance
Related MCP Connectors
Control a real browser from AI agents: navigate, click, type, screenshot, read the page.
Provides cloud browser automation capabilities using Stagehand and Browserbase, enabling LLMs to iβ¦
Browser agents and stealth cloud browsers for AI: run web tasks, fill forms, extract data.
Give AI agents a real cloud Chrome: open sessions, navigate, read pages, click, type and screenshot.
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables browser automation with anti-detection features, including navigation, interaction, form filling, and session management.2236 PyPI10MIT
- AlicenseNot gradedqualityBmaintenanceEnables browser automation through MCP with native Playwright operations, deterministic assertions, and natural-language grounded actions, structured extraction, and bounded agent workflows over live page elements.13Apache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to perform Playwright-compatible browser automation with persistent profiles, proxy routing, extension loading, and humanized mouse, keyboard, and scroll interactions over stdio, Streamable HTTP, npm, or Docker.431 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to drive a Chromium-based browser for web research, testing, and automation with Playwright-compatible tools, persistent profiles, proxy matching, extension loading, and humanized input across local or containerized deployments.431 npmMIT