AI 클라이언트가 일상적인 영어 프롬프트를 통해 BrowserStack 수동 및 자동 테스트를 관리 및 실행하고, 실패 원인을 디버깅하며, 접근성 스캔을 수행할 수 있도록 지원합니다.
다른 이름 browserstack/mcp-server, @browserstack/mcp-server
- 스타
- 153
- Tools
- —
- 다운로드, 30일
- 114,405
- 최신 버전
- 2.6.8
- 마지막 커밋
- 2026년 11월 13일
- 라이선스
- AGPL-3.0
BrowserStack MCP란?
BrowserStack은(는) MCP server입니다. AI 클라이언트가 일상적인 영어 프롬프트를 통해 BrowserStack 수동 및 자동 테스트를 관리 및 실행하고, 실패 원인을 디버깅하며, 접근성 스캔을 수행할 수 있도록 지원합니다.
프로젝트 README에서 생성된 요약
BrowserStack MCP server 정보
이 서버는 Cursor, Claude, VS Code와 같은 AI 기반 클라이언트를 사용하는 개발자가 자연어를 통해 소프트웨어 테스트를 관리하고 실행할 수 있게 해줍니다. BrowserStack Test Platform에 연결함으로써 사용자는 기본 개발 환경을 벗어나지 않고도 수동 또는 자동 테스트를 트리거하고, 접근성 스캔을 수행하며, 테스트 계획을 관리할 수 있습니다. 이 서버는 Playwright, Selenium, Jest를 포함한 다양한 테스트 프레임워크를 지원하며, k6 또는 JMeter와 같은 도구를 사용한 부하 테스트 기능도 제공합니다.
이 서버를 사용하려면 username과 access key가 포함된 BrowserStack 계정이 필요합니다. 로컬에 설정하거나 mcp.browserstack.com을 통해 원격 stateless HTTP 연결로 설정할 수 있습니다. 연결되면 AI 어시스턴트는 핵심 도구를 사용하여 워크플로 카탈로그를 검색하며, Android 14 크래시 디버깅이나 특정 버전의 Chrome에서 웹사이트 실행과 같은 특정 작업을 요청할 수 있습니다. 시스템은 실패한 자동화 테스트에 대한 코드 수정안을 제안할 수도 있지만, 파일에 변경 사항을 적용하기 전에는 반드시 사용자의 명시적인 승인을 거쳐야 합니다.
활용 사례
- 1모바일 애플리케이션 오류 디버깅특정 모바일 운영 체제에서 애플리케이션이 왜 크래시되었는지 AI에게 조사하도록 요청합니다.
- 2자동화 테스트 스위트 실행AI 어시스턴트에게 BrowserStack 인프라에서 기존 자동화 테스트를 실행하도록 명령합니다.
- 3접근성 준수 스캔 수행자동화 스캔을 사용하여 로컬 또는 운영 중인 웹사이트의 접근성 문제를 식별하고 수정합니다.
- 4테스트 조직 관리자연어를 사용하여 관리 시스템 내에서 프로젝트, 폴더 및 특정 테스트 케이스를 생성합니다.
- 5부하 테스트 성능 분석최근 부하 테스트 실행 결과에 대한 상세 지표 및 비교 분석을 요청합니다.
프로젝트의 README를 바탕으로 작성되었습니다. 모든 활용 사례는 해당 내용의 인용문과 대조하여 확인합니다.
BrowserStack MCP 설치 방법
형식 확인: 2026년 11월 10일Cursor에 추가Goose에 추가Claude Code에 BrowserStack MCP 설치
$ claude mcp add --env 'BROWSERSTACK_ACCESS_KEY=<YOUR_BROWSERSTACK_ACCESS_KEY>' --env 'BROWSERSTACK_USERNAME=<BROWSERSTACK_USERNAME>' mcp-server -- npx -y @browserstack/mcp-serverCursor에 BrowserStack MCP 설치
~/.cursor/mcp.json
{
"mcpServers": {
"mcp-server": {
"command": "npx",
"args": [
"-y",
"@browserstack/mcp-server"
],
"env": {
"BROWSERSTACK_ACCESS_KEY": "<YOUR_BROWSERSTACK_ACCESS_KEY>",
"BROWSERSTACK_USERNAME": "<BROWSERSTACK_USERNAME>"
}
}
}
}VS Code에 BrowserStack MCP 설치
.vscode/mcp.json
{
"servers": {
"mcp-server": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@browserstack/mcp-server"
],
"env": {
"BROWSERSTACK_ACCESS_KEY": "<YOUR_BROWSERSTACK_ACCESS_KEY>",
"BROWSERSTACK_USERNAME": "<BROWSERSTACK_USERNAME>"
}
}
}
}VS Code CLI에 BrowserStack MCP 설치
$ code --add-mcp '{"name":"mcp-server","type":"stdio","command":"npx","args":["-y","@browserstack/mcp-server"],"env":{"BROWSERSTACK_ACCESS_KEY":"<YOUR_BROWSERSTACK_ACCESS_KEY>","BROWSERSTACK_USERNAME":"<BROWSERSTACK_USERNAME>"}}'Claude Desktop에 BrowserStack MCP 설치
claude_desktop_config.json
{
"mcpServers": {
"mcp-server": {
"command": "npx",
"args": [
"-y",
"@browserstack/mcp-server"
],
"env": {
"BROWSERSTACK_ACCESS_KEY": "<YOUR_BROWSERSTACK_ACCESS_KEY>",
"BROWSERSTACK_USERNAME": "<BROWSERSTACK_USERNAME>"
}
}
}
}Codex에 BrowserStack MCP 설치
$ codex mcp add mcp-server --env 'BROWSERSTACK_ACCESS_KEY=<YOUR_BROWSERSTACK_ACCESS_KEY>' --env 'BROWSERSTACK_USERNAME=<BROWSERSTACK_USERNAME>' -- npx -y @browserstack/mcp-serverCodex config.toml에 BrowserStack MCP 설치
~/.codex/config.toml
[mcp_servers.mcp-server] command = "npx" args = ["-y", "@browserstack/mcp-server"] [mcp_servers.mcp-server.env] BROWSERSTACK_ACCESS_KEY = "<YOUR_BROWSERSTACK_ACCESS_KEY>" BROWSERSTACK_USERNAME = "<BROWSERSTACK_USERNAME>"
Gemini CLI에 BrowserStack MCP 설치
$ gemini mcp add -s user -e 'BROWSERSTACK_ACCESS_KEY=<YOUR_BROWSERSTACK_ACCESS_KEY>' -e 'BROWSERSTACK_USERNAME=<BROWSERSTACK_USERNAME>' mcp-server npx -- -y @browserstack/mcp-serverGemini settings.json에 BrowserStack MCP 설치
~/.gemini/settings.json
{
"mcpServers": {
"mcp-server": {
"command": "npx",
"args": [
"-y",
"@browserstack/mcp-server"
],
"env": {
"BROWSERSTACK_ACCESS_KEY": "<YOUR_BROWSERSTACK_ACCESS_KEY>",
"BROWSERSTACK_USERNAME": "<BROWSERSTACK_USERNAME>"
}
}
}
}구성
BROWSERSTACK_ACCESS_KEY필수비밀BrowserStack Access Key
BROWSERSTACK_USERNAME필수BrowserStack Username
| 이름 | 설명 | 유형 |
|---|---|---|
| BROWSERSTACK_ACCESS_KEY | BrowserStack Access Key | 필수비밀 |
| BROWSERSTACK_USERNAME | BrowserStack Username | 필수 |
자동 검사
2026년 11월 12일에 실행됨전체 보고서 →자동 검사를 통과했습니다. 이는 보안 감사가 아닙니다. 코드를 직접 읽고 서버에 필요한 최소한의 권한만 부여하십시오. 검사 방식
- 소스 저장소 연결 및 접근 가능통과
- 오픈 소스 라이선스 (OSI)통과
- 최근 1년 내 커밋 또는 릴리스통과
- 패키지 이름이 인기 패키지와 유사하지 않음통과
- 원격 엔드포인트가 HTTPS 사용통과
- 파괴적인 도구에 라벨 표시됨검사되지 않음
- 모델에 대한 숨겨진 지침 없음통과
- 패키지 및 해당 종속성에 중요한 보안 권고 없음통과
README
GitHub에서 보기BrowserStack MCP Server
Manage test cases, execute manual or automated tests, debug issues, and even fix code—directly within tools like Cursor, Claude, or any MCP-enabled client, using plain English.
Test from anywhere:
Easily connect the BrowserStack Test Platform to your favourite AI tools, such as IDEs, LLMs, or agentic workflows.
Test with natural language:
Manage, execute, debug tests, and even fix code using plain English prompts.
Reduced context switching:
Stay in flow—keep all project context in one place and trigger actions directly from your IDE or LLM.
⚡️ One Click MCP Setup
Click on the buttons below to install MCP in your respective IDE or assistant:
Note: The hosted Remote MCP server (
mcp.browserstack.com) is now fully stateless over Streamable HTTP — any Streamable-HTTP client (Claude, Cursor, VS Code, ChatGPT) connects with no configuration change.
Kiro: a Kiro power for this server lives in
integrations/kiro-power. In the Kiro IDE, open the Powers panel → Add Custom Power → Import power from GitHub and enterhttps://github.com/browserstack/mcp-server/tree/main/integrations/kiro-power, or clone this repository and use Import power from a folder with that directory.
Prerequisites
- A BrowserStack account. Sign up if you don't have one; open-source projects can get a free plan.
- Your
usernameandaccess_keyfrom Account Settings.
For manual setup in any MCP client, see Install the MCP server locally or Set up the remote MCP server.
Note : Ensure you are using Node version >= 22
- Check your node version using
node --version. Recommended version:v22.15.0(LTS) - To Upgrade Node :
-
- On macOS
(Homebrew) - brew update && brew upgrade node or if using (nvm) - nvm install 22.15.0 && nvm use 22.15.0 && nvm alias default 22.15.0
- On macOS
-
- On Windows
(nvm-windows) : nvm install 22.15.0 && nvm use 22.15.0
- On Windows
- 👉 Or directly download the Node.js LTS Installer
🪄 Agent-assisted setup
Most AI agents can add the BrowserStack MCP server, connect to it, and walk you through sign-in without manual config. Paste this prompt into your agent:
Add the BrowserStack MCP server to this agent, following the setup guide at
https://www.browserstack.com/docs/browserstack-mcp-server/get-started/remote-mcp-server
and using the server URL https://mcp.browserstack.com/mcp. Once it is added, start the
BrowserStack sign-in flow so I can log in.
To add it yourself, use your client's command or menu:
| Client | Command or configuration |
|---|---|
| Claude Code | claude mcp add --scope user --transport http browserstack https://mcp.browserstack.com/mcp, then run /mcp in a session and sign in |
| Claude Desktop / claude.ai | Settings → Connectors → Add custom connector, with the URL https://mcp.browserstack.com/mcp |
| ChatGPT | Install the BrowserStack plugin |
| Codex | codex mcp add browserstack --url https://mcp.browserstack.com/mcp, then codex mcp login browserstack to sign in |
| VS Code / GitHub Copilot | code --add-mcp '{"name":"browserstack","type":"http","url":"https://mcp.browserstack.com/mcp"}', then start the server from the MCP view and sign in |
| Cursor | Add "browserstack": { "url": "https://mcp.browserstack.com/mcp" } under mcpServers in ~/.cursor/mcp.json, then sign in from Cursor Settings → MCP |
| Any other MCP client | Point it at https://mcp.browserstack.com/mcp |
💡 Usage Examples
📱 Manual App Testing
Test mobile apps on real devices across the latest OS versions. Reproduce bugs and debug crashes without setup hassles. Below are some sample prompts to use your mobile apps on BrowserStack's extensive cloud of real devices
# Open app on specific device
"open my app on a iPhone 15 Pro Max"
# Debug app crashes
"My app crashed on Android 14 device, can you help me debug?"
- Unlike emulators, test your app's real-world performance on actual devices. With advanced App-Profiling features, you can debug crashes and performance issues in real-time.
- Access all major devices and OS versions from our device grid, We have strict SLAs to provision our global datacenters with newly released devices on launch day.
🌐 Manual Web Testing
Similar to the app testing, you can use the following prompts to test your websites on BrowserStack's extensive cloud of real browsers and devices. Don't have Edge browser installed on your machine ? We've got you covered!
# Test your websites
"open my website hosted on localhost:3001 on Edge"
"open browserstack.com on latest version of Chrome"
- Test websites across different browsers and devices. We support every major browser across every major OS.
- Seamlessly test websites hosted locally on your machine, no need to deploy to a remote server!
🧪 Automated Testing (Playwright, Selenium, A11y and more..)
Auto-analyze, diagnose, and even fix broken test scripts right in your IDE or LLM. Instantly fetch logs, identify root causes, and apply context-aware fixes. No more debugging loops. Below are few example prompts to run/debug/fix your automated tests on BrowserStack's Test Platform.
Note: When fetching Root Cause Analysis (RCA) for a test, the server returns the suggested fix as a proposal only. It never applies code changes automatically — your assistant must present the suggestion and wait for your explicit approval before editing any files.
#Port test suite to BrowserStack
"Setup test suite to run on BrowserStack infra"
#Run tests on BrowserStack
“Run my tests on BrowserStack”
#AI powered debugging of test failures
"My App Automate tests have failed, can you help me fix the new failures?"
- Fix test failures reported by your CI/CD pipeline by utilising our industry leading Test Observability features. Find more info here.
- Run tests written in Jest, Playwright, Selenium, and more on BrowserStack's Test Platform
🌐 Accessibility
Catch accessibility issues early with automated, local a11y scans. Get one-click, AI-suggested fixes. No docs hunting, no CI surprises. Ensure WCAG and ADA compliance with our Accessibility Testing tool
#Scan accessibility issues while development
"Scan & help fix accessibility issues for my website running locally on localhost:3000"
#Scan accessibility issues on production site
“Run accessibility scan & identify issues on my website - www.bstackdemo.com”
📋 Test Management
Create and manage test cases, create test plans and trigger test runs using natural language. Below are a few example prompts to utilise capabilities of BrowserStack's Test Management with MCP server.
# Create project & folder structure
"create new Test management project named My Demo Project with two sub folders - Login & Checkout"
# Add test cases
"add invalid login test case in Test Management project named My Demo Project"
# List added test cases
"list high priority Login test cases from Test Management project - My Demo Project"
# Create test run
"create a test run for Login tests from Test Management project - My Demo Project"
# Update test results
"update test results as passed for Login tests test run from My Demo Project"
⚡ Load Testing
Run and analyse load tests at scale without leaving your IDE or chat — find tests, start and stop runs, read reports and AI Insights, compare runs, and check your VU-hours. Works with API (JMeter, k6, Gatling, Locust), browser (Playwright, Selenium, WebdriverIO, Nightwatch) and hybrid load tests on BrowserStack's Load Testing. These go through the core tools.
# Find a test
"find my load test called checkout-api"
# Run it
"run checkout-api for 5 minutes with 100 virtual users"
# Check on it
"is my checkout-api run finished yet?"
# Read the results
"what was the p95 response time and error rate of the last checkout-api run?"
# Compare two runs of the same test
"did the latest checkout-api run regress compared with the previous one?"
# Check quota before a big run
"how many VU-hours do I have left, and what would a 30-minute run with 500 VUs cost?"
🧪 Access BrowserStack AI agents
Generate test cases from PRDs, convert manual tests to low-code automation, and auto-heal flaky scripts powered by BrowserStack’s AI agents, seamlessly integrated into your workflow. Below are few example prompts to access Browserstack AI agents
#Test case generator agent
"With Browserstack AI, create relevant test cases for my PRD located at /usr/file/location"
#Low code authoring agent
“With Browserstack AI, automate my manual test case X, added in Test Management”
#Self healing agent
“Help fix flaky tests in my test script with Browserstack AI self healing”
🧭 Core Tools
Five core tools let your AI assistant find and run any BrowserStack workflow. Your assistant loads every tool an MCP server exposes at the start of each session, so one tool per workflow would fill your context window and slow down the whole session. Instead, your assistant uses the core tools to search a catalog of BrowserStack tools in plain language and run the one it needs.
| Tool | Description |
|---|---|
listProducts |
Lists the BrowserStack products in the catalog, with a short summary of what each product covers |
describeEntity |
Explains one entity: its aliases, ID format, parent and related entities, and the capabilities that act on it |
searchCapability |
Finds the capabilities that match a plain-language request, with everything your assistant needs to run each one |
describeCapability |
Returns the full details of one capability, such as its parameters, request body and response format |
invokeCapability |
Runs one capability and returns the product's response unchanged. Changes to data need your approval |
See Core tools for parameters and how changes to data are approved.
All tools — See docs/TOOLS.md for every tool organised by product, or BrowserStack MCP tools & workflows for product workflows.
File & app uploads: tools that upload a local file/app (
uploadProductRequirementFile,takeAppScreenshot,runAppTestsOnBrowserStack,runAppLiveSession) require theMCP_UPLOAD_BASE_DIRenv var set to a directory containing those files; uploads are restricted to it.
🚀 Remote MCP Server
Remote MCP comes with all the functionalities of an MCP server without the hassles of complex setup or local installation.
Key benefits:
-
✅ Works seamlessly in enterprise networks without worrying about firewalls or binaries or where local installation is not allowed.
-
✅ Secure OAuth integration – no password sharing or manual credential handling.
Limitations:
- ❌ No Local Testing support (cannot test apps behind VPNs, firewalls, or localhost). If you have to do Local Testing, you would have to use a BrowserStack Local MCP server.
- ❌ Latency can be slightly higher, but nothing considerable — you generally won’t notice it in normal use.
⚠️ Important Notes
- The BrowserStack MCP Server is under active development and currently supports a subset of the MCP spec. More features will be added soon.
- Tool invocations rely on the MCP Client which in turn relies on an LLM, hence there can be some non-deterministic behaviour that can lead to unexpected results. If you have any suggestions or feedback, please open an issue to discuss.
📝 Contributing
We welcome contributions! Please open an issue to discuss any changes you'd like to make. 👉 Click here to view our Contributing Guidelines
📞 Support
For support, please:
- Open an issue in our GitHub repository if you face any issues related to the MCP Server.
- Contact our support team for any other queries.
- Email support@browserstack.com.
- Privacy policy: browserstack.com/privacy.
🚀 More Features Coming Soon
Stay tuned for exciting updates! Have any suggestions? Please open an issue to discuss.
BrowserStack MCP 질문
BrowserStack MCP를 Claude Code에 추가하려면 어떻게 하나요?
터미널에서 claude mcp add --env 'BROWSERSTACK_ACCESS_KEY=<YOUR_BROWSERSTACK_ACCESS_KEY>' --env 'BROWSERSTACK_USERNAME=<BROWSERSTACK_USERNAME>' mcp-server -- npx -y @browserstack/mcp-server를 실행합니다. 모든 프로젝트에서 사용할 수 있게 하려면 --scope user를 추가합니다.
BrowserStack MCP를 Cursor에 추가하려면 어떻게 하나요?
~/.cursor/mcp.json를 열고 mcpServers 아래에 서버를 추가합니다. 위 설치 섹션에 표시된 Cursor 구성을 사용합니다.
BrowserStack MCP server 인증은 어떻게 하나요?
BrowserStack 계정과 Account Settings에서 확인 가능한 username 및 access_key가 필요합니다. 호스팅된 클라이언트의 경우 로그인 흐름도 지원합니다.
BrowserStack MCP server에 필요한 Node 버전은 무엇인가요?
Node version 22 이상이 필요하며, v22.15.0 LTS 버전을 권장합니다.
로컬 머신에서 호스팅 중인 웹사이트를 테스트할 수 있나요?
네, 원격 서버에 배포하지 않고도 localhost에서 실행 중인 사이트를 열고 테스트할 수 있습니다.
서버에서 Playwright나 Selenium 같은 자동화 테스트 스위트를 실행할 수 있나요?
네, BrowserStack Test Platform에서 Jest, Playwright, Selenium 및 기타 스위트를 설정하고 실행하며 실패 원인 디버깅을 도울 수 있습니다.
디버깅 시 서버가 코드를 자동으로 수정하나요?
아니요, 근본 원인 분석을 통한 수정 사항은 제안 형태로만 반환되며, 파일이 수정되기 전에 사용자의 명시적인 승인이 필요합니다.