Quackback

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. The supplied material does not specify a separate MCP endpoint, transport configuration, client configuration block, or per-tool permission model for external MCP clients.

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.

The README does not provide a standalone package command for launching only the MCP server. 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

The available material identifies the MCP-supported actions but does not document their exact tool names, argument schemas, return formats, or compatibility with specific MCP clients. 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. The platform includes broader integrations such as Slack, Linear, Jira, GitHub, Intercom, and Zendesk, but the provided material does not establish that every integration is directly exposed through MCP.