Ybug vs Bugherd MCP
A side-by-side look at the Ybug and Bugherd MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Ybug for support & service management work; choose Bugherd MCP for support & service management. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Ybug when
- You need dedicated capabilities in the Support & Service Management domain.
- Its auth model fits you: OAuth 2.0.
Choose Bugherd MCP when
- You need dedicated capabilities in the Support & Service Management domain.
- You want tools like
bugherd_get_organization, bugherd_list_users, bugherd_list_members.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Support & Service Management | Support & Service Management |
| Quality signal | 32/100 · Emerging | 45/100 · Fair |
| Install command | Not confirmed yet | Not confirmed yet |
| Transport | — | — |
| Auth | OAuth 2.0 | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
Tools & capabilities
Ybug tools
No tool names declared yet. Check the project README from the listing page.
Bugherd MCP tools 37
bugherd_get_organizationGet organization/account detailsbugherd_list_usersList all users (members + guests)bugherd_list_membersList only team membersbugherd_list_guestsList only guests/clientsbugherd_get_user_tasksGet tasks assigned to a userbugherd_get_user_projectsGet projects for a userbugherd_list_projectsList all projectsbugherd_list_active_projectsList only active projectsbugherd_get_projectGet project detailsbugherd_create_projectCreate a new projectbugherd_update_projectUpdate project settingsbugherd_delete_project⚠️ Delete a project permanently- +25 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Ybug
No confirmed install command for Ybug yet — follow the setup steps linked from its listing page rather than a guessed package name.
Bugherd MCP
No confirmed install command for Bugherd MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Ybug is categorized under Support & Service Management and uses an install path we have not confirmed yet. Bugherd MCP belongs to Support & Service Management and uses an install path we have not confirmed yet. Pick Ybug for support & service management work and Bugherd MCP for support & service management.
Neither server has a confirmed install command yet, so we don't publish a guessed config. Follow each project's own setup instructions, linked from its listing page.
Ybug has no declared pricing — check the project's own site. Auth: oauth 2.0. Bugherd MCP has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add ybug and berckan-bugherd-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Ybug has a quality signal of 32/100 (Emerging) with 0 views, 0 installs and 0 GitHub stars. Bugherd MCP has 45/100 (Fair) with 1 views, 0 installs and 7 GitHub stars.
