Bring Bug Tracking
to Cursor
Learn how to connect BugHerd to Cursor and start using 10 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the BugHerd MCP Server?
O que você pode fazer
- Create and list your BugHerd projects.
- Manage tasks seamlessly inside projects.
- Retrieve, add, and monitor comments on specific bug tasks.
- View all members within your BugHerd workspace.
Como funciona
1. Install the BugHerd MCP Server on your Vinkius Edge. 2. Add your personal BugHerd API key in the credentials page. 3. Empower your AI agent to fetch bugs, add comments, and triage tickets naturally via chat.Para quem é?
Ideal for development and QA teams looking to interact with BugHerd tickets directly via Cursor, Claude, or any MCP-enabled agent. Turn your AI into a full-fledged QA assistant.Built-in capabilities (10)
Add a comment to a BugHerd task
Create a new project in BugHerd
Create a new task in a BugHerd project
Get a specific project in BugHerd
Get a specific task in BugHerd
List comments on a BugHerd task
List projects in BugHerd
List tasks for a project in BugHerd
List users in the BugHerd account
Can update description, status, priority, or assigned_to_id. Update a task in BugHerd
Why Cursor?
Cursor's Agent mode turns BugHerd into an in-editor superpower. Ask Cursor to generate code using live data from BugHerd and it fetches, processes, and writes. all in a single agentic loop. 10 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
BugHerd in Cursor
BugHerd and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect BugHerd 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 BugHerd in Cursor
The BugHerd 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 10 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
BugHerd for Cursor
Every tool call from Cursor to the BugHerd MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can the AI Agent resolve or close a task automatically?
Yes, using the update_task tool, the agent can change the task status to 'closed' or 'done' within BugHerd.
Are attachments or screenshots supported?
Currently, the MCP Server manages text-based tasks, comments, and project structures. Adding direct screenshot files via AI is not supported in this version.
Can I read comments from any ticket?
Yes! The agent can fetch and read all comments attached to a specific task using the list_comments tool, provided you supply the Project ID and Task ID.
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.