<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Forem: James Morton</title>
    <description>The latest articles on Forem by James Morton (@mortondev).</description>
    <link>https://forem.com/mortondev</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3777611%2Fc7f951df-c725-4b78-b12a-bf7137be649c.jpeg</url>
      <title>Forem: James Morton</title>
      <link>https://forem.com/mortondev</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://forem.com/feed/mortondev"/>
    <language>en</language>
    <item>
      <title>Introducing Quackback: Open-Source Feedback Platform with a Built-in MCP Server</title>
      <dc:creator>James Morton</dc:creator>
      <pubDate>Tue, 17 Feb 2026 12:40:18 +0000</pubDate>
      <link>https://forem.com/mortondev/introducing-quackback-open-source-feedback-platform-with-a-built-in-mcp-server-mo3</link>
      <guid>https://forem.com/mortondev/introducing-quackback-open-source-feedback-platform-with-a-built-in-mcp-server-mo3</guid>
      <description>&lt;p&gt;Quackback is an open-source feedback platform. Voting boards, a public roadmap, changelogs, and 23 integrations. The same workflow that tools like Canny and UserVoice established, but open source and with a built-in MCP server.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why feedback tools need an open-source option
&lt;/h2&gt;

&lt;p&gt;UserVoice starts at $999 per quarter. Canny has a free tier, but meaningful features require their paid plans. Productboard charges per seat. These tools got the collection model right. But they're closed-source, expensive at scale, and none of them offer self-hosting.&lt;/p&gt;

&lt;p&gt;Meanwhile, development workflows have changed. AI agents write code, review pull requests, and ship features. But customer feedback is still a manual loop: triaging, responding, updating statuses, notifying voters when something ships. That work doesn't scale for small teams.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://plausible.io" rel="noopener noreferrer"&gt;Plausible&lt;/a&gt; brought open source to web analytics. &lt;a href="https://cal.com" rel="noopener noreferrer"&gt;Cal.com&lt;/a&gt; did it for scheduling. &lt;a href="https://formbricks.com" rel="noopener noreferrer"&gt;Formbricks&lt;/a&gt; did it for surveys. &lt;a href="https://posthog.com" rel="noopener noreferrer"&gt;PostHog&lt;/a&gt; did it for product analytics. Quackback does it for feedback collection.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fxxa1p3pcg1y3otjx40m3.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fxxa1p3pcg1y3otjx40m3.png" alt="Quackback feedback board" width="800" height="474"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Try it locally in under a minute:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;git clone https://github.com/QuackbackIO/quackback.git
&lt;span class="nb"&gt;cd &lt;/span&gt;quackback &lt;span class="o"&gt;&amp;amp;&amp;amp;&lt;/span&gt; bun run setup &lt;span class="o"&gt;&amp;amp;&amp;amp;&lt;/span&gt; bun run dev
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  Agents as part of the feedback loop
&lt;/h2&gt;

&lt;p&gt;Quackback ships with an &lt;a href="https://quackback.io/docs/mcp" rel="noopener noreferrer"&gt;MCP server&lt;/a&gt;. Claude, Cursor, and Windsurf already support the protocol. Connect an agent and it gets read-write access to your feedback data.&lt;/p&gt;

&lt;p&gt;An agent connected to Quackback can:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Search&lt;/strong&gt; across all feedback posts and changelogs&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Triage&lt;/strong&gt; posts: update status, assign owners, add tags, write official responses&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Create&lt;/strong&gt; new posts and changelog entries&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Comment&lt;/strong&gt; and &lt;strong&gt;vote&lt;/strong&gt; on behalf of your team&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Every action is attributed. Every change is auditable. When an agent triages a post, you see which agent did it, when, and what changed.&lt;/p&gt;

&lt;p&gt;In practice, this means a team of three can keep up with a feedback volume that would otherwise require dedicated support staff. Posts that would sit unread for weeks get triaged in hours.&lt;/p&gt;

&lt;h2&gt;
  
  
  Open source. Self-host. Own your data.
&lt;/h2&gt;

&lt;p&gt;Quackback is &lt;a href="https://github.com/QuackbackIO/quackback/blob/main/LICENSE" rel="noopener noreferrer"&gt;AGPL-3.0&lt;/a&gt; licensed. You can read every line, audit every dependency, and run it on your own infrastructure.&lt;/p&gt;

&lt;p&gt;Self-host with Docker or deploy in one click on Railway. Your feedback data stays in your PostgreSQL database. No vendor lock-in. No per-seat pricing.&lt;/p&gt;

&lt;h2&gt;
  
  
  What's included
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;For your users:&lt;/strong&gt; Public feedback boards with voting, status tracking, nested comments, and official responses. A public roadmap. A changelog that notifies voters when their requested features ship.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;For your team:&lt;/strong&gt; Admin inbox with unified triage, filtering, bulk actions, and deduplication. Two-way sync with your issue tracker. SSO and OIDC for enterprise authentication.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;For your stack:&lt;/strong&gt; Slack, Linear, Jira, GitHub, GitLab, Asana, ClickUp, Intercom, Zendesk, HubSpot, Salesforce, Discord, Teams, Zapier, and Make. Full REST API with OpenAPI 3.0 docs. Webhooks with HMAC-SHA256 signing. The MCP server for agents. Custom branding with your logo, colors, and domain.&lt;/p&gt;

&lt;h2&gt;
  
  
  Get involved
&lt;/h2&gt;

&lt;p&gt;Quackback is on GitHub at &lt;a href="https://github.com/QuackbackIO/quackback" rel="noopener noreferrer"&gt;QuackbackIO/quackback&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;I'd especially like feedback on the MCP server. Giving agents access to user feedback is new territory, and the interface is shaped by how people actually use it. Follow the &lt;a href="https://quackback.io/docs/mcp" rel="noopener noreferrer"&gt;MCP setup guide&lt;/a&gt; to connect your agent, then tell me what's missing.&lt;/p&gt;

</description>
      <category>opensource</category>
      <category>selfhosted</category>
      <category>webdev</category>
      <category>productivity</category>
    </item>
  </channel>
</rss>
