BugBug MCP Server for CursorGive Cursor instant access to 12 tools to Get Ips, Get Suite, Get Suite Run, and more
Cursor is an AI-first code editor built on VS Code that integrates LLM-powered coding assistance directly into the development workflow. Its Agent mode enables autonomous multi-step coding tasks, and MCP support lets agents access external data sources and APIs during code generation.
Ask AI about this App Connector for Cursor
The BugBug app connector for Cursor is a standout in the Developer Tools category — giving your AI agent 12 tools to work with, ready to go from day one.
Vinkius delivers Streamable HTTP and SSE to any MCP client
Vinkius Desktop App
The modern way to manage MCP Servers — no config files, no terminal commands. Install BugBug and 3,400+ MCP Servers from a single visual interface.
{
"mcpServers": {
"bugbug": {
"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 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.
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.
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
The BugBug MCP Server exposes 12 tools through the Vinkius. Connect it to Cursor in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.
All 12 BugBug tools available for Cursor
When Cursor connects to BugBug through Vinkius, your AI agent gets direct access to every tool listed below — spanning browser-automation, end-to-end-testing, no-code-testing, and more. Every call is secured with network, filesystem, subprocess, and code evaluation entitlements inside a sandboxed runtime. Beyond a simple connection, you get a full AI Gateway with real-time visibility into agent activity, enterprise governance, and optimized token usage.
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
Connect BugBug to Cursor via MCP
Follow these steps to wire BugBug into Cursor. The entire setup takes under two minutes — your credentials stay safe behind the Vinkius.
Open MCP Settings
Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) → search "MCP Settings"Add the server config
mcp.json file that opensSave the file
Start using BugBug
Why Use Cursor with the BugBug MCP Server
Cursor AI Code Editor provides unique advantages when paired with BugBug through the Model Context Protocol.
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 + Cursor Use Cases
Practical scenarios where Cursor combined with the BugBug MCP Server delivers measurable value.
Code generation with live data: ask Cursor to generate a security report module using live DNS and subdomain data fetched through MCP
Automated documentation: have Cursor query your API's tool schemas and generate TypeScript interfaces or OpenAPI specs automatically
Infrastructure-as-code: Cursor can fetch domain configurations and generate corresponding Terraform or CloudFormation templates
Test scaffolding: ask Cursor to pull real API responses via MCP and generate unit test fixtures from actual data
Example Prompts for BugBug in Cursor
Ready-to-use prompts you can give your Cursor agent to start working with BugBug immediately.
"List all my automated tests in BugBug."
"Run the 'Smoke Test' suite (ID: 'suite_456') in the 'Staging' environment."
"Show the status and results for the latest test run ID 'run_789'."
Troubleshooting BugBug MCP Server with Cursor
Common issues when connecting BugBug to Cursor through the Vinkius, and how to resolve them.
Tools not appearing in Cursor
Server shows as disconnected
BugBug + Cursor FAQ
Common questions about integrating BugBug MCP Server with Cursor.
What is Agent mode and why does it matter for MCP?
Where does Cursor store MCP configuration?
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.