BrowserStack MCP Server for VS Code Copilot 10 tools — connect in under 2 minutes
GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.
ASK AI ABOUT THIS MCP SERVER
Vinkius supports streamable HTTP and SSE.
Vinkius Desktop App
The modern way to manage MCP Servers — no config files, no terminal commands. Install BrowserStack and 2,500+ MCP Servers from a single visual interface.
{
"mcpServers": {
"browserstack": {
"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
}
}
}
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
About 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.
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.
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
The BrowserStack MCP Server exposes 10 tools through the Vinkius. Connect it to VS Code Copilot in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.
How to Connect BrowserStack to VS Code Copilot via MCP
Follow these steps to integrate the BrowserStack MCP Server with VS Code Copilot.
Create MCP config
Create a .vscode/mcp.json file in your project root
Add the server config
Paste the JSON configuration above
Enable Agent mode
Open GitHub Copilot Chat and switch to Agent mode using the dropdown
Start using BrowserStack
Ask Copilot: "Using BrowserStack, help me...". 10 tools available
Why Use VS Code Copilot with the BrowserStack MCP Server
GitHub Copilot for Visual Studio Code provides unique advantages when paired with BrowserStack through the Model Context Protocol.
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 + VS Code Copilot Use Cases
Practical scenarios where VS Code Copilot combined with the BrowserStack MCP Server delivers measurable value.
Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step
DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review
Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses
Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples
BrowserStack MCP Tools for VS Code Copilot (10)
These 10 tools become available when you connect BrowserStack to VS Code Copilot via MCP:
delete_build
json`. Delete a BrowserStack build by ID
delete_session
json`. Delete a BrowserStack session by ID
get_build
json`. Returns session details, OS/browser combos, results, and logs. Get all sessions within a BrowserStack automation build
get_plan
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
get_project
json`. This includes name, group ID, and recent builds associated with the project. Get full details of a BrowserStack project including linked builds
get_session
json`. Includes name, OS, browser, status, reason, duration, video URL, and log URLs. Get full details of a specific BrowserStack session
get_session_logs
Useful for debugging failed test steps. Get text execution logs of a BrowserStack session
list_browsers
json`. Returns OS names/versions, browser names/versions required for configuring automation desired capabilities. List all supported OS/browser combinations on BrowserStack
list_builds
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
list_projects
json`. Returns project names, IDs, and build counts. Used to organize automation runs. List all projects on BrowserStack Automate
Example Prompts for BrowserStack in VS Code Copilot
Ready-to-use prompts you can give your VS Code Copilot agent to start working with BrowserStack immediately.
"List my recent automation builds and summarize their outcomes."
"Fetch the logs for the failed session in build e4da3b."
"Check how many parallel sessions our current plan allows."
Troubleshooting BrowserStack MCP Server with VS Code Copilot
Common issues when connecting BrowserStack to VS Code Copilot through the Vinkius, and how to resolve them.
MCP tools not available
BrowserStack + VS Code Copilot FAQ
Common questions about integrating BrowserStack MCP Server with VS Code Copilot.
Which VS Code version supports MCP?
How do I switch to Agent mode?
Can I restrict which MCP tools Copilot can access?
Does MCP work in VS Code Remote or Codespaces?
.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.Connect BrowserStack with your favorite client
Step-by-step setup guides for every MCP-compatible client and framework:
Anthropic's native desktop app for Claude with built-in MCP support.
AI-first code editor with integrated LLM-powered coding assistance.
GitHub Copilot in VS Code with Agent mode and MCP support.
Purpose-built IDE for agentic AI coding workflows.
Autonomous AI coding agent that runs inside VS Code.
Anthropic's agentic CLI for terminal-first development.
Python SDK for building production-grade OpenAI agent workflows.
Google's framework for building production AI agents.
Type-safe agent development for Python with first-class MCP support.
TypeScript toolkit for building AI-powered web applications.
TypeScript-native agent framework for modern web stacks.
Python framework for orchestrating collaborative AI agent crews.
Leading Python framework for composable LLM applications.
Data-aware AI agent framework for structured and unstructured sources.
Microsoft's framework for multi-agent collaborative conversations.
Connect BrowserStack to VS Code Copilot
Get your token, paste the configuration, and start using 10 tools in under 2 minutes. No API key management needed.