Skip to content

BrowserStack MCP Server

Full BrowserStack Test Platform access for cross-browser testing. Run tests across real devices and browsers.

Capabilities
Cross-Browser Testing Real Devices Automation Screenshots
Maintained by
BrowserStack
Hosting
Runs locally on your machine
Authentication
API key or credentials (environment variables)
Last checked

BrowserStack also runs a hosted version at mcp.browserstack.com with OAuth sign-in.

How to connect the BrowserStack MCP server

Pick your AI client and paste the snippet. Swap the YOUR_… placeholders for your own values. New to this? Our guide to how MCP clients and servers fit together explains what each piece does.

Claude Code

Terminal
claude mcp add --env BROWSERSTACK_USERNAME=YOUR_USERNAME --env BROWSERSTACK_ACCESS_KEY=YOUR_ACCESS_KEY --transport stdio browserstack \
  -- npx -y @browserstack/mcp-server@latest
Full Claude Code setup guide →

Claude Desktop

claude_desktop_config.json (Settings → Developer → Edit Config)
{
  "mcpServers": {
    "browserstack": {
      "command": "npx",
      "args": [
        "-y",
        "@browserstack/mcp-server@latest"
      ],
      "env": {
        "BROWSERSTACK_USERNAME": "YOUR_USERNAME",
        "BROWSERSTACK_ACCESS_KEY": "YOUR_ACCESS_KEY"
      }
    }
  }
}

Fully quit and reopen Claude Desktop after saving.

Full Claude Desktop setup guide →

Cursor

~/.cursor/mcp.json (or .cursor/mcp.json in a project)
{
  "mcpServers": {
    "browserstack": {
      "command": "npx",
      "args": [
        "-y",
        "@browserstack/mcp-server@latest"
      ],
      "env": {
        "BROWSERSTACK_USERNAME": "YOUR_USERNAME",
        "BROWSERSTACK_ACCESS_KEY": "YOUR_ACCESS_KEY"
      }
    }
  }
}
Full Cursor setup guide →

VS Code

.vscode/mcp.json
{
  "servers": {
    "browserstack": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@browserstack/mcp-server@latest"
      ],
      "env": {
        "BROWSERSTACK_USERNAME": "YOUR_USERNAME",
        "BROWSERSTACK_ACCESS_KEY": "YOUR_ACCESS_KEY"
      }
    }
  }
}
Full VS Code setup guide →

Frequently asked questions

What is the BrowserStack MCP server?

It is a Model Context Protocol (MCP) server — a small piece of software that gives AI assistants like Claude a secure, governed connection to BrowserStack. Full BrowserStack Test Platform access for cross-browser testing. Run tests across real devices and browsers.

Is there an official BrowserStack MCP server?

Yes. The BrowserStack MCP server is an official integration, maintained by the vendor or the Model Context Protocol project, which makes it the safest default for business use. It is maintained by BrowserStack.

Is the BrowserStack MCP server hosted, or do I run it myself?

It runs locally. Your AI client starts it on your own machine with npx, and it talks to the client over standard input and output rather than the network.

Do I need an API key for the BrowserStack MCP server?

Yes. The local server reads BROWSERSTACK_USERNAME, BROWSERSTACK_ACCESS_KEY from its environment, so you create those credentials first and add them to your client's config.

What can an AI assistant actually do with BrowserStack?

Through this server an assistant can work with cross-browser testing, real devices, automation, screenshots — reading from and acting on BrowserStack directly instead of you copy-pasting between windows. What you allow it to do is controlled by the permissions you grant.

How do I set this up for my business?

The setup section above has copy-paste config for Claude Code, Claude Desktop, Cursor and VS Code. If you want it rolled out across a team with permissions, governance and support handled, that is what Crox's Build engagement covers.

New to MCP? Start with our plain-English guide to the Model Context Protocol or see how to connect AI to your business tools without writing code .

Done-for-you integration

Want this connected to your business — with governance handled?

Crox maps your processes, connects AI to the tools you already use, and keeps it working as models change. Start with a readiness assessment or talk to us about a build.