io.github.Berckan/bugherd-mcp
NPM · BUGHERD-MCP
BugHerd API v2 integration — 37 tools for projects, tasks, comments, and webhooks.
Available components
Last scanned (11 hours ago)
Scores higher than 69% of npm servers
Category Project Management
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency44
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 259 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1983 tokens (~53/item across 37 items; 37 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "bugherd_delete_project" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 37 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +1
- Stability: 0.97 → pass security
- 3 Nov 26 −1
- Stability: pass → 0.93 functional
- 28 Oct 26 +1
- Stability: 0.97 → pass security
- 27 Oct 26 −1
- Stability: pass → 0.97 functional
- 21 Oct 26 +1
- Stability: 0.97 → pass security
- 20 Oct 26 −1
- Stability: pass → 0.97 functional
- 17 Oct 26 +3
- Stability: 0.83 → pass security
- 15 Oct 26 −3
- Stability: pass → 0.80 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/bugherd-mcp@0.2.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
bugherd_add_guest ~66
Add a guest/client to a project by user ID or email.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | Email of the guest to add | |
| project_id | number | yes | The BugHerd project ID |
| user_id | number | – | The user ID to add as guest |
No output schema declared.
No examples provided.
bugherd_add_member ~48
Add a team member to a project.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | number | yes | The BugHerd project ID |
| user_id | number | yes | The user ID to add as member |
No output schema declared.
No examples provided.
bugherd_create_attachment ~68
Create an attachment from a URL.
| Name | Type | Req | Description |
|---|---|---|---|
| file_name | string | yes | Name of the file |
| project_id | number | yes | The BugHerd project ID |
| task_id | number | yes | The task ID |
| url | string | yes | URL of the file to attach |
No output schema declared.
No examples provided.
bugherd_create_column ~54
Create a new column in a project's Kanban board.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Column name |
| position | number | – | Column position |
| project_id | number | yes | The BugHerd project ID |
No output schema declared.
No examples provided.
bugherd_create_comment ~79
Add a comment to a task.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | Email of the user posting the comment | |
| project_id | number | yes | The BugHerd project ID |
| task_id | number | yes | The task ID |
| text | string | yes | Comment text |
| user_id | number | – | User ID posting the comment |
No output schema declared.
No examples provided.
bugherd_create_project ~67
Create a new BugHerd project.
| Name | Type | Req | Description |
|---|---|---|---|
| devurl | string | yes | Development URL for the project |
| is_active | boolean | – | Whether the project is active |
| is_public | boolean | – | Whether the project is public |
| name | string | yes | Project name |
No output schema declared.
No examples provided.
bugherd_create_task ~115
Create a new task/bug in a project.
| Name | Type | Req | Description |
|---|---|---|---|
| assigned_to_id | number | – | User ID to assign task to |
| description | string | yes | Task description |
| external_id | string | – | External reference ID |
| priority | string | – | Task priority |
| project_id | number | yes | The BugHerd project ID |
| requester_email | string | – | Email of the requester |
| status | string | – | Task status/column name |
| tag_names | array | – | Tags for the task |
No output schema declared.
No examples provided.
bugherd_create_webhook ~66
Create a webhook to receive notifications for BugHerd events.
| Name | Type | Req | Description |
|---|---|---|---|
| event | string | yes | Event type that triggers the webhook |
| project_id | number | – | Optional project ID to scope the webhook |
| target_url | string | yes | URL to receive webhook POST requests |
No output schema declared.
No examples provided.
bugherd_delete_attachment ~61
⚠️ DESTRUCTIVE: Delete an attachment permanently.
| Name | Type | Req | Description |
|---|---|---|---|
| attachment_id | number | yes | The attachment ID to delete |
| project_id | number | yes | The BugHerd project ID |
| task_id | number | yes | The task ID |
No output schema declared.
No examples provided.
bugherd_delete_project ~43
⚠️ DESTRUCTIVE: Delete a project and all its tasks permanently.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | number | yes | The BugHerd project ID to delete |
No output schema declared.
No examples provided.
bugherd_delete_webhook ~37
⚠️ DESTRUCTIVE: Delete a webhook permanently.
| Name | Type | Req | Description |
|---|---|---|---|
| webhook_id | number | yes | The webhook ID to delete |
No output schema declared.
No examples provided.
bugherd_get_attachment ~54
Get details of a specific attachment.
| Name | Type | Req | Description |
|---|---|---|---|
| attachment_id | number | yes | The attachment ID |
| project_id | number | yes | The BugHerd project ID |
| task_id | number | yes | The task ID |
No output schema declared.
No examples provided.
bugherd_get_column ~43
Get details of a specific column.
| Name | Type | Req | Description |
|---|---|---|---|
| column_id | number | yes | The column ID |
| project_id | number | yes | The BugHerd project ID |
No output schema declared.
No examples provided.
bugherd_get_organization ~21
Get organization/account details including name and timezone.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
bugherd_get_project ~32
Get details of a specific project.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | number | yes | The BugHerd project ID |
No output schema declared.
No examples provided.
bugherd_get_task ~57
Get detailed information about a specific task including description, screenshot URL, selector info, and metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | number | yes | The BugHerd project ID |
| task_id | number | yes | The task ID to retrieve |
No output schema declared.
No examples provided.
bugherd_get_task_by_local_id ~57
Get a task by its local ID (#123) within a project.
| Name | Type | Req | Description |
|---|---|---|---|
| local_task_id | number | yes | The local task ID (#123) |
| project_id | number | yes | The BugHerd project ID |
No output schema declared.
No examples provided.
bugherd_get_task_global ~38
Get a task by its global ID (without needing the project ID).
| Name | Type | Req | Description |
|---|---|---|---|
| task_id | number | yes | The global task ID |
No output schema declared.
No examples provided.
bugherd_get_user_projects ~31
Get projects accessible to a specific user.
| Name | Type | Req | Description |
|---|---|---|---|
| user_id | number | yes | The user ID |
No output schema declared.
No examples provided.
bugherd_get_user_tasks ~62
Get tasks assigned to a specific user.
| Name | Type | Req | Description |
|---|---|---|---|
| page | number | – | Page number for pagination |
| priority | string | – | Filter by priority |
| status | string | – | Filter by status |
| user_id | number | yes | The user ID |
No output schema declared.
No examples provided.
bugherd_list_active_projects ~17
List only active projects.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
bugherd_list_archived_tasks ~45
List archived tasks for a project.
| Name | Type | Req | Description |
|---|---|---|---|
| page | number | – | Page number for pagination |
| project_id | number | yes | The BugHerd project ID |
No output schema declared.
No examples provided.
bugherd_list_attachments ~44
List all attachments on a task.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | number | yes | The BugHerd project ID |
| task_id | number | yes | The task ID |
No output schema declared.
No examples provided.
bugherd_list_columns ~54
List all columns (statuses) for a project. Use this to find the correct status names for updating tasks in projects with custom Kanban boards.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | number | yes | The BugHerd project ID |
No output schema declared.
No examples provided.
bugherd_list_comments ~57
List all comments on a specific task. Returns comment text, author, and timestamp.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | number | yes | The BugHerd project ID |
| task_id | number | yes | The task ID to get comments for |
No output schema declared.
No examples provided.
bugherd_list_feedback_tasks ~49
List feedback tasks (unprocessed/new) for a project.
| Name | Type | Req | Description |
|---|---|---|---|
| page | number | – | Page number for pagination |
| project_id | number | yes | The BugHerd project ID |
No output schema declared.
No examples provided.
bugherd_list_guests ~21
List only guests/clients in the organization.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
bugherd_list_members ~19
List only team members in the organization.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
bugherd_list_projects ~32
List all BugHerd projects accessible to the authenticated user. Returns project names, URLs, and IDs.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
bugherd_list_taskboard_tasks ~53
List taskboard tasks (not feedback, not archived) for a project.
| Name | Type | Req | Description |
|---|---|---|---|
| page | number | – | Page number for pagination |
| project_id | number | yes | The BugHerd project ID |
No output schema declared.
No examples provided.
bugherd_list_tasks ~139
List tasks (bugs/feedback) for a specific BugHerd project. Can filter by status (use column name from bugherd_list_columns), priority, or tag.
| Name | Type | Req | Description |
|---|---|---|---|
| page | number | – | Page number for pagination (default: 1) |
| priority | string | – | Filter by priority |
| project_id | number | yes | The BugHerd project ID |
| status | string | – | Filter by task status (use column name from bugherd_list_columns, e.g., 'backlog', 'todo', 'doing', 'Ready for review', 'done') |
| tag | string | – | Filter by tag name |
No output schema declared.
No examples provided.
bugherd_list_users ~23
List all users (members + guests) in the organization.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
bugherd_list_webhooks ~21
List all webhooks configured for the organization.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
bugherd_move_tasks ~58
Move tasks from one project to another.
| Name | Type | Req | Description |
|---|---|---|---|
| destination_project_id | number | yes | The destination project ID |
| project_id | number | yes | The source project ID |
| task_ids | array | yes | Array of task IDs to move |
No output schema declared.
No examples provided.
bugherd_update_column ~66
Update a column's name or position.
| Name | Type | Req | Description |
|---|---|---|---|
| column_id | number | yes | The column ID to update |
| name | string | – | New column name |
| position | number | – | New column position |
| project_id | number | yes | The BugHerd project ID |
No output schema declared.
No examples provided.
bugherd_update_project ~77
Update a project's settings.
| Name | Type | Req | Description |
|---|---|---|---|
| devurl | string | – | New development URL |
| is_active | boolean | – | Whether the project is active |
| is_public | boolean | – | Whether the project is public |
| name | string | – | New project name |
| project_id | number | yes | The BugHerd project ID |
No output schema declared.
No examples provided.
bugherd_update_task ~109
Update a task's status, priority, or description. Use this to mark tasks as done or move them through workflow stages.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | New description for the task |
| priority | string | – | New priority for the task |
| project_id | number | yes | The BugHerd project ID |
| status | string | – | New status for the task (use column name from bugherd_list_columns) |
| task_id | number | yes | The task ID to update |
No output schema declared.
No examples provided.
How do I install the io.github.Berckan/bugherd-mcp server?
io.github.Berckan/bugherd-mcp runs locally as an npm package, launched with npx -y bugherd-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · bugherd-mcp
claude mcp add berckan-bugherd-mcp -- npx -y bugherd-mcp
What is the io.github.Berckan/bugherd-mcp server?
io.github.Berckan/bugherd-mcp is listed in the public MCP registry as io.github.Berckan/bugherd-mcp. BugHerd API v2 integration, 37 tools for projects, tasks, comments, and webhooks. This page covers its npm package (bugherd-mcp).
Is the io.github.Berckan/bugherd-mcp server safe to use?
io.github.Berckan/bugherd-mcp scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.Berckan/bugherd-mcp server expose?
io.github.Berckan/bugherd-mcp exposes 37 tools: bugherd_get_organization, bugherd_list_users, bugherd_list_members, bugherd_list_guests, bugherd_get_user_tasks, and 32 more. Their descriptions and schemas cost roughly 1,983 tokens of context every time the server is loaded.
Is the io.github.Berckan/bugherd-mcp server still maintained?
io.github.Berckan/bugherd-mcp is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.Berckan/bugherd-mcp server under?
io.github.Berckan/bugherd-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.