@@ -99,6 +99,8 @@ That's it! Reload your MCP client and Claude will be able to use Browserbase.
9999
100100### To run 100% local:
101101
102+ #### Option 1: Direct installation
103+
102104``` bash
103105# Clone the Repo
104106git clone https://github.com/browserbase/mcp-server-browserbase.git
@@ -108,10 +110,23 @@ cd mcp-server-browserbase
108110npm install && npm run build
109111```
110112
113+ #### Option 2: Docker
114+
115+ ``` bash
116+ # Clone the Repo
117+ git clone https://github.com/browserbase/mcp-server-browserbase.git
118+ cd mcp-server-browserbase
119+
120+ # Build the Docker image
121+ docker build -t mcp-browserbase .
122+ ```
123+
111124Then in your MCP Config JSON run the server. To run locally we can use STDIO or self-host SHTTP.
112125
113126### STDIO:
114127
128+ #### Using Direct Installation
129+
115130To your MCP Config JSON file add the following:
116131
117132``` json
@@ -130,6 +145,37 @@ To your MCP Config JSON file add the following:
130145}
131146```
132147
148+ #### Using Docker
149+
150+ To your MCP Config JSON file add the following:
151+
152+ ``` json
153+ {
154+ "mcpServers" : {
155+ "browserbase" : {
156+ "command" : " docker" ,
157+ "args" : [
158+ " run" ,
159+ " --rm" ,
160+ " -i" ,
161+ " -e" ,
162+ " BROWSERBASE_API_KEY" ,
163+ " -e" ,
164+ " BROWSERBASE_PROJECT_ID" ,
165+ " -e" ,
166+ " GEMINI_API_KEY" ,
167+ " mcp-browserbase"
168+ ],
169+ "env" : {
170+ "BROWSERBASE_API_KEY" : " " ,
171+ "BROWSERBASE_PROJECT_ID" : " " ,
172+ "GEMINI_API_KEY" : " "
173+ }
174+ }
175+ }
176+ }
177+ ```
178+
133179Then reload your MCP client and you should be good to go!
134180
135181## Configuration
@@ -156,7 +202,49 @@ These flags can be passed directly to the CLI or configured in your MCP configur
156202
157203### NOTE:
158204
159- Currently, these flags can only be used with the local server (npx @browserbasehq/mcp-server-browserbase ).
205+ Currently, these flags can only be used with the local server (npx @browserbasehq/mcp-server-browserbase or Docker).
206+
207+ ### Using Configuration Flags with Docker
208+
209+ When using Docker, you can pass configuration flags as additional arguments after the image name. Here's an example with the ` --proxies ` flag:
210+
211+ ``` json
212+ {
213+ "mcpServers" : {
214+ "browserbase" : {
215+ "command" : " docker" ,
216+ "args" : [
217+ " run" ,
218+ " --rm" ,
219+ " -i" ,
220+ " -e" ,
221+ " BROWSERBASE_API_KEY" ,
222+ " -e" ,
223+ " BROWSERBASE_PROJECT_ID" ,
224+ " -e" ,
225+ " GEMINI_API_KEY" ,
226+ " mcp-browserbase" ,
227+ " --proxies"
228+ ],
229+ "env" : {
230+ "BROWSERBASE_API_KEY" : " " ,
231+ "BROWSERBASE_PROJECT_ID" : " " ,
232+ "GEMINI_API_KEY" : " "
233+ }
234+ }
235+ }
236+ }
237+ ```
238+
239+ You can also run the Docker container directly from the command line:
240+
241+ ``` bash
242+ docker run --rm -i \
243+ -e BROWSERBASE_API_KEY=your_api_key \
244+ -e BROWSERBASE_PROJECT_ID=your_project_id \
245+ -e GEMINI_API_KEY=your_gemini_key \
246+ mcp-browserbase --proxies
247+ ```
160248
161249## Configuration Examples
162250
0 commit comments