Add the BrowserStack MCP server to Codex

# ~/.codex/config.toml
[mcp_servers.browserstack]
command = "npx"
args = ["-y", "@browserstack/mcp-server"]

[mcp_servers.browserstack.env]
BROWSERSTACK_USERNAME = "<your BROWSERSTACK_USERNAME>"
BROWSERSTACK_ACCESS_KEY = "<your BROWSERSTACK_ACCESS_KEY>"

Scopes, env vars, OAuth and limits: Codex MCP config guide

Run codex mcp login <name> to complete OAuth for a remote server. BrowserStack runs locally and needs BROWSERSTACK_USERNAME, BROWSERSTACK_ACCESS_KEY. Replace the placeholder values above with your own before starting Codex.

Ask Codex for something BrowserStack can do. Run Playwright and Selenium tests on real devices and browsers, debug failures, scan for accessibility issues and manage test cases. 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.

How do I add the BrowserStack MCP server to Codex?

Run: # ~/.codex/config.toml …. Run codex mcp login <name> to complete OAuth for a remote server.

Is this the official BrowserStack MCP server?

Yes. It is published by BrowserStack as io.github.browserstack/mcp-server in the official MCP registry.

Does the BrowserStack MCP server need an API key?

Yes. It runs locally and requires BROWSERSTACK_USERNAME, BROWSERSTACK_ACCESS_KEY.