Bring Browser Automation
to VS Code Copilot
Learn how to connect BugBug to VS Code Copilot and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the BugBug MCP Server?
Connect your BugBug account to any AI agent and take full control of your automated browser testing and application quality monitoring through natural conversation.
What you can do
- Test Orchestration — List and run high-fidelity automated browser tests in the cloud programmatically, including support for custom environment IDs
- Suite Execution Architecture — Trigger entire test suites to run simultaneously and monitor their aggregate results to oversee platform-wide quality in real-time
- Run Intelligence — Retrieve detailed high-fidelity reports and execution status for every test run to identify regressions and friction points instantly
- History & Performance Monitoring — Access complete historical records of past test and suite runs to coordinate your QA trends programmatically
- Infrastructure Visibility — Access high-fidelity metadata for your projects and retrieve BugBug IP addresses for secure firewall allowlisting directly through your agent
How it works
1. Subscribe to this server
2. Retrieve your API Token from your BugBug dashboard (Integrations tab)
3. Start automating your QA pipeline from Claude, Cursor, or any MCP client
No more manual triggering of cloud tests or digging through complex run logs. Your AI acts as your dedicated QA engineer and quality architect.
Who is this for?
- QA Engineers — instantly trigger regression suites and retrieve results using natural language commands
- Developers — verify application quality after a deployment without leaving your creative workspace
- DevOps Teams — automate the retrieval of testing IPs and monitor suite performance through simple AI queries
Built-in capabilities (12)
Get BugBug IP addresses
Get details for a specific suite
Get status of a suite run
Get details for a specific test
Get status of a test run
List all projects
List recent suite runs
List all test suites
List recent test runs
List all tests
Run a specific test suite
Run a specific test
Why VS Code Copilot?
GitHub Copilot Agent mode brings BugBug data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 12 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
BugBug in VS Code Copilot
BugBug and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect BugBug to VS Code Copilot through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for BugBug in VS Code Copilot
The BugBug 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. All 12 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in VS Code Copilot only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* 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
How Vinkius secures
BugBug for VS Code Copilot
Every tool call from VS Code Copilot to the BugBug MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I find my BugBug API Token?
Log in to your account, navigate to the Integrations tab in the sidebar, and copy your unique API Token.
Can I run tests in a specific environment?
Yes! Both run_test and run_suite tools accept an optional environmentId parameter to target specific deployment stages.
How do I get the IP addresses for allowlisting?
Use the get_ips tool to retrieve the list of high-fidelity IP addresses used by BugBug's cloud infrastructure programmatically.
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.