browz-mcp
Run the Browz MCP server from Python tooling, and drive Browz from Python. Browz keeps each web account in its own isolated browser profile; the MCP server lets an AI agent list, create, start and stop those profiles, open pages, click, type, fill forms, read the page and take screenshots in them.
The MCP server ships inside the Browz desktop app. This package finds it and starts it, so Browz must be installed and open on the same computer (download).
Use it from an MCP client
uvx browz-mcp # stdio, for Claude Desktop, Claude Code, Cursor, Gemini CLI, …
pipx run browz-mcp # the same with pipx
uvx browz-mcp --http # local Streamable HTTP on 127.0.0.1
uvx browz-mcp --where # print the path of the server bundled with Browz
In a client's JSON config:
{ "mcpServers": { "browz": { "command": "uvx", "args": ["browz-mcp"] } } }
Claude Code: claude mcp add browz -- uvx browz-mcp.
Setup for every client (Claude, OpenAI, Grok, Gemini, Cursor, VS Code, agent frameworks) and the
remote server https://mcp.gobrowz.com/mcp: https://gobrowz.com/docs/ai-agents.html
The Python SDK
pip install browz-mcp
import os
from browz import Browz
bz = Browz(token=os.environ["BROWZ_TOKEN"]) # the Local API of the Browz app on this computer
profile = bz.profiles.create(name="research")
session = bz.browser.start(profile["id"])
print(session.cdp_endpoint) # connect Playwright, browser-use or Stagehand here
token can also be a local agent key (blcl_…) made in Browz or with bz.agent_keys.create();
the key then limits which routes, profiles and sites the client reaches. The owner manages keys with
bz.agent_keys (list, create, revoke, resume, stop_all, audit) and stored credentials with
bz.credentials (list, add, update, remove). No method returns a stored password or TOTP seed.
browz.agents has session helpers for browser-use and LangChain. No dependencies; the
playwright extra pins the Playwright version Browz is tested with.
mcp-name: com.gobrowz/browz
Metadata
Release files for browz-mcp 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| browz_mcp-0.1.0.tar.gz | 29.4 kB | Without provenance | Details for browz_mcp-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| browz_mcp-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for browz_mcp-0.1.0-py3-none-any.whl |
Total release size: 48.1 kB
Release files / browz_mcp-0.1.0.tar.gz
| Download URL | browz_mcp-0.1.0.tar.gz |
|---|---|
| Size | 29.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cf292f52d03ffe112d48e7d60607918f12e021a74cccaed741fc914c0c6039d3
|
|
BLAKE2b-256 checksum How to use checksums |
f0157b6367ac26ae5969c5dd8594d5464e36b88ebb1eef43c01c5b78cb9dad1a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.12.22 {"installer":{"name":"uv","version":"0.12.22","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / browz_mcp-0.1.0-py3-none-any.whl
| Download URL | browz_mcp-0.1.0-py3-none-any.whl |
|---|---|
| Size | 18.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f009d04ba1dd990900f0a024f5f9eede79ee3e0d8544e74040800113faab2091
|
|
BLAKE2b-256 checksum How to use checksums |
312f727e0f19c0e54aaf42ba17073502a1a33a8e22434845b24fbd8034f0ea41
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.12.22 {"installer":{"name":"uv","version":"0.12.22","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for browz-mcp 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.