Bring Browser Automation
to Cursor
Learn how to connect BugBug to Cursor 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 Cursor?
Cursor's Agent mode turns BugBug into an in-editor superpower. Ask Cursor to generate code using live data from BugBug and it fetches, processes, and writes. all in a single agentic loop. 12 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
BugBug in Cursor
BugBug and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect BugBug to Cursor 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 Cursor
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 Cursor 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 Cursor
Every tool call from Cursor 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.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.