Log inSubmit server
Quackback logo

Quackback

by QuackbackIO

Lets AI agents search, triage, update, and manage customer feedback through Quackback.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Quackback

Pick your client, then add it in one click or paste the config.

No confirmed install command yet

We only publish a config when the install details come from the project itself — its README, its docs, or a verified owner. We haven’t found those for QuackbackIO/quackback, and we’d rather show nothing than a guess you’d paste into your client.

Open setup steps on GitHub

Overview

QuackbackIO/quackback MCP server gives AI agents access to Quackback’s customer feedback workflows. It supports searching feedback, triaging posts, changing statuses, creating and commenting on posts, voting, managing roadmaps, merging duplicates, and publishing changelogs. Reach for it when an agent needs to inspect customer input or carry out feedback-management tasks in a Quackback deployment.

Use cases

  • Search customer feedback for recurring requests
  • Triage incoming feedback posts
  • Update the status of a feature request
  • Merge duplicate feedback posts
  • Publish a product changelog update

Key features

  • Search feedback
  • Triage and update posts
  • Create and comment on posts
  • Vote on feedback
  • Manage roadmaps
  • Merge duplicates and publish changelogs

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

21/22 checks healthy over the last 79d

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars331Stargazers on the source repository.
Last commit6d agoMost recent push to the default branch.
Directory activity5 viewsConfig copies, upvotes, and views on AllMCPs.

How Quackback works

What QuackbackIO/quackback MCP server does

QuackbackIO/quackback MCP server exposes customer feedback operations to AI agents through Quackback. The surrounding platform provides feedback boards, an administrative inbox, roadmaps, changelogs, and customer-facing feedback collection. The MCP capability is intended for agents that need to work with this information rather than only read documentation about it.

Supported operations listed for the server include:

  • Searching feedback
  • Triaging posts
  • Updating post statuses
  • Creating posts and adding comments
  • Voting on posts
  • Managing roadmaps
  • Merging duplicate posts
  • Publishing changelogs

These operations cover both discovery and changes to feedback records. They can support workflows such as finding recurring requests, organizing incoming posts, and communicating shipped product updates.

How it works

QuackbackIO/quackback MCP server is built into the Quackback open-source application. Quackback describes its MCP server as an interface that lets AI agents search, triage, and act on feedback directly. The platform also includes a REST API and outbound webhooks, but those are separate automation interfaces from MCP.

Quackback can be used as a hosted cloud service or self-hosted with Docker or a one-click Railway deployment. Self-hosted installations use PostgreSQL, and the repository says migrations run automatically when the application starts.

Setup and configuration

The repository supports two main deployment paths for Quackback. Cloud users can start at app.quackback.io without managing application infrastructure. For self-hosting, the documented Docker flow clones the repository, copies .env.example to .env, builds the image from apps/web/Dockerfile, and runs it on port 3000. A PostgreSQL database is required, and configuration values are documented in the project’s runtime configuration table.

It also does not list the environment variable names needed specifically by MCP, so an MCP client setup should be based on the project’s current documentation rather than inferred from the general application deployment example.

Limitations and notes

It also does not state whether an external MCP connection requires an API key, OAuth, a session token, or another authentication method.

Quackback is licensed under AGPL-3.0. Self-hosting is described as free and fully functional without limits, while a hosted cloud option is also available.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Quackback

It can search feedback, triage posts, update statuses, create and comment on posts, vote, manage roadmaps, merge duplicates, and publish changelogs.

Related MCP servers

All in Customer Data Platforms All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewQuackback AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/quackbackio-quackback?style=directory)](https://allmcps.com/mcp/quackbackio-quackback)
HTML Embed
<a href="https://allmcps.com/mcp/quackbackio-quackback"><img src="https://allmcps.com/api/badge/quackbackio-quackback?style=directory" alt="Quackback on AllMCPs" /></a>