Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

com.browser-use/browser-use

PYPI · BROWSER-USE · SCANNED SEP 20

Control a real Chrome browser to complete any task: fill forms, extract data, book flights.

Available components

pypi · browser-use 0
−69 this week 0 Trust /100

Recent critical change

CVE-2026-63374 affects this package (19 Sept 2026). See the changelog before you install this server.

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security72
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: an unpatched critical CVE affects this package; the score is capped at 0. See how to fix → View diagnostics → Fail
  • Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
  • Dependency health was assessed across the 245 of 308 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency35
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • License check failed: the license (MIT License) isn't a recognized OSI-approved license. See how to fix → Fail
  • Actively maintained (last published 16 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability57
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1582 tokens (~791/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
  • Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "browser_exec" implies "exec" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the com.browser-use/browser-use MCP server?

com.browser-use/browser-use runs locally as a PyPI package, launched with uvx browser-use. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · browser-use

# add to Claude Code
claude mcp add com-browser-use-browser-use -- uvx browser-use
// .cursor/mcp.json
{
  "mcpServers": {
    "com-browser-use-browser-use": {
      "command": "uvx",
      "args": [
        "browser-use"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-browser-use-browser-use": {
      "command": "uvx",
      "args": [
        "browser-use"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add com-browser-use-browser-use -- uvx browser-use
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-browser-use-browser-use": {
      "type": "local",
      "command": [
        "uvx",
        "browser-use"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-browser-use-browser-use --command uvx --arg browser-use
# ~/.hermes/config.yaml
mcp_servers:
  com-browser-use-browser-use:
    command: "uvx"
    args: ["browser-use"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-browser-use-browser-use": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "browser-use"
      ]
    }
  }
}
# add to Vellum
assistant mcp add com-browser-use-browser-use -t stdio -c uvx -a browser-use
// mcp.json
{
  "mcpServers": {
    "com-browser-use-browser-use": {
      "command": "uvx",
      "args": [
        "browser-use"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Sept 26 0
    • Stability: pass → 0.80 functional
  • 19 Sept 26 −71
    • CVE-2026-63374 affects this package: high ▼ critical
    • Score status: scored → failed ▼ critical
    • Known CVEs: CVE check failed: an unpatched critical CVE affects this package; the score is capped at 0. critical
    • Stability: 0.97 → pass security
  • 18 Sept 26 0
    • CVE-2026-54276 affects this package: high ▼ security
    • CVE-2026-54531 affects this package: high ▼ security
    • CVE-2026-59199 affects this package: high ▼ security
    • CVE-2026-54059 affects this package: high ▼ security
    • CVE-2026-59938 affects this package: high ▼ security
    • CVE-2026-54278 affects this package: high ▼ security
    • CVE-2026-54651 affects this package: high ▼ security
    • CVE-2026-59950 affects this package: high ▼ security
    • CVE-2026-59203 affects this package: high ▼ security
    • CVE-2026-7246 affects this package: high ▼ security
    • CVE-2026-69243 affects this package: high ▼ security
    • CVE-2026-84311 affects this package: high ▼ security
    • CVE-2026-59937 affects this package: high ▼ security
    • CVE-2026-54058 affects this package: high ▼ security
    • CVE-2026-48735 affects this package: high ▼ security
    • CVE-2026-54530 affects this package: high ▼ security
    • CVE-2026-59205 affects this package: high ▼ security
    • CVE-2026-59198 affects this package: high ▼ security
    • CVE-2026-47265 affects this package: high ▼ security
    • CVE-2026-69244 affects this package: high ▼ security
    • CVE-2026-54279 affects this package: high ▼ security
    • CVE-2026-54277 affects this package: high ▼ security
    • CVE-2026-59204 affects this package: high ▼ security
    • CVE-2026-48155 affects this package: high ▼ security
    • CVE-2026-54275 affects this package: high ▼ security
    • CVE-2026-54280 affects this package: high ▼ security
    • CVE-2026-54060 affects this package: high ▼ security
    • CVE-2026-82398 affects this package: high ▼ security
    • CVE-2026-49461 affects this package: high ▼ security
    • CVE-2026-52869 affects this package: high ▼ security
    • CVE-2026-49460 affects this package: high ▼ security
    • CVE-2026-52870 affects this package: high ▼ security
    • CVE-2026-59197 affects this package: high ▼ security
    • CVE-2026-34993 affects this package: high ▼ security
    • CVE-2026-59935 affects this package: high ▼ security
    • CVE-2026-59936 affects this package: high ▼ security
    • CVE-2026-54273 affects this package: high ▼ security
    • CVE-2026-59200 affects this package: high ▼ security
    • CVE-2026-50269 affects this package: high ▼ security
    • CVE-2026-55380 affects this package: high ▼ security
    • CVE-2026-59881 affects this package: high ▼ security
    • CVE-2026-54274 affects this package: high ▼ security
    • CVE-2026-84309 affects this package: high ▼ security
    • CVE-2026-57204 affects this package: high ▼ security
    • CVE-2026-71870 affects this package: high ▼ security
    • CVE-2026-55798 affects this package: high ▼ security
    • CVE-2026-71852 affects this package: high ▼ security
    • CVE-2026-55379 affects this package: high ▼ security
    • CVE-2026-84310 affects this package: high ▼ security
    • CVE-2026-48156 affects this package: high ▼ security
  • 17 Sept 26 +1
    • CVE-2026-54058 affects this package: high ▼ security
    • CVE-2026-34993 affects this package: high ▼ security
    • CVE-2026-59197 affects this package: high ▼ security
    • CVE-2026-52870 affects this package: high ▼ security
    • CVE-2026-49460 affects this package: high ▼ security
    • CVE-2026-52869 affects this package: high ▼ security
    • CVE-2026-49461 affects this package: high ▼ security
    • CVE-2026-82398 affects this package: high ▼ security
    • CVE-2026-54060 affects this package: high ▼ security
    • CVE-2026-54280 affects this package: high ▼ security
    • CVE-2026-54275 affects this package: high ▼ security
    • CVE-2026-48155 affects this package: high ▼ security
    • CVE-2026-59204 affects this package: high ▼ security
    • CVE-2026-54277 affects this package: high ▼ security
    • CVE-2026-54279 affects this package: high ▼ security
    • CVE-2026-69244 affects this package: high ▼ security
    • CVE-2026-47265 affects this package: high ▼ security
    • CVE-2026-59198 affects this package: high ▼ security
    • CVE-2026-59205 affects this package: high ▼ security
    • CVE-2026-54530 affects this package: high ▼ security
    • CVE-2026-48735 affects this package: high ▼ security
    • CVE-2026-59937 affects this package: high ▼ security
    • CVE-2026-84311 affects this package: high ▼ security
    • CVE-2026-69243 affects this package: high ▼ security
    • CVE-2026-7246 affects this package: high ▼ security
    • CVE-2026-59203 affects this package: high ▼ security
    • CVE-2026-59950 affects this package: high ▼ security
    • CVE-2026-54651 affects this package: high ▼ security
    • CVE-2026-54278 affects this package: high ▼ security
    • CVE-2026-59938 affects this package: high ▼ security
    • CVE-2026-54059 affects this package: high ▼ security
    • CVE-2026-59199 affects this package: high ▼ security
    • CVE-2026-54531 affects this package: high ▼ security
    • CVE-2026-54276 affects this package: high ▼ security
    • CVE-2026-48156 affects this package: high ▼ security
    • CVE-2026-84310 affects this package: high ▼ security
    • CVE-2026-55379 affects this package: high ▼ security
    • CVE-2026-71852 affects this package: high ▼ security
    • CVE-2026-55798 affects this package: high ▼ security
    • CVE-2026-59935 affects this package: high ▼ security
    • CVE-2026-59936 affects this package: high ▼ security
    • CVE-2026-54273 affects this package: high ▼ security
    • CVE-2026-59200 affects this package: high ▼ security
    • CVE-2026-50269 affects this package: high ▼ security
    • CVE-2026-55380 affects this package: high ▼ security
    • CVE-2026-59881 affects this package: high ▼ security
    • CVE-2026-54274 affects this package: high ▼ security
    • CVE-2026-84309 affects this package: high ▼ security
    • CVE-2026-71870 affects this package: high ▼ security
    • CVE-2026-57204 affects this package: high ▼ security
  • 16 Sept 26 0
    • CVE-2026-69243 affects this package: high ▼ security
    • CVE-2026-34993 affects this package: high ▼ security
    • CVE-2026-59197 affects this package: high ▼ security
    • CVE-2026-52870 affects this package: high ▼ security
    • CVE-2026-49460 affects this package: high ▼ security
    • CVE-2026-52869 affects this package: high ▼ security
    • CVE-2026-49461 affects this package: high ▼ security
    • CVE-2026-82398 affects this package: high ▼ security
    • CVE-2026-54060 affects this package: high ▼ security
    • CVE-2026-54280 affects this package: high ▼ security
    • CVE-2026-54275 affects this package: high ▼ security
    • CVE-2026-48155 affects this package: high ▼ security
    • CVE-2026-59204 affects this package: high ▼ security
    • CVE-2026-54277 affects this package: high ▼ security
    • CVE-2026-54279 affects this package: high ▼ security
    • CVE-2026-69244 affects this package: high ▼ security
    • CVE-2026-47265 affects this package: high ▼ security
    • CVE-2026-59198 affects this package: high ▼ security
    • CVE-2026-59205 affects this package: high ▼ security
    • CVE-2026-54530 affects this package: high ▼ security
    • CVE-2026-48735 affects this package: high ▼ security
    • CVE-2026-54058 affects this package: high ▼ security
    • CVE-2026-59937 affects this package: high ▼ security
    • CVE-2026-84311 affects this package: high ▼ security
    • CVE-2026-7246 affects this package: high ▼ security
    • CVE-2026-59203 affects this package: high ▼ security
    • CVE-2026-59950 affects this package: high ▼ security
    • CVE-2026-54651 affects this package: high ▼ security
    • CVE-2026-54278 affects this package: high ▼ security
    • CVE-2026-59938 affects this package: high ▼ security
    • CVE-2026-54059 affects this package: high ▼ security
    • CVE-2026-59199 affects this package: high ▼ security
    • CVE-2026-54531 affects this package: high ▼ security
    • CVE-2026-54276 affects this package: high ▼ security
    • CVE-2026-48156 affects this package: high ▼ security
    • CVE-2026-84310 affects this package: high ▼ security
    • CVE-2026-55379 affects this package: high ▼ security
    • CVE-2026-71852 affects this package: high ▼ security
    • CVE-2026-55798 affects this package: high ▼ security
    • CVE-2026-59935 affects this package: high ▼ security
    • CVE-2026-59936 affects this package: high ▼ security
    • CVE-2026-54273 affects this package: high ▼ security
    • CVE-2026-59200 affects this package: high ▼ security
    • CVE-2026-50269 affects this package: high ▼ security
    • CVE-2026-55380 affects this package: high ▼ security
    • CVE-2026-59881 affects this package: high ▼ security
    • CVE-2026-54274 affects this package: high ▼ security
    • CVE-2026-84309 affects this package: high ▼ security
    • CVE-2026-71870 affects this package: high ▼ security
    • CVE-2026-57204 affects this package: high ▼ security
  • 15 Sept 26 +1

    We did not load change detail this far back for this component, so this day may have recorded more than is shown.

    • CVE-2026-84309 affects this package: high ▼ security
    • CVE-2026-34993 affects this package: high ▼ security
    • CVE-2026-59197 affects this package: high ▼ security
    • CVE-2026-52870 affects this package: high ▼ security
    • CVE-2026-49460 affects this package: high ▼ security
    • CVE-2026-52869 affects this package: high ▼ security
    • CVE-2026-49461 affects this package: high ▼ security
    • CVE-2026-82398 affects this package: high ▼ security
    • CVE-2026-54060 affects this package: high ▼ security
    • CVE-2026-54280 affects this package: high ▼ security
    • CVE-2026-54275 affects this package: high ▼ security
    • CVE-2026-48155 affects this package: high ▼ security
    • CVE-2026-59204 affects this package: high ▼ security
    • CVE-2026-54277 affects this package: high ▼ security
    • CVE-2026-54279 affects this package: high ▼ security
    • CVE-2026-69244 affects this package: high ▼ security
    • CVE-2026-47265 affects this package: high ▼ security
    • CVE-2026-59198 affects this package: high ▼ security
    • CVE-2026-59205 affects this package: high ▼ security
    • CVE-2026-54530 affects this package: high ▼ security
    • CVE-2026-48735 affects this package: high ▼ security
    • CVE-2026-57204 affects this package: high ▼ security
    • CVE-2026-54058 affects this package: high ▼ security
    • CVE-2026-59937 affects this package: high ▼ security
    • CVE-2026-71870 affects this package: high ▼ security
    • CVE-2026-84311 affects this package: high ▼ security
    • CVE-2026-69243 affects this package: high ▼ security
    • CVE-2026-7246 affects this package: high ▼ security
    • CVE-2026-59203 affects this package: high ▼ security
    • CVE-2026-59950 affects this package: high ▼ security
    • CVE-2026-54651 affects this package: high ▼ security
    • CVE-2026-54278 affects this package: high ▼ security
    • CVE-2026-59938 affects this package: high ▼ security
    • CVE-2026-54059 affects this package: high ▼ security
    • CVE-2026-59199 affects this package: high ▼ security
    • CVE-2026-54531 affects this package: high ▼ security
    • CVE-2026-54276 affects this package: high ▼ security
    • CVE-2026-48156 affects this package: high ▼ security
    • CVE-2026-84310 affects this package: high ▼ security
    • CVE-2026-55379 affects this package: high ▼ security
    • CVE-2026-71852 affects this package: high ▼ security
    • CVE-2026-55798 affects this package: high ▼ security
  • 13 Sept 26 −3

    We did not load change detail this far back for this component, so this day may have recorded more than is shown.

  • 12 Sept 26 +1

    We did not load change detail this far back for this component, so this day may have recorded more than is shown.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Analysed pypi/browser-use@0.13.5

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build

Background: Why install scripts are a supply-chain risk →

Vulnerabilities 100 findings
ID CVE Severity Vector Fix available
GHSA-2fqr-mr3j-6wp8 CVE-2026-54279 low yes
GHSA-4fvr-rgm6-gqmc CVE-2026-54273 medium yes
GHSA-4m7w-qmgq-4wj5 CVE-2026-54275 low yes
GHSA-63hw-fmq6-xxg2 CVE-2026-54277 medium yes
GHSA-9x8q-7h8h-wcw9 CVE-2026-54280 low yes
GHSA-cq5v-8q36-5273 CVE-2026-69244 high yes
GHSA-g3cq-j2xw-wf74 CVE-2026-54278 medium yes
GHSA-hg6j-4rv6-33pg CVE-2026-47265 medium yes
GHSA-hpj7-wq8m-9hgp CVE-2026-54276 medium yes
GHSA-jg22-mg44-37j8 CVE-2026-34993 medium CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:C/C:L/I:H/A:L yes
GHSA-m6qw-4cw2-hm4m CVE-2026-50269 low yes
GHSA-mfx4-hv73-q22v CVE-2026-69243 medium yes
GHSA-mq44-7p77-q5h7 CVE-2026-59881 medium yes
GHSA-xcgm-r5h9-7989 CVE-2026-54274 medium yes
PYSEC-2026-2104 CVE-2026-34993 high CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H yes
PYSEC-2026-2105 CVE-2026-47265 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N yes
PYSEC-2026-2106 CVE-2026-50269 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
PYSEC-2026-2107 CVE-2026-54273 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
PYSEC-2026-2108 CVE-2026-54274 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
PYSEC-2026-2109 CVE-2026-54276 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N yes
PYSEC-2026-2110 CVE-2026-54277 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
PYSEC-2026-2111 CVE-2026-54278 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
PYSEC-2026-2112 CVE-2026-54279 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
PYSEC-2026-2113 CVE-2026-54280 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
PYSEC-2026-237 CVE-2026-54275 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
PYSEC-2026-3545 CVE-2026-69244 none yes
PYSEC-2026-3546 CVE-2026-69243 none yes
PYSEC-2026-3547 CVE-2026-59881 none yes
GHSA-5p39-cfhj-2xmp CVE-2026-64847 medium yes
GHSA-82r6-8w77-94w6 CVE-2026-63374 critical yes
PYSEC-2026-2132 CVE-2026-7246 high CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:C/C:H/I:H/A:H yes
GHSA-hvrp-rf83-w775 CVE-2026-52870 high CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L yes
GHSA-jpw9-pfvf-9f58 CVE-2026-52869 high CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L yes
GHSA-vj7q-gjh5-988w CVE-2026-59950 high yes
PYSEC-2026-3481 CVE-2026-52870 high CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L yes
PYSEC-2026-3482 CVE-2026-52869 high CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L yes
PYSEC-2026-3483 CVE-2026-59950 none yes
GHSA-45hq-cxwh-f6vc CVE-2026-55379 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-4x4j-2g7c-83w6 CVE-2026-55798 medium CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L yes
GHSA-5x94-69rx-g8h2 CVE-2026-54060 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-62p4-gmf7-7g93 CVE-2026-54058 high yes
GHSA-6r8x-57c9-28j4 CVE-2026-59199 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-8v84-f9pq-wr9x CVE-2026-54059 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-9hw9-ch79-4vh6 CVE-2026-59205 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-fj7v-r99m-22gq CVE-2026-59198 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:L yes
GHSA-jjj6-mw9f-p565 CVE-2026-59200 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-pg7v-jwj7-p798 CVE-2026-59203 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L yes
GHSA-phj9-mv4w-65pm CVE-2026-55380 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-vjc4-5qp5-m44j CVE-2026-59204 high yes
GHSA-xj96-63gp-2gmr CVE-2026-59197 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H yes

Showing 50 of 100 vulnerabilities.

Background: What a vulnerability scan can and cannot prove →

Dependencies 245 packages
Packages resolved 245
Stale 12
No linked repository 1
Tree resolution Partial

The dependency tree was only partially resolved, so these counts may be incomplete.

Background: SBOMs and build attestations, explained →

MCP tools · 2 exposed · ~167 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
browser_exec ~93

Execute Python in the browser-harness session. Helpers like new_tab(url), goto_url(url), page_info(), click_at_xy(x, y), type_text(text), js(code), cdp(method, ...), wait_for_load(), list_tabs() are pre-imported. The namespace persists across calls. Returns whatever the code prints. First navigation should be new_tab(url).

NameTypeReqDescription
codestringyesPython code to execute

No output schema declared.

No examples provided.

browser_screenshot ~74

Capture the current page and return it as an image. Prefer this over capture_screenshot() in browser_exec.

NameTypeReqDescription
fullboolean–Capture beyond the viewport (full page)
max_diminteger–Downscale so no side exceeds this many pixels (e.g. 1800 for 2x displays)

No output schema declared.

No examples provided.

Common questions

What is the com.browser-use/browser-use MCP server?

com.browser-use/browser-use is an MCP server listed in the public MCP registry as com.browser-use/browser-use. Control a real Chrome browser to complete any task: fill forms, extract data, book flights. This page covers its PyPI package (browser-use).

What tools does the com.browser-use/browser-use MCP server expose?

com.browser-use/browser-use exposes 2 tools: browser_exec, browser_screenshot. Their descriptions and schemas cost roughly 167 tokens of context every time the server is loaded.

Is the com.browser-use/browser-use MCP server still maintained?

com.browser-use/browser-use is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.