Bring Cross Browser Testing
to VS Code Copilot
Create your Vinkius account to connect BrowserStack to VS Code Copilot and start using all 10 AI tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code. No hosting, no server setup — just connect and start using.
GDPR Free for SubscribersCompatible with every major AI agent and IDE
Gemini
What is the BrowserStack MCP Server?
Connect your BrowserStack Automate account to any AI agent and take full control of your automated cross-browser testing pipeline through natural conversation.
What you can do
- Project Management — List all test projects and drill down into specific project details
- Build Tracking — Surface your recent automation builds, their statuses (running, failed, passed), and duration
- Session Deep Dive — Retrieve the granular executions of a specific test session, including OS and browser stats
- Log Extraction — Automatically dump and analyze the raw Selenium/Appium logs of a failed session
- Quota & Plan — View your current plan's parallel session usage and testing queue length
- Environment Specs — List all supported OS/browser combinations required to configure your capabilities
How it works
- Subscribe to this server
- Enter your BrowserStack Username and Access Key
- Start investigating your test suite directly from Claude, Cursor, or any MCP-compatible client
No more context switching to the BrowserStack dashboard just to figure out why a test timed out.
Who is this for?
- QA Engineers — fetch the exact log output of a failing session directly into your IDE for rapid debugging
- DevOps — check parallel session concurrency limits and clean up stuck execution sessions
- Software Developers — parse build results in natural language without opening the CI/CD test reports
- Test Automators — retrieve exact OS/browser configuration payload limits when updating test scripts
Built-in capabilities (10)
json`. Delete a BrowserStack build by ID
json`. Delete a BrowserStack session by ID
json`. Returns session details, OS/browser combos, results, and logs. Get all sessions within a BrowserStack automation build
json`, including parallel sessions allowed, team parallel sessions used, queued sessions, and plan name. Essential for managing execution concurrency. Get current BrowserStack plan details and parallel session usage
json`. This includes name, group ID, and recent builds associated with the project. Get full details of a BrowserStack project including linked builds
json`. Includes name, OS, browser, status, reason, duration, video URL, and log URLs. Get full details of a specific BrowserStack session
Useful for debugging failed test steps. Get text execution logs of a BrowserStack session
json`. Returns OS names/versions, browser names/versions required for configuring automation desired capabilities. List all supported OS/browser combinations on BrowserStack
json`. Returns build names, IDs, statuses (running/done/timeout/failed), durations, and session counts. Useful for tracking test suite execution. List recent builds on BrowserStack Automate
json`. Returns project names, IDs, and build counts. Used to organize automation runs. List all projects on BrowserStack Automate
Why VS Code Copilot?
GitHub Copilot Agent mode brings BrowserStack data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 10 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.
- —
VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor
- —
Project-scoped MCP configs (
.vscode/mcp.json) let you commit server configurations to your repository, ensuring the entire team shares the same tool access - —
Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop
- —
GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services
BrowserStack in VS Code Copilot
Why run BrowserStack with Vinkius?
The BrowserStack connection runs on our fully managed, secure cloud infrastructure. We handle the hosting, maintenance, and security so you don't have to deal with servers or code. All 10 tools are ready to work instantly without any complex setup.
You stay in complete control of your data. Your AI only accesses the information you approve, keeping your sensitive passwords and private details completely safe. Plus, with automatic optimizations, your AI works faster and more efficiently.
* Every connection is hosted and maintained by Vinkius. We handle the security, updates, and infrastructure so you don't have to write code or manage servers. See our infrastructure
Over 4,000 integrations ready for AI agents
Explore a vast library of pre-built integrations, optimized and ready to deploy.
Connect securely in under 30 seconds
Generate tokens to authenticate and link external services in a single step.
Complete visibility into every agent action
Audit live requests, latency, success rates, and active security compliance policies.
Optimize spending and track token ROI
Analyze real-time token consumption and cost metrics detailed by connection.
Explore our live AI Agents Analytics dashboard to see it all working
This dashboard is included when you connect BrowserStack using Vinkius. You will never be left in the dark about what your AI agents are doing with your tools.
BrowserStack and 4,000+ other AI tools. No hosting, no code, ready to use.
Professionals who connect BrowserStack to VS Code Copilot through Vinkius don't need to write code, manage servers, or worry about security. Everything is pre-configured, secure, and runs automatically in the background.
Raw MCP | Vinkius | |
|---|---|---|
| Ready-to-use MCPs | Find and configure each manually | 4,000+ MCPs ready to use |
| Connection Setup | Manual coding & server setup | 1-click instant connection |
| Server Hosting | You host it yourself (needs 24/7 uptime) | 100% hosted & managed by Vinkius |
| Security & Privacy | Stored in plaintext config files | Bank-grade encrypted vault |
| Activity Visibility | Blind execution (no logs or tracking) | Live dashboard with real-time logs |
| Cost Control | Runaway AI token spend risk | Automatic budget limits |
| Revoking Access | Must delete files or code to stop | 1-click disconnect button |
How Vinkius secures
BrowserStack for VS Code Copilot
Every request between VS Code Copilot and BrowserStack is protected by our secure gateway. We automatically keep your sensitive data private, prevent unauthorized access, and let you disconnect instantly at any time.
Frequently asked questions
Can my AI automatically read the logs of a failed Selenium test?
Yes. When you ask it to investigate a recently failed build, the agent can use get_build to find the failed session, and then automatically call get_session_logs. It will download the raw textual execution steps directly into the chat and summarize why the UI test failed.
Is there a risk that my AI alters my testing scripts or repository code?
No, this MCP server integrates exclusively with BrowserStack Automate API. It can read statuses, logs, and configurations, and can delete hung sessions or builds, but it has no connection to your actual codebase or git repository.
How can I resolve concurrent session limits preventing my pipeline from advancing?
You can ask your agent to get_plan to inspect your parallel boundaries and verify if you are queuing. Then, the agent can look up stalled items via list_builds and execute delete_session or delete_build to manually unblock stuck processes.
Which VS Code version supports MCP?
MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
How do I switch to Agent mode?
Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
Can I restrict which MCP tools Copilot can access?
Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
Does MCP work in VS Code Remote or Codespaces?
Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.
MCP tools not available
Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.
Explore More MCP Servers
View all →
Traefik Hub
8 toolsCloud-native API Management & Gateway evaluating proxy topologies explicitly running Kubernetes integrations.
Geocodio
10 toolsEmpower geocoding via Geocodio — perform batch geocoding and reverse geocoding for US/Canada, and retrieve Census and legislative data directly from any AI agent.
TimezoneDB
5 toolsManage global time — audit timezones and offsets via AI.
Polygon.io
6 toolsAccess real-time and historical stock market data, including trades, quotes, aggregates, and company metadata directly via AI.