Browserstack

Connects Claude to BrowserStack for running cross-browser tests without maintaining your own device lab. You'd reach for this when you need to verify your web app works across different browsers, OS versions, and real mobile devices. The integration lets Claude spin up test sessions, grab screenshots, and collect logs programmatically. It's overkill if you're just testing Chrome locally, but becomes essential once you need to confirm that Safari bug or check Android compatibility. The API access means you can automate the whole flow instead of clicking through their web interface.

skills.sh installs: 1.6K
GitHub stars: 29.5K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add alirezarezvani/claude-skills --skill browserstack --agent claude-code

Installs into .claude/skills of the current project.

Files

BrowserStack Integration

Run Playwright tests on BrowserStack's cloud grid for cross-browser and cross-device testing.

Prerequisites

Environment variables must be set:

BROWSERSTACK_USERNAME — your BrowserStack username
BROWSERSTACK_ACCESS_KEY — your access key

If not set, inform the user how to get them from browserstack.com/accounts/settings and stop.

The BrowserStack MCP server is not auto-registered (issue #978). pw-browserstack was removed from the plugin's .mcp.json because it failed to connect for every user (the plugin ships no node_modules). The browserstack_* MCP tools used below, and the /pw:browserstack command, will fail with "tool not found" until it is enabled manually — see the Integrations section of the plugin's CLAUDE.md (cd integrations/browserstack-mcp && npm install, then register the server in your own user/project MCP config). Setting the env vars alone is not sufficient.