About QuackbackIO/quackback
QuackbackIO/quackback is an MCP server published by QuackbackIO in the Developer Tools category: open source alternative to Canny, UserVoice, Productboard.
The repository has 319 stars and 106 forks, with the last commit 8 hours ago. Recent commit activity is the strongest signal that reported issues will get attention.
Install
git clone https://github.com/QuackbackIO/quackbackThis server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.
Ask AI
Ask AI about QuackbackIO/quackback
Powered by Claude · Grounded in docs
Security checks
Static checks derived from the repository 7 hours ago. Heuristics on the source, not an audit.
- ✓README presentThe repository ships documentation.
- ✓License declaredUsable under a stated license.
- ✓Tests presentA test suite exists in the repository.
- ✓Dependencies pinnedA lockfile pins dependency versions.
- !No dynamic code executionSource scan found eval or shell execution. Review how tool inputs reach it before granting credentials.
- !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.
Releases
README
Why Quackback
- One loop, from request to release. Customers post and vote, you plan on a public roadmap, and when it ships, everyone who asked hears about it.
- Support that knows what customers asked for. Live chat, email and tickets share an inbox with your feedback, so a conversation can become a vote on a request.
- Yours to run. AGPL-licensed, with every feature when you self-host. Quackback Cloud runs the same code.
- Ready for AI. An agent answers customers, Copilot works beside your team, and an MCP server lets your own AI tools work on feedback and tickets.
What's inside
| Product | What it does |
|---|---|
| Feedback boards | Customers post ideas, vote and comment. Similar ideas appear as they type, and duplicates merge with their votes. Statuses, tags, segments, moderation and private boards. |
| Roadmap | Show what's planned, in progress and complete. Link requests to Linear, GitHub, Jira and other trackers. Linear and GitHub move the request as the issue moves; other trackers send each change for your approval. |
| Changelog | Publish updates and link the requests they ship, so every voter hears about it. Schedule entries, and reach subscribers by email and RSS. |
| Support inbox | Live chat, email and tickets in one shared inbox, with assignment, snoozing, macros, SLAs, office hours and workflows. |
| Help center | A searchable knowledge base on your own domain and inside the widget. |
| Status page | Components, incidents and maintenance windows, with email updates for subscribers. |
| Widget | One embeddable widget for feedback, chat, help articles and your changelog. Works on the web, with SDKs for iOS and Android. |
| Quackback AI | An agent that answers customers from your help center, changelog and status page, and hands off to your team when a person should step in. Copilot answers your team's questions and drafts replies; on Home (in Labs) it can propose settings changes you review and apply. Also duplicate detection, summaries and translation. |
| Developers | A REST API with an OpenAPI spec, signed webhooks, and an MCP server for AI agents. |
The portal and widget speak 10+ languages, including right-to-left, and follow each visitor's browser language.
Get started
Quackback Cloud
Start free. We host, scale, back up and update it for you. The Free plan needs no card, and every paid plan starts with a 14-day trial. See pricing.
Self-host
Every feature, unlimited seats, no license key. You run the servers, backups and upgrades, and bring your own email and AI providers.
Or run the published image with Docker Compose. It starts Quackback, PostgreSQL and S3-compatible file storage on one host:
git clone https://github.com/QuackbackIO/quackback.git
cd quackback
cp .env.prod.example .env # fill in every value
docker compose -f docker-compose.prod.yml up -d
Migrations run on startup. To upgrade, back up your database and files, then:
git pull
docker compose -f docker-compose.prod.yml pull
docker compose -f docker-compose.prod.yml up -d
- Self-hosting guide: images, reverse proxy, scaling, upgrades and troubleshooting
- Configuration reference: every environment variable
- System requirements and the Docker guide in our docs
Self-hosted installs send one anonymous usage snapshot a day: version, setup and banded counts, never content or anything identifying. telemetry.md lists every field, and DISABLE_TELEMETRY=true turns it off.
Connect your AI tools
Every instance serves an MCP server at /api/mcp, so agents like Claude and Cursor can search, triage and act on feedback, tickets, the changelog and help articles. Sign in with OAuth from your client:
claude mcp add --transport http quackback https://feedback.yourcompany.com/api/mcp
Setup for other clients is in the MCP docs.
Integrations
| Kind | Tools |
|---|---|
| Issue trackers | Linear, GitHub, GitLab, Jira, Azure DevOps, Asana, ClickUp, Shortcut, Trello, Monday.com, Notion |
| Chat and alerts | Slack, Microsoft Teams, Discord, ntfy |
| Support and CRM | Zendesk, Intercom, Freshdesk, HubSpot, Salesforce, Stripe |
| Automation | Zapier, Make, n8n, Segment, webhooks |
Each has a setup guide in the docs.
The cloud code in this repo
Quackback Cloud runs this codebase, so its client side lives here: a default-off cloud settings block, plan and entitlement checks, and a control-plane client. On a self-hosted install none of it activates. An install with no cloud configuration is entitled to every feature, shows no upgrade prompts and makes no requests to our control plane. There's nothing to opt out of. We say so here so you never have to discover it in the code.
Contributing
Start with the Contributing Guide, ask questions in Discussions, and see what's being asked for on our own board.
Local development
You need Bun 1.4 or later and Docker.
git clone https://github.com/QuackbackIO/quackback.git
cd quackback
bun run setup # install dependencies, start Postgres, file storage and Mailpit, run migrations
bun run db:seed # optional: demo data
bun run dev # http://localhost:3000
With the demo data, sign in as demo@example.com with the password password.
Built with
TanStack Start and TanStack Router, PostgreSQL with Drizzle ORM (also the background job queue), Better Auth, Tailwind CSS with shadcn/ui, and Bun.
License
AGPL-3.0. Self-hosting is free and complete. If you run a modified version as a service or distribute it, publish your changes under the AGPL. Contributions need a signed CLA.
README fetched from the repository 7 hours ago. The original is authoritative.