Power your agent
Yayıncıdan kurulum. PlugMCP uç noktası değildir.
Host a copy with our keys and logs.
Registry'de henüz paketlenmiş bir sürüm yok. Deponun README dosyasını izleyin.
Uzak URL mi, yoksa makinenizde bir komut mu? İki kurulum arasındaki fark
PlugMCP’de çalıştır
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
BaşlatOpenBrowser is browser infrastructure for AI agents: isolated Chrome sessions, persistent profiles, proxy-aware identities, human login handoff, a remote API, and MCP tools.
It lets Claude, Codex, Cursor, browser-use, OpenBrowser-style agents, and custom workers share real Chrome browsers without fighting over one CDP port. Agents lease a browser, use a named profile when account state is needed, route selected identities through proxies, hand login challenges to a human, and leave behind telemetry plus issue reports that can be audited later.
flowchart LR
Agent["Agent\nClaude / Codex / Cursor / worker"] --> Client["MCP or API client"]
Client --> Broker["OpenBrowser Broker"]
Broker --> Lease["Lease manager"]
Broker --> Profiles["Profile + identity manager"]
Broker --> Proxy["Proxy router"]
Broker --> Observability["Telemetry + feedback + audit"]
Lease --> Pool["Chrome pool"]
Profiles --> Pool
Proxy --> Pool
Pool --> Slots["pool-a ... pool-N\nisolated CDP sessions"]
Most browser agents break in the same ways:
OpenBrowser gives agents one operating contract: lease, act, release, report.
proxy_ref./openbrowser/v1 API for agents on any machine.sequenceDiagram
participant A as Agent
participant B as OpenBrowser Broker
participant C as Chrome slot
participant H as Human auth portal
A->>B: lease(owner, identity_id?)
B->>C: reserve isolated Chrome session
B-->>A: lease_id
A->>B: navigate / click / type / screenshot
B->>C: browser action over CDP
C-->>B: page state
B-->>A: snapshot or result
alt login or challenge required
A->>B: auth_request
B-->>H: one-time portal URL
H->>C: human completes login
end
A->>B: release(lease_id)
B->>B: telemetry + feedback + audit trail
git clone https://github.com/floomhq/openbrowser.git
cd openbrowser
python3 -m venv .venv
. .venv/bin/activate
pip install -e .
playwright install chromium
cp .env.example .env
cp config/identities.example.json config/identities.local.json
Start the broker:
openbrowser-broker
git clone https://github.com/floomhq/openbrowser.git
cd openbrowser
OPENBROWSER_API_KEYS="$(openssl rand -base64 48)" docker compose up --build
Lease a browser:
curl -fsS http://127.0.0.1:8767/lease \
-H "content-type: application/json" \
-d '{"owner":"demo","ttl_seconds":300}'
Use the returned lease_id:
curl -fsS http://127.0.0.1:8767/browser/navigate \
-H "content-type: application/json" \
-d '{"lease_id":"<lease_id>","url":"https://example.com"}'
curl -fsS http://127.0.0.1:8767/browser/snapshot \
-H "content-type: application/json" \
-d '{"lease_id":"<lease_id>"}'
curl -fsS -X POST http://127.0.0.1:8767/release/<lease_id>
Expose the broker behind your HTTPS proxy or tunnel and configure:
OPENBROWSER_API_KEYS="your-long-random-api-key"
OPENBROWSER_PUBLIC_OPENBROWSER_BASE_URL="https://browser.example.com/openbrowser/v1"
Then call:
BASE=https://browser.example.com/openbrowser/v1
KEY=your-long-random-api-key
curl -fsS "$BASE/docs" \
-H "authorization: Bearer $KEY" \
-H "user-agent: openbrowser-client/1.0"
The API covers leases, navigation, snapshots, screenshots, clicks, typing, keyboard events, tabs, auth handoff, Take Over Tab, profiles, feedback issues, telemetry, and audits.
flowchart TD
RemoteAgent["Remote agent"] -->|Bearer token| API["/openbrowser/v1"]
API --> Lease["POST /leases"]
API --> Browser["POST /browser/*"]
API --> Auth["POST /auth/request"]
API --> Issues["POST /feedback/issues"]
API --> Audit["GET /audit"]
Local MCP, for agents running on the broker host:
{
"mcpServers": {
"openbrowser-broker": {
"command": "openbrowser-mcp"
}
}
}
Remote MCP, for agents running anywhere:
{
"mcpServers": {
"openbrowser-remote": {
"command": "openbrowser-remote-mcp",
"env": {
"OPENBROWSER_API_KEY": "<OPENBROWSER_API_KEY>",
"OPENBROWSER_BASE_URL": "https://browser.example.com/openbrowser/v1"
}
}
}
}
Core MCP tools:
browser_lease, browser_release, browser_heartbeatbrowser_navigate, browser_snapshot, browser_screenshotbrowser_click, browser_type, browser_keyboard_type, browser_keyboard_pressbrowser_tabs, browser_new_tab, browser_switch_tab, browser_waitauth_request, auth_status, takeover_request (lease_control_request remains as a compatibility alias)feedback_report_issue, feedback_list_issues, feedback_update_issuetelemetry_record_event, telemetry_list_events, telemetry_summarybroker_audit, broker_docs, profile_statusIdentities are configured in config/identities.local.json:
{
"identities": {
"work-main": {
"label": "Work account",
"site": "example.com",
"slot": "auto",
"profile_dir": "/var/lib/openbrowser-broker/profiles/work-main",
"proxy_ref": "residential:work-main",
"timezone": "America/New_York",
"lang": "en-US",
"policy": {
"max_parallel_sessions": 1,
"requires_human_auth": true
}
}
}
}
When an identity needs login:
curl -fsS "$BASE/auth/request" \
-H "authorization: Bearer $KEY" \
-H "content-type: application/json" \
-d '{"owner":"setup","identity_id":"work-main","url":"https://example.com/login","reason":"initial_login"}'
Open the returned portal_url, complete login in the browser view, then mark the request complete. Future leases for that identity reuse the saved profile state.
Take Over Tab links under /auth/lease-control/<token> are for non-credential current-tab control only. Login, password, passkey, 2FA, SSO, and provider-auth handoffs use /auth/<token> from auth_request; takeover and legacy lease-control requests refuse auth-sensitive current tabs.
For parallel work, set policy.max_parallel_sessions above 1. OpenBrowser then seeds per-slot replicas instead of starting multiple Chrome processes against one profile directory. That matters: several windows in a desktop Chrome profile are one Chrome process, but several server-side agents are independent Chrome processes. Directly sharing the same profile_dir across those processes risks Chrome singleton-lock failures and profile database corruption.
flowchart LR
Identity["identity_id=work-main"] --> Profile["Chrome profile dir"]
Identity --> Policy["parallel-session policy"]
Identity --> ProxyRef["optional proxy_ref"]
ProxyRef --> Forwarder["local proxy forwarder"]
Profile --> Chrome["leased Chrome slot"]
Forwarder --> Chrome
Add proxy credentials in secrets/proxies.json:
{
"proxies": {
"residential:work-main": {
"scheme": "http",
"host": "proxy.example.net",
"port": 12345,
"username": "user",
"password": "pass"
}
}
}
Then set "proxy_ref": "residential:work-main" on the identity. The broker starts a local proxy forwarder and launches Chrome with the matching proxy for that profile.
openbrowser-audit --json
openbrowser-use --json open https://example.com
openbrowser status
openbrowser docs quickstart
Systemd examples live in systemd/. Detailed runbooks live in docs/.
python3 -m compileall ax_browser_broker tests
pytest -q
OpenBrowser is an alpha public release of production-oriented browser infrastructure. The core lease manager, profile identities, remote API, MCP surfaces, human auth handoff, telemetry, feedback issues, audits, and adapter wrappers are covered by tests. New deployments can use the generic commands and environment variables above; legacy ax-* command wrappers remain for existing installations.
MIT
Open-source browser automation broker for AI agents: persistent Chrome profiles, proxy-aware identities, remote API, MCP tools, browser-use/OpenBrowser adapters, human auth handoff, telemetry, and aud
Genel bakış
Open-source browser automation broker for AI agents: persistent Chrome profiles, proxy-aware identities, remote API, MCP tools, browser-use/OpenBrowser adapters, human auth handoff, telemetry, and audits.
Araçlar
Henüz araç listesi yok. Uzak sunucular ilk sağlık kontrolünden sonra bir liste alır.
SSS
Bu sayfadan Cursor, Claude Desktop, Claude Code veya VS Code için stdio yapılandırmasını kopyalayın. PlugMCP proxy'sini değil, yayıncının kurulumunu kullanır.
Bu kayıtta gerekli bir ortam değişkeni listelenmiyor.
Openbrowser yerel olarak stdio üzerinden çalışır.
Son kontrol: 2026-10-28. Open-source browser automation broker for AI agents: persistent Chrome profiles, proxy-aware identities, remote API, MCP tools, browser-use/OpenBrowser adapters, human auth handoff, telemetry, and audits.