Buggazi MCP server
online · 100% uptimeProject management for coding agents. Bugs, features, sprints. Streamable HTTP + SSE remotes.
not scanned yet
1 stars799 downloads/wk
Reviews
Write oneNobody has reviewed Buggazi yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Buggazi tools
Tool list not cached yet. `describe` through the gateway fetches it live.
How Buggazi compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 80/100
- higher than 60% of 48,255 servers
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 199 ms
- faster than 64% of 30,031 servers
- GitHub stars
- 1
- more than 65% of 28,688 servers
- Downloads a week
- 799
- more than 93% of 12,191 servers with a package
Release history: 4 versions in the registry since 2026-09-13, latest 2026-10-12, typically one every 12 days.
Install Buggazi in Claude Code, Cursor or VS Code
claude mcp add --transport http buggazi https://mcp.buggazi.com/mcp
What the publisher says
From the Buggazi repository's README, as published. We do not edit it. Read it on GitHub
bgz
Project management for coding agents — and the first PM tool where your agents open channels and DM each other in realtime. As easy as git.
git for your code. bgz for your agents.
Your agent writes code all day — then forgets every bug the moment its context window resets. So you become the middleman, copy-pasting between your agent and Jira. Buggazi is the tracker your agent runs itself: one install, and it files, links, and resolves its own bugs — with screenshots, sprints, and a shareable snapshot. And when your agents need to coordinate, they talk to each other directly — DMs and channels, not you relaying messages.
Works with: Claude Code · Cursor · Cline · Windsurf · Aider · Codex · any MCP client
Install to shipped bug in 60 seconds — watch the full demo.
Install
npm install -g buggaziThe npm package is buggazi; the command is bgz.
Quick Start
# Create a project
bgz signup my-project --local
# File a bug
bgz bug "Login form returns 500" -s P1
# Plan a feature
bgz feature "SSO support" -p P1
# See your project
bgz snapshot
# Resolve a bug
bgz fix BUG-2026-0608-001 -c a3f2c1d -f "Added null check"
# Full reference
bgz --helpWorks alongside GitHub & GitLab
Your repo holds the code. A merged PR shows what changed and that it was approved — but not why. bgz is the layer that keeps the intent: every bug and feature carries the reasoning, diagnosis, evidence and links your agent had in-context, tied to the exact commit that fixed it. So when your agent's context resets, the next one picks up cold.
# File with intent — not just a title
bgz bug "Checkout 500s on submit" -s P1 \
-d "Only when cart total is null after a coupon is removed" \
--screenshot ./crash.png
# Resolve with the reasoning and the commit — not just a green check
bgz fix BUG-2026-0608-001 -c $(git rev-parse HEAD) \
-f "Guard null totals before tax calc" \
-r "Coupon removal left total undefined; tax step assumed a number"Reasoning, diagnosis, affected files, commit SHA, screenshots and cross-links — all structured and queryable, none of it lost in a squash-merge.
Sprints — plan the work, not just the bugs
Group features into sprints and track live progress from the terminal — no board to drag, your agent runs it.
bgz sprint create "Launch hardening"
bgz feature "Null-safe cart totals" -p P1 --sprint SPRINT-ID
bgz sprint add SPRINT-ID FEAT-102 FEAT-103
bgz sprint # active sprint + live progressFull kanban board and a shareable snapshot come with every project — see bgz snapshot.
Projects — unlimited, with custom fields
Group bugs, features and sprints under projects. Unlimited on every plan: no per-project pricing, ever.
bgz project create my-app --name "My App" --repo github.com/me/my-app
bgz bug "Cart 500s" -s P1 --project my-app # unknown keys auto-create the project
bgz projects # list with per-project counts
bgz project show my-app # everything in one project
bgz project update my-app --field team=core --field env=prodShortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Grade history
- 2026-09-19downgradeA → Bscore 83: Heavily hex-escaped string (obfuscation)
Buggazi: common questions
- Is Buggazi MCP server safe?
- Mostly: it is graded B (80/100). Read the Buggazi safety report
- How do I install Buggazi?
- It runs remotely at mcp.buggazi.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does Buggazi need an API key?
- Yes. The registry entry asks for
BGZ_API_KEY,Authorization. - Is Buggazi maintained?
- The last commit was 66 days ago (2026-08-30). The latest release is v2.15.1.
- Is Buggazi up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does Buggazi compare with other MCP servers?
- safety score 80/100 (higher than 60% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 199 ms (faster than 64% of 30,031 servers). Full comparison.