Browserbase · Codex
Add the Browserbase MCP server to Codex
Cloud browser automation with Browserbase and Stagehand.
Official serverLocalBrowser automation
1. Add the server
Run in your terminal
# ~/.codex/config.toml [mcp_servers.browserbase] command = "npx" args = ["-y", "@browserbasehq/mcp-server-browserbase"] [mcp_servers.browserbase.env] BROWSERBASE_API_KEY = "<your BROWSERBASE_API_KEY>" BROWSERBASE_PROJECT_ID = "<your BROWSERBASE_PROJECT_ID>" GEMINI_API_KEY = "<your GEMINI_API_KEY>"
2. Sign in
Run codex mcp login <name> to complete OAuth for a remote server. Browserbase runs locally and needs BROWSERBASE_API_KEY, BROWSERBASE_PROJECT_ID, GEMINI_API_KEY. Replace the placeholder values above with your own before starting Codex.
3. Try it
Ask Codex for something Browserbase can do. Cloud browser automation with Browserbase and Stagehand. Approve the first tool call and check the result before allowing write actions automatically.
- · Each server is a [mcp_servers.<name>] table in config.toml.
- · Use enabled_tools or disabled_tools to keep the tool list short.
FAQ
- How do I add the Browserbase MCP server to Codex?
- Run: # ~/.codex/config.toml …. Run codex mcp login <name> to complete OAuth for a remote server.
- Is this the official Browserbase MCP server?
- Yes. It is published by Browserbase as io.github.browserbase/mcp-server-browserbase in the official MCP registry.
- Does the Browserbase MCP server need an API key?
- Yes. It runs locally and requires BROWSERBASE_API_KEY, BROWSERBASE_PROJECT_ID, GEMINI_API_KEY.
Links
Browserbase in other clients
More browser automation for Codex
Work at Browserbase?
Feature Browserbase across the directory and its category from $49/month.
Reviewed Oct 5, 2026. Command generated from the registry record and checked against Codex's documented syntax.