← Back to directory
Q

Quackback

Community
Open-source feedback platform. AI agents can search, triage, comment, vote, and manage changelogs.
GitHub source repository ↗
★ 242 Stars Category · Collaboration Popular Source revision 0204d1e6afc4
39FMRS · D
Reliability
8/20
Security and permissions
4/20
Maintenance
10/20
Documentation
8/20
Setup experience
9/20

The Quackback MCP server is a feature-rich toolset for teams with a Quackback instance. It provides 15 tools covering comprehensive management of feedback posts, comments, changelogs, and roadmaps. While official status is not explicitly stated, it is part of the Quackback project and is open-source licensed. Installation requires a self-hosted or cloud instance, and configuration is straightforward. Risks mainly involve data access permissions and potential misoperations, but overall it is powerful, especially for teams looking to automate feedback workflows with AI agents.

Read the FMRS scoring method →

Quackback is an open-source customer feedback collection and management platform, positioned as an alternative to Canny, UserVoice, and Productboard. This MCP server allows AI agents to directly interact with a Quackback instance, performing actions such as searching feedback, triaging posts, voting, commenting, and creating/managing changelogs. It supports self-hosting and offers 24 integrations (Slack, Linear, Jira, etc.).

Tools

search
Search feedback posts or changelog entries with filtering and pagination.
get_details
Get full details for any entity by TypeID (post, changelog).
triage_post
Update a post: set status, tags, and/or owner.
vote_post
Toggle vote on a feedback post.
add_comment
Post a comment on a feedback post, with threaded reply support.
create_post
Submit new feedback on a board.
create_changelog
Create a changelog entry (draft or published).
update_changelog
Update title, content, publish state, and linked posts on a changelog.
delete_changelog
Soft-delete a changelog entry.
update_comment
Edit a comment's content.
delete_comment
Hard-delete a comment and its replies.
react_to_comment
Add or remove an emoji reaction on a comment.
manage_roadmap_post
Add or remove a post from a roadmap.
merge_post
Merge a duplicate post into a canonical post.
unmerge_post
Restore a merged post to independent state.

Setup

After configuring your Quackback instance, set the MCP server URL to https://{host}/api/mcp, where {host} is your Quackback instance's hostname (e.g., feedback.yourcompany.com). In your MCP client (e.g., Claude Desktop), add this URL to the mcpServers configuration.

claude_desktop_config.json
{
  "mcpServers": {
    "quackback": {
      "url": "https://feedback.yourcompany.com/api/mcp"
    }
  }
}

Fit and risk

Best for

  • Teams using Quackback (self-hosted or cloud) who want AI agents to automate feedback management
  • Developers integrating feedback data with other tools like Jira or Slack
  • Customer support teams needing AI-assisted duplicate detection and theme summarization

Not for

  • Users without a deployed Quackback instance
  • Scenarios requiring non-HTTP transport (e.g., stdio or SSE)
  • Those seeking a full replacement rather than an integration with existing tools

Required permissions

  • Read feedback posts, changelog entries, and comments
  • Create and edit feedback posts, changelogs, and comments
  • Manage post status, tags, owner, roadmap assignment, and merging
  • Add/remove comment reactions and votes

Risks and side effects

  • Sensitive customer feedback may be exposed if the instance uses weak authentication or is publicly accessible
  • Modifying post statuses or content may affect workflows, so use caution
  • Merging operations are irreversible (though unmerge_post exists, it may affect related data)
  • Self-hosted instances require maintenance and updates, otherwise security vulnerabilities may arise

Troubleshooting

  1. Check that the `host` variable correctly points to your Quackback instance
  2. Ensure the instance is publicly accessible or network-reachable
  3. Verify API authentication credentials are valid; the MCP server may require the same authentication as the instance
  4. Check server logs for error messages and ensure the MCP server is properly deployed and running

Use cases

AI agents automatically triage and organize customer feedback
Extract feedback from chat or email and create posts
Automatically update roadmaps and changelogs based on feedback
Manage duplicate feedback to keep the list clean
Reply to user comments on feedback posts with real-time updates

Supported clients

Claude DesktopFull support