Project management for coding agents. Bugs, features, sprints. 71 tools, stdio or remote SSE.
Buggazi MCP server exists for a simple reason — assistants are far more useful when they can act on Buggazi directly instead of describing what you should do. Project management for coding agents. Bugs, features, sprints. 71 tools, stdio or remote SSE.
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.
Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
Once Buggazi is connected, these are the calls the assistant has available:
Bugs — file, track, resolve with evidence and screenshotsFeatures — plan, prioritize, link to bugs, dependency treesSprints — create, track progress, kanban boardProjects — unlimited on every plan, custom fields, auto-created from item labelsContracts — cross-tenant bug/feature filing between projects, with screenshot attachments and a human approval gateSnapshots — terminal project views, shareable HTML linksMigration — import from Jira, Linear, or Shortcut via API or plain CSV export, always with --dry-runReferrals — bgz refer gives you a code and share link. Each referral that becomes a paying customer earns you 3 months of your plan free as account credit (up toJira — LinearYou will need 5 environment variables: BGZ_API_KEY, LINEAR_API_KEY, SHORTCUT_TOKEN, YOUR_API_KEY, YOUR_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Among the planning and project tracking options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Buggazi's toolset — Bugs, Features, Sprints and 6 more — is a fair guide to whether it matches your workflow. It is maintained by jyswee; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Bugs | file, track, resolve with evidence and screenshots |
| Features | plan, prioritize, link to bugs, dependency trees |
| Sprints | create, track progress, kanban board |
| Projects | unlimited on every plan, custom fields, auto-created from item labels |
| Contracts | cross-tenant bug/feature filing between projects, with screenshot attachments and a human approval gate |
| Snapshots | terminal project views, shareable HTML links |
| Migration | import from Jira, Linear, or Shortcut via API or plain CSV export, always with --dry-run |
| Referrals | bgz refer gives you a code and share link. Each referral that becomes a paying customer earns you 3 months of your plan free as account credit (up to 12 free months per rolling year) |
| Jira | Linear |
{
"mcpServers": {
"buggazi": {
"command": "npx",
"args": ["-y", "buggazi"],
"env": {
"BGZ_API_KEY": "your-value",
"LINEAR_API_KEY": "your-value",
"SHORTCUT_TOKEN": "your-value",
"YOUR_API_KEY": "your-value",
"YOUR_KEY": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| BGZ_API_KEY | Credential the server authenticates with. | Yes |
| LINEAR_API_KEY | Credential the server authenticates with. | Yes |
| SHORTCUT_TOKEN | Credential the server authenticates with. | Yes |
| YOUR_API_KEY | Credential the server authenticates with. | Yes |
| YOUR_KEY | Credential the server authenticates with. | Yes |
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.