Browser Use MCP Server
Browser Use MCP Server is an MCP server published by Browser Use, verified on MCP revision 2025-11-25; support for the current revision (2026-07-28) is not yet confirmed. It is the first-party server from Browser Use. Last verified 2026-08-20.
Does Browser Use MCP Server support the current MCP specification (2026-07-28)?
Not yet confirmed. Browser Use MCP Server is verified on revision 2025-11-25; we have not confirmed support for the current revision (2026-07-28) as of 2026-08-20.
Is Browser Use MCP Server a first-party (official) MCP server?
Yes. Browser Use MCP Server is the first-party MCP server published by Browser Use (last verified 2026-08-20).
How do I connect to Browser Use MCP Server?
Browser Use MCP Server is available via the package pypi:browser-use, the official MCP Registry under com.browser-use/browser-use, the source repository at https://github.com/browser-use/browser-use. Authentication: none. Transports: stdio.
Does Browser Use MCP Server support MCP revision 2025-11-25?
Yes. Browser Use MCP Server supports MCP revision 2025-11-25 (checked 2026-08-20).
Does Browser Use MCP Server support MCP revision 2026-07-28?
No. Browser Use MCP Server was checked against MCP revision 2026-07-28 and does not support it (checked 2026-08-20).
When were Browser Use MCP Server's facts last verified?
2026-08-20. Each fact on this page links to the sources used to verify it.
Browser Use is a browser automation library whose MCP server ships
inside the main browser-use Python package rather than as a separate
artifact. The codebase carries two stdio server variants. The --mcp
flag starts the full-featured server documented on docs.browser-use.com,
with tools such as browser_navigate, browser_click, browser_type,
browser_get_state, and browser_extract_content, plus an agent tool
that requires an LLM API key in the environment. The --cli-mcp flag
starts a minimal two-tool server: browser_exec, which runs Python
snippets against a browser-harness session, and browser_screenshot.
The distinction matters because the registry entry and the docs point at
different variants. The in-repo server.json that feeds the official
registry launches the package with --cli-mcp, so a client installing
from the registry record gets the minimal exec-style server, not the
tool set the public docs walk through. Neither variant carries MCP-level
authentication; both run locally.
Browser Use also operates a hosted MCP endpoint at
https://api.browser-use.com/v3/mcp, authorized with an
x-browser-use-api-key header and exposing cloud session-management
tools. That service has a different tool surface from the local server
and is not covered by this record.
Authority rests on the domain-verified com.browser-use registry
namespace, the GitHub-verified browser-use organization, and the
README's registry ownership comment. No surface names a supported MCP
specification revision; the library pins the Python mcp==1.26.0 SDK,
which is not evidence of revision support. spec_status is therefore
unknown. The registry record (0.13.5) trails the repository's latest
release (0.13.7, 2026-07-27) by two releases.
Which MCP spec revisions does Browser Use MCP Server support?
Browser Use MCP Server has 2 verified spec-support records. Each row lists the revision, the verified status, the evidence URL, and the date that fact was last checked.
| Spec revision | Status | Last checked | Evidence |
|---|---|---|---|
| MCP 2025-11-25 | Supported | Source | |
| MCP 2026-07-28 | Not supported | Source |
How widely adopted is Browser Use MCP Server?
Ranked #6 in The MCP 500 with Adoption Index 79.17 (snapshot , methodology v1).
| Measurement | Value | Source |
|---|---|---|
| Official MCP Registry | yes | API · |
| Docker MCP Catalog | no | API · |
| GitHub stars | 114,702 | API · |
| GitHub forks | 12,609 | API · |
| Last push | 2026-09-15T01:14:00Z | API · |
| Repository archived | no | API · |
Repository and package signals for Browser Use MCP Server
Measured directly from the source registries, not asserted from a document. Each figure carries the date it was read; none of it affects the verified spec status above.
Repository as of
- Created
- Open issues
- 390
- Primary language
- Python
- License (repository)
- MIT
- Continuous integration
- Present
- Tests
- Present
- Security policy
- None
Declared topics: ai-agents, ai-tools, browser-automation, browser-use, llm, playwright, python — author-declared on the repository, not our taxonomy.
Package (pypi) as of
- Latest version
0.13.8- Last published
- First published
- Releases
- 137
- Direct dependencies
- 60
- Unpacked size
- 705 KB
- Registry signature
- Not measured
- Build provenance
- No attestation
How was this verified, and what are the sources?
Verified · method: sdk-protocol-constant
· confidence 0.85 (Good).
- Official MCP Registry record com.browser-use/browser-use version 0.13.5 (published 2026-07-17) - pypi package browser-use, stdio transport, website browser-use.com; the com.* namespace requires domain verification - accessed
- browser-use/browser-use repository - README's first line carries the registry ownership comment "mcp-name: com.browser-use/browser-use"; the in-repo server.json launches the pypi package with the positional argument --cli-mcp; the repo's browser_use/mcp/ package contains both server.py (--mcp, tools including browser_navigate, browser_click, browser_type, browser_get_state, browser_extract_content) and cli_mcp.py (--cli-mcp, tools browser_exec and browser_screenshot) - accessed
- Browser Use open-source MCP docs - documents running the server via uvx --from 'browser-use[cli]' browser-use --mcp in stdio mode, with LLM API keys passed as environment variables - accessed
- Browser Use cloud MCP docs - document a separate hosted endpoint at https://api.browser-use.com/v3/mcp authorized with an x-browser-use-api-key header, exposing session-management tools (run_session, get_session, send_task, stop_session); a distinct product from the local stdio server this record covers - accessed
- browser-use/browser-use releases - 0.13.5 (2026-07-17) notes "support MCP registry" via PR #5242; 0.13.6 and 0.13.7 (2026-07-27) have since shipped, so the registry record trails the repo by two releases - accessed
- Staleness re-verification via the GitHub API - repository browser-use/browser-use active (pushed 2026-08-14, not archived), latest release 0.13.7 (2026-07-27); entity facts unchanged - accessed
- PyPI metadata for browser-use at published version 0.13.8, retrieved 2026-08-20 - declares a dependency on mcp, which resolves to mcp@1.26.0 - accessed
- Published artifact of mcp@1.26.0, retrieved 2026-08-20 - the artifact declares LATEST_PROTOCOL_VERSION 2025-11-25 and carries no 2026-07-28 implementation. Read from the artifact itself, not from release notes - accessed