Bring Bug Tracking
to VS Code Copilot
Learn how to connect BugHerd to VS Code Copilot 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 VS Code Copilot?
GitHub Copilot Agent mode brings BugHerd data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 10 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
BugHerd in VS Code Copilot
BugHerd and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect BugHerd 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 BugHerd in VS Code Copilot
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 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
BugHerd for VS Code Copilot
Every tool call from VS Code Copilot 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.
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.