Back to guides
How to Analyze Reddit Feedback on a Feature Release with Claude
MCPClaude

How to Analyze Reddit Feedback on a Feature Release with Claude

Nicolas More, Reddinbox founder

Nicolas More

Reddinbox Founder

·5 min read

Support tickets and survey forms tell you what customers are willing to tell you. Reddit, X and Hacker News tell you what they say when you are not in the room. After a release, that second source is often the faster signal.

This guide shows how to check it every day with Claude and the Reddinbox MCP server, and turn it into a short report your team can act on.

What you need

  • A Reddinbox account. The free trial covers Reddit and Hacker News. X, Bluesky and Facebook need Starter or Pro.
  • An API key from Settings, API keys.
  • Claude Code, Claude Desktop or Cursor. Claude Code is the easiest for a daily job.

Step 1: Connect Claude to Reddinbox

In Claude Code, run this once and replace the placeholder with your key:

bash
claude mcp add --transport http reddinbox https://reddinbox.com/api/mcp \
  --header "Authorization: Bearer rdb_your_api_key"

Using Claude Desktop or Cursor? Follow the Claude Desktop setup or the Cursor setup.

Type /mcp in Claude Code to confirm Reddinbox is connected. You should see five tools: search_threads, get_thread, summarize_feedback, list_briefs and run_research.

Step 2: Find the threads about your release

Start with a search that names the release and where your users talk:

text
Use reddinbox to search Reddit, X and Hacker News for posts about
[product name] from the last 24 hours. Focus on the new [feature name].
Return the raw posts with links.

search_threads returns posts with title, body, author, engagement and URL. Spam and AI-generated posts are filtered before they reach Claude, so the list is shorter and more useful.

Tips for better searches:

  • Name the feature, not only the product. "Export flow" finds more than "Acme".
  • Add the subreddits you know your users read.
  • Use a short time window for a daily run so you do not re-read old threads.

Step 3: Read the comments, not only the headlines

A thread title rarely holds the feedback. The replies do. Ask Claude to open the biggest threads:

text
For the three threads with the most comments, call get_thread and read the
comment trees. List every complaint, bug report and feature request.

get_thread returns the post with its nested comments for Reddit and Hacker News. For X, Bluesky and Facebook, work from the posts that search_threads returns.

Step 4: Sort the feedback

Ask for a structure your team already uses:

text
Group the feedback into: bugs, usability problems, missing features, pricing,
and praise. For each group, give a count, two direct quotes and the source link.
Flag anything that looks like a regression from the last release.

Asking for quotes and links keeps the report honest. Your team can click through and check the original thread.

If you want a faster pass, summarize_feedback runs the search and summary in one call and returns themes with their sources.

Step 5: Post it where your team works

Add a last line to the prompt:

text
Write the result as a short Slack-ready message: three bullet points on what
changed since yesterday, then the top issue with its link.

If Slack is connected to Claude, it can post for you. If not, copy the message by hand.

Step 6: Run it every day

With Claude Code you can run the prompt non-interactively and schedule it. Save the prompt in a file, then call it from cron or your CI each morning.

Keep three things in mind:

  1. Budget. Calls use the same monthly token budget as the Reddinbox app. Searching three platforms and reading a few big threads costs more than a single search.
  2. Rate limit. Each key allows 30 calls per minute. A daily job rarely comes close.
  3. Keep the key secret. Store it as a secret in your CI. Revoke it from Settings if it leaks.

Add what customers tell you directly

Public feedback is one half. If you also export Zendesk tickets or form responses, paste them in or connect those tools to Claude, and ask:

text
Compare these support tickets with the Reddit and X feedback. Which issues
appear in both? Which appear only in public?

Issues that show up in public and not in tickets are the ones customers are not reporting to you. Those are the most useful to find.

A starter prompt to copy

text
You are checking public feedback on our latest release.
1. Use reddinbox to search Reddit, X and Hacker News for [product] and
   [feature] from the last 24 hours.
2. Read the comment trees of the three most-discussed threads.
3. Group feedback into bugs, usability, missing features, pricing and praise,
   with counts, two quotes per group and source links.
4. Finish with a three-bullet summary for Slack and the single most urgent issue.

Ready to try it? Get your API key and connect Claude in a few minutes. For the full tool list, see the Reddinbox MCP overview. If you came here looking for a way around Reddit's API limits, read Reddit API alternatives for AI agents.

Join 500+ practitioners already using Reddinbox

Stop Guessing What Your Audience Wants

Start your free trial today and discover real insights from millions of conversations. No credit card required.

No credit card required
Full access to all features
Cancel anytime