Permettez à vos clients IA de gérer et d'exécuter des tests manuels et automatisés sur BrowserStack, de déboguer les échecs et de lancer des scans d'accessibilité à partir de simples instructions en langage naturel.
Aussi connu sous browserstack/mcp-server, @browserstack/mcp-server
- Étoiles
- 153
- Outils
- —
- Téléchargements, 30 jours
- 114 405
- Dernière version
- 2.6.8
- Dernier commit
- 13 nov. 2026
- Licence
- AGPL-3.0
Qu'est-ce que BrowserStack MCP ?
BrowserStack est un serveur MCP. Permettez à vos clients IA de gérer et d'exécuter des tests manuels et automatisés sur BrowserStack, de déboguer les échecs et de lancer des scans d'accessibilité à partir de simples instructions en langage naturel.
Résumé généré à partir du README du projet
À propos du MCP server BrowserStack
La gestion et l'exécution de tests logiciels via le langage naturel est ce que ce serveur permet aux développeurs utilisant des clients dopés à l'IA comme Cursor, Claude ou VS Code. En se connectant à la plateforme de test BrowserStack, les utilisateurs peuvent déclencher des tests manuels ou automatisés, effectuer des scans d'accessibilité et gérer des plans de test sans quitter leur environnement de développement principal. Le serveur prend en charge divers frameworks de test, notamment Playwright, Selenium et Jest, tout en offrant des capacités de tests de charge avec des outils comme k6 ou JMeter.
Pour utiliser ce serveur, vous avez besoin d'un compte BrowserStack avec un nom d'utilisateur et une access key. Il peut être configuré localement ou via une connexion HTTP sans état à distance sur mcp.browserstack.com. Une fois connecté, l'assistant IA utilise des outils de base pour rechercher dans un catalogue de workflows, vous permettant de demander des actions spécifiques comme le débogage d'un crash sur Android 14 ou l'exécution d'un site web sur une version spécifique de Chrome. Le système peut même suggérer des corrections de code pour les tests automatisés ayant échoué, bien qu'une approbation explicite soit requise avant d'appliquer tout changement à vos fichiers.
Ce que vous pouvez faire avec
- 1Déboguer les échecs d'applications mobilesDemandez à l'IA d'enquêter sur la raison pour laquelle une application a planté sur un système d'exploitation mobile spécifique.
- 2Exécuter des suites de tests automatisésCommandez à votre assistant IA d'exécuter des tests automatisés existants sur l'infrastructure BrowserStack.
- 3Effectuer des scans de conformité d'accessibilitéIdentifiez et corrigez les problèmes d'accessibilité sur des sites web locaux ou en production à l'aide de scans automatisés.
- 4Gérer l'organisation des testsUtilisez le langage naturel pour créer des projets, des dossiers et des cas de test spécifiques au sein d'un système de gestion.
- 5Analyser les performances des tests de chargeDemandez des métriques détaillées et des comparaisons issues de récents tests de charge.
Extrait du README du projet. Chaque cas d'utilisation est vérifié par rapport à une citation du document.
Comment installer BrowserStack MCP
Formats vérifiés le 10 nov. 2026Ajouter à CursorAjouter à GooseInstaller BrowserStack MCP dans Claude Code
$ claude mcp add --env 'BROWSERSTACK_ACCESS_KEY=<YOUR_BROWSERSTACK_ACCESS_KEY>' --env 'BROWSERSTACK_USERNAME=<BROWSERSTACK_USERNAME>' mcp-server -- npx -y @browserstack/mcp-serverInstaller BrowserStack MCP dans Cursor
~/.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>"
}
}
}
}Installer BrowserStack MCP dans VS Code
.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>"
}
}
}
}Installer BrowserStack MCP dans VS Code CLI
$ 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>"}}'Installer BrowserStack MCP dans Claude Desktop
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>"
}
}
}
}Installer BrowserStack MCP dans Codex
$ codex mcp add mcp-server --env 'BROWSERSTACK_ACCESS_KEY=<YOUR_BROWSERSTACK_ACCESS_KEY>' --env 'BROWSERSTACK_USERNAME=<BROWSERSTACK_USERNAME>' -- npx -y @browserstack/mcp-serverInstaller BrowserStack MCP dans Codex config.toml
~/.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>"
Installer BrowserStack MCP dans Gemini CLI
$ gemini mcp add -s user -e 'BROWSERSTACK_ACCESS_KEY=<YOUR_BROWSERSTACK_ACCESS_KEY>' -e 'BROWSERSTACK_USERNAME=<BROWSERSTACK_USERNAME>' mcp-server npx -- -y @browserstack/mcp-serverInstaller BrowserStack MCP dans Gemini settings.json
~/.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>"
}
}
}
}Configuration
BROWSERSTACK_ACCESS_KEYRequisSecretBrowserStack Access Key
BROWSERSTACK_USERNAMERequisBrowserStack Username
| Nom | Description | Type |
|---|---|---|
| BROWSERSTACK_ACCESS_KEY | BrowserStack Access Key | RequisSecret |
| BROWSERSTACK_USERNAME | BrowserStack Username | Requis |
Vérifications automatisées
Exécuté le 12 nov. 2026Rapport complet →A passé nos vérifications automatisées. Il ne s'agit pas d'un audit de sécurité : lisez le code et donnez au serveur l'accès le plus restreint dont il a besoin. Fonctionnement des vérifications
- Dépôt source lié et accessibleRéussi
- Licence open source (OSI)Réussi
- Commit ou version publiée au cours de l'année écouléeRéussi
- Nom du package non proche d'un package populaireRéussi
- L'endpoint distant utilise HTTPSRéussi
- Les outils destructifs sont étiquetésNon vérifié
- Aucune instruction cachée destinée au modèleRéussi
- Aucun avis critique dans le package ou ses dépendancesRéussi
README
Voir sur GitHubBrowserStack 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.
Questions sur BrowserStack MCP
Comment ajouter BrowserStack MCP à Claude Code ?
Exécutez claude mcp add --env 'BROWSERSTACK_ACCESS_KEY=<YOUR_BROWSERSTACK_ACCESS_KEY>' --env 'BROWSERSTACK_USERNAME=<BROWSERSTACK_USERNAME>' mcp-server -- npx -y @browserstack/mcp-server dans votre terminal. Ajoutez --scope user pour le rendre disponible dans tous les projets.
Comment ajouter BrowserStack MCP à Cursor ?
Ouvrez ~/.cursor/mcp.json et ajoutez le serveur sous mcpServers, avec la configuration Cursor indiquée dans la section d'installation ci-dessus.
Comment puis-je m'authentifier au MCP server de BrowserStack ?
Vous avez besoin d'un compte BrowserStack ainsi que de votre nom d'utilisateur et de votre access_key depuis vos paramètres de compte ; les flux de connexion sont également pris en charge pour les clients hébergés.
Quelle version de Node le MCP server de BrowserStack nécessite-t-il ?
Il nécessite la version 22 de Node ou une version ultérieure, la version v22.15.0 LTS étant recommandée.
Puis-je tester des sites web hébergés localement sur ma machine ?
Oui, vous pouvez ouvrir et tester des sites s'exécutant sur localhost sans avoir à les déployer sur un serveur distant.
Le serveur peut-il exécuter des suites de tests automatisés comme Playwright et Selenium ?
Oui, il peut configurer et exécuter Jest, Playwright, Selenium et d'autres suites sur la plateforme de test de BrowserStack, tout en aidant au débogage des échecs.
Le serveur applique-t-il automatiquement des corrections de code lors du débogage ?
Non, les corrections issues de l'analyse des causes profondes sont retournées uniquement sous forme de propositions et nécessitent votre approbation explicite avant toute modification de fichier.