Redmine vs io.github.jyswee/buggazi
Redmine is an MCP server published by aarondpn. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). io.github.jyswee/buggazi is an MCP server published by jyswee. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-08. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace | ||
|---|---|---|
| Official MCP Registry | Listed Version: 2.19.1 Forks (GitHub): 10 Stars (GitHub): 59 Not marked · First seen |
Listed Version: 2.15.1 Downloads/month (npm): 1 229 Downloads/week (npm): 193 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 2.15.1 Downloads/month (npm): 1 229 Downloads/week (npm): 193 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Redmine | io.github.jyswee/buggazi |
|---|---|---|
| Marketplaces that list it | 2 | 2 |
| Stars (GitHub) (differs) | 59 (better) | 1 (worse) |
| Forks (GitHub) (differs) | 10 (better) | 0 (worse) |
| Last release (differs) | 2026-11-07 (better) | 2026-10-12 (worse) |
| Where it runs (differs) | On your machine (ghcr.io/aarondpn/redmine-mcp:2.19.1) | Remote server or your machine |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 3, secrets among them: 1 | 1, secrets among them: 1 |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence (differs) | MIT | SEE LICENSE IN LICENSE |
| Repository (differs) | github.com/aarondpn/redmine-cli | github.com/jyswee/buggazi |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Status out of date: last check 2 days ago returned HTTP 400 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Redmine
Work with Redmine issues, projects, time entries, wiki pages and more. Read-only by default.
io.github.jyswee/buggazi
Project management for coding agents. Bugs, features, sprints. Streamable HTTP + SSE remotes.
How to run each
Redmine As a local MCP server: Docker image
claude mcp add --env "REDMINE_API_KEY=<YOUR_REDMINE_API_KEY>" --env "REDMINE_SERVER=<YOUR_REDMINE_SERVER>" --transport stdio redmine-mcp -- docker run -i --rm -e REDMINE_API_KEY -e REDMINE_SERVER ghcr.io/aarondpn/redmine-mcp:2.19.1
Requires: REDMINE_API_KEY (secret), REDMINE_SERVER
io.github.jyswee/buggazi As a remote MCP server
claude mcp add --transport http buggazi https://mcp.buggazi.com/mcp --header "Authorization: Bearer <YOUR_TOKEN>"
Requires: BGZ_API_KEY (secret), Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only io.github.jyswee/buggazi has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only Redmine asks for
REDMINE_API_KEY (secret)REDMINE_MCP_ENABLE_WRITESREDMINE_SERVER
Only io.github.jyswee/buggazi asks for
BGZ_API_KEY (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Redmine · What it can do: io.github.jyswee/buggazi · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.