Browserbasehq Mcp Browserbase

ai.smithery由 smithery.ai 發布官方發布者v2.2.0更新於 Oct 24, 2026

Provides cloud browser automation capabilities using Stagehand and Browserbase, enabling LLMs to i…

發布方自己的服務:222wcnm Bilistalkermcp

已驗證Streamable HTTP可網頁執行網頁搜尋與抓取瀏覽器自動化

概覽

AI 產生的概覽

以 Browserbase 與 Stagehand 為基礎的雲端瀏覽器自動化伺服器,讓助理開啟工作階段、瀏覽頁面、執行動作、觀察元素並擷取資料。

可以做什麼
  • 建立或重複使用 Browserbase 雲端瀏覽器工作階段,並在結束時關閉
  • 將瀏覽器導覽至指定網址
  • 在頁面上執行動作,並觀察可互動的元素
  • 依指示從目前頁面擷取資料
適用情境
適合需要助理操作真實雲端瀏覽器的情境,例如填寫表單、點擊瀏覽網站,或從一般 HTTP 擷取無法處理的頁面取得結構化資訊。README 指出此儲存庫已封存,建議改用 Browserbase 託管版本。
執行需求
遠端端點位於 server.smithery.ai,需在 Authorization 標頭提供 bearer 權杖。自架版本需要 Node.js(npx @browserbasehq/mcp)或 Docker,並設定 BROWSERBASE_API_KEY、BROWSERBASE_PROJECT_ID,預設 Stagehand 模型另需 GEMINI_API_KEY;使用自訂模型需提供 --modelApiKey。
安裝前請注意
README 明確說明儲存庫已封存且不再維護,建議優先使用託管版本。自架需要 Browserbase API 金鑰與專案 ID,非預設模型還需模型供應商金鑰。助理可對實際網頁執行動作,可能送出表單或改變遠端狀態,頁面內容會交由 Browserbase 與所選模型供應商處理。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Browserbasehq Mcp Browserbase,將其新增到工作區。
  2. 連接 Authorization token 憑證。它們會被私密儲存,絕不會在公開頁面上展示。
  3. 為需要使用其工具的對話啟用該服務。

Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/ai.smithery%2Fbrowserbasehq-mcp-browserbase/install.md,並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前,先告訴我它的發布者、端點和登入方式,等我確認。不要把 API 金鑰寫進命令或我會提交的檔案;問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

{
  "mcpServers": {
    "browserbasehq-browserbase": {
      "type": "http",
      "url": "https://server.smithery.ai/@browserbasehq/mcp-browserbase/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

Browserbase MCP Server

Archived

This repository is archived and no longer maintained.

It was originally published as a reference implementation and is retained for historical purposes. It should not be interpreted as representative of Browserbase's current production services or implementation.

[cover]

The Model Context Protocol (MCP) is an open protocol that enables seamless integration between LLM applications and external data sources and tools. Whether you're building an AI-powered IDE, enhancing a chat interface, or creating custom AI workflows, MCP provides a standardized way to connect LLMs with the context they need.

This server provides cloud browser automation capabilities using Browserbase and Stagehand. It enables LLMs to interact with web pages, extract information, and perform automated actions.

This is a self-hostable version of the Browserbase hosted MCP server with the same tools and functionality. We recommend using the hosted version for the easiest setup.

Tools

This server exposes 6 tools that match the hosted Browserbase MCP server:

ToolDescriptionInput
startCreate or reuse a Browserbase session(none)
endClose the current Browserbase session(none)
navigateNavigate to a URL{ url: string }
actPerform an action on the page{ action: string }
observeObserve actionable elements on the page{ instruction: string }
extractExtract data from the page{ instruction?: string }

How to Setup

We currently support 2 transports for our MCP server, STDIO and SHTTP. We recommend you use SHTTP with our hosted MCP server to take advantage of the server at full capacity.

SHTTP (Hosted MCP):

Use the Browserbase hosted MCP server at https://mcp.browserbase.com/mcp. This is the easiest way to get started -- we host the server and provide the LLM costs for Gemini, the best performing model in Stagehand.

For full setup instructions, see the Browserbase MCP documentation.

If your client supports SHTTP:

json
{  "mcpServers": {    "browserbase": {      "type": "http",      "url": "https://mcp.browserbase.com/mcp"    }  }}

If your client doesn't support SHTTP:

json
{  "mcpServers": {    "browserbase": {      "command": "npx",      "args": ["mcp-remote", "https://mcp.browserbase.com/mcp"]    }  }}

STDIO (Self-Hosted):

You can either use our server hosted on NPM or run it completely locally by cloning this repo.

Note: If you want to use a different model you have to add --modelName to the args and provide that respective key as an arg. More info below.

To run via NPM (Recommended)

Go into your MCP Config JSON and add the Browserbase Server:

json
{  "mcpServers": {    "browserbase": {      "command": "npx",      "args": ["@browserbasehq/mcp"],      "env": {        "BROWSERBASE_API_KEY": "",        "BROWSERBASE_PROJECT_ID": "",        "GEMINI_API_KEY": ""      }    }  }}

That's it! Reload your MCP client and you're ready to go.

To run 100% local:

Option 1: Direct installation
bash
git clone https://github.com/browserbase/mcp-server-browserbase.gitcd mcp-server-browserbasenpm install && npm run build
Option 2: Docker
bash
git clone https://github.com/browserbase/mcp-server-browserbase.gitcd mcp-server-browserbasedocker build -t mcp-browserbase .

Then in your MCP Config JSON run the server:

Using Direct Installation
json
{  "mcpServers": {    "browserbase": {      "command": "node",      "args": ["/path/to/mcp-server-browserbase/cli.js"],      "env": {        "BROWSERBASE_API_KEY": "",        "BROWSERBASE_PROJECT_ID": "",        "GEMINI_API_KEY": ""      }    }  }}
Using Docker
json
{  "mcpServers": {    "browserbase": {      "command": "docker",      "args": [        "run",        "--rm",        "-i",        "-e",        "BROWSERBASE_API_KEY",        "-e",        "BROWSERBASE_PROJECT_ID",        "-e",        "GEMINI_API_KEY",        "mcp-browserbase"      ],      "env": {        "BROWSERBASE_API_KEY": "",        "BROWSERBASE_PROJECT_ID": "",        "GEMINI_API_KEY": ""      }    }  }}

Configuration

The Browserbase MCP server accepts the following command-line flags:

FlagDescription
--proxiesEnable Browserbase proxies for the session
--verifiedEnable Browserbase Verified Identity (Only for Scale Plan Users)
--advancedStealthDeprecated alias for --verified
--keepAliveEnable Browserbase Keep Alive Session
--contextId <contextId>Specify a Browserbase Context ID to use
--persistWhether to persist the Browserbase context (default: true)
--port <port>Port to listen on for HTTP/SHTTP transport
--host <host>Host to bind server to (default: localhost, use 0.0.0.0 for all interfaces)
--browserWidth <width>Browser viewport width (default: 1024)
--browserHeight <height>Browser viewport height (default: 768)
--modelName <model>The model to use for Stagehand (default: google/gemini-2.5-flash-lite)
--modelApiKey <key>API key for the custom model provider (required when using custom models)
--experimentalEnable experimental features (default: false)

These flags can be passed directly to the CLI or configured in your MCP configuration file.

Note: These flags can only be used with the self-hosted server (npx @browserbasehq/mcp or Docker).

Model Configuration

Stagehand defaults to using Google's Gemini 2.5 Flash Lite model, but you can configure it to use other models like GPT-4o, Claude, or other providers.

Important: When using any custom model (non-default), you must provide your own API key for that model provider using the --modelApiKey flag.

json
{  "mcpServers": {    "browserbase": {      "command": "npx",      "args": [        "@browserbasehq/mcp",        "--modelName",        "anthropic/claude-sonnet-4.5",        "--modelApiKey",        "your-anthropic-api-key"      ],      "env": {        "BROWSERBASE_API_KEY": "",        "BROWSERBASE_PROJECT_ID": ""      }    }  }}

Note: The model must be supported in Stagehand. Check out the docs here.

Links

License

Licensed under the Apache 2.0 License.

Copyright 2025 Browserbase, Inc.

來源:README.md,提交 3e6f534

工具

0
SourceWeft 尚未讀取此伺服器的工具。

版本歷史

1
  1. v2.2.0最新Sep 16, 2026

評分

已滿足適用檢查項的 85%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具必需15 分

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分

其他 Smithery 整合