Every improvement in dev tooling has led to developers wearing more hats. Frontend/backend became full-stack. Ops became DevOps, then DevSecOps. With AI-assisted development accelerating everything, developers are increasingly taking on product responsibilities too. But that only works if customer feedback is accessible where you already work, not siloed in a separate tool.
So Quackback ships with a built-in MCP server. Connect Claude Code, Cursor, or any MCP-compatible agent and it gets full read/write access to your feedback - search, triage, update statuses, merge duplicates, draft changelogs, respond to users.
Self-hosted with Docker (Bun, TanStack Start, PostgreSQL, Dragonfly, MinIO). Auto-runs migrations on startup:
git clone https://github.com/QuackbackIO/quackback.git cd quackback && bun run setup && bun run dev
Interested in feedback on the MCP integration especially - embedding product feedback into AI-assisted dev workflows feels like an area worthy of further exploration.