How to Use the BrowserStack MCP in VS Code Copilot

Q: How do I set up the BrowserStack integration in VS Code Copilot?

Create a .vscode/mcp.json file in your project root and add the server settings. Once committed, anyone on your team using VS Code Copilot can access the tools.

Q: Can I use VS Code Copilot to find supported OS versions on BrowserStack?

Yes, you can ask Copilot to list them. The agent runs listbrowsers to fetch the current list of supported operating systems and browser versions.

Q: How does VS Code Copilot retrieve BrowserStack execution logs?

Copilot uses this MCP Server to call the getsessionlogs tool to pull the raw text execution logs of a specific session directly into your chat.

Q: Can I check how many parallel sessions my team is using?

Yes. Ask Copilot for your team's usage, and it will run getplan to show you active and queued sessions.

Debug failing BrowserStack builds and pull raw execution logs directly into your VS Code Copilot chat.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect BrowserStack MCP to VS Code Copilot

Create your Vinkius account to connect BrowserStack to VS Code Copilot and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup BrowserStack with VS Code Copilot

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Team-wide debugging with the VS Code Copilot MCP Server

Share your testing tools across your entire engineering team. By committing the server config to your repository, every developer gets instant access to `get_session_logs` and `get_session` through VS Code Copilot. When a pipeline run fails, any team member can ask Copilot to inspect the logs. The agent pulls the exact failure reason and suggests a fix, keeping everyone aligned without manual dashboard lookups.

Inspect test builds directly in your workspace

Monitor your automated test runs without leaving your editor. Copilot uses the MCP Server to call `list_builds` and `get_build` to fetch active run statuses, durations, and session counts. You can ask Copilot to summarize the results of your latest test suite. It breaks down which OS and browser combinations failed and links you directly to the relevant files in your workspace.

Keep your automation workspace clean

Avoid cluttering your testing history with local debug runs. Copilot can clean up your project by using `delete_build` and `delete_session` to remove temporary test runs. It can also check your team's concurrency limits using `get_plan`. This prevents you from triggering new builds that would get stuck in the queue and slow down your CI/CD pipeline.

Setup guide

Set up BrowserStack MCP in VS Code Copilot

Prerequisites

VS Code 1.99 or later with GitHub Copilot extension
Active Vinkius subscription with a valid endpoint token

1

Open MCP configuration

Open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and run "MCP: Add Server". Select HTTP (Streamable) as the server type. VS Code will create .vscode/mcp.json in your workspace.
2

Add the BrowserStack MCP

Paste the JSON snippet shown on the right into your .vscode/mcp.json. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Switch to Agent mode

Open Copilot Chat (Cmd+Shift+I / Ctrl+Shift+I) and switch to Agent mode using the dropdown. MCP tools are only available in Agent mode — they do not appear in Edit or Ask modes.
4

Verify the connection

In the Copilot Chat input, type # to list available tools. You should see the BrowserStack tools listed. Try asking: "List my recent BrowserStack transactions" and Copilot will invoke them automatically.

.vscode/mcp.json

{
  "mcpServers": {
    "browserstack-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by BrowserStack. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect BrowserStack now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about BrowserStack MCP in VS Code Copilot

Create a `.vscode/mcp.json` file in your project root and add the server settings. Once committed, anyone on your team using VS Code Copilot can access the tools.

Yes, you can ask Copilot to list them. The agent runs `list_browsers` to fetch the current list of supported operating systems and browser versions.

Copilot uses this MCP Server to call the `get_session_logs` tool to pull the raw text execution logs of a specific session directly into your chat.

Yes. Ask Copilot for your team's usage, and it will run `get_plan` to show you active and queued sessions.

Your build IDs and logs are processed entirely in memory during your active Copilot session. Vinkius hosts the MCP Server in a zero-trust, ephemeral environment, meaning no test data is saved or logged on our servers.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript