Reddit Scraper for Claude Code: What Claude Actually Calls

Claude Code can search Reddit. It just never touches reddit.com to do it — every direct path returns 403, including stealth browsers, and we tested all of them. This post assumes you accept that and want to know what actually happens in your terminal.

Setup is one line — Claude Code's own MCP documentation covers the three install scopes. If the server does not show up afterwards, that is a different problem with a longer answer:

claude mcp add crawlforge \
  --env CRAWLFORGE_API_KEY=cf_live_your_key_here \
  -- npx -y crawlforge-mcp-server

What happens when you ask Claude Code to search Reddit?

You describe an outcome, not a tool:

What are people in r/LocalLLaMA complaining about with long context this month? Read the top thread in full.

Claude makes two calls. The first is scoped, so it goes straight to the archive:

{
  "tool": "reddit_search",
  "arguments": {
    "query": "long context",
    "subreddit": "LocalLLaMA",
    "mode": "posts",
    "after": "30d",
    "limit": 25
  }
}

The second takes an id from those results and reads the discussion:

{
  "tool": "reddit_search",
  "arguments": {
    "mode": "thread",
    "link_id": "1vbf4nh",
    "limit": 100
  }
}

Two calls, 10 credits, no Reddit credentials anywhere. What comes back is normalized archive rows, so Claude can hand them to summarize_content without a parsing step in between — the full parameter list is in the API reference.

Why does a Reddit-wide search cost a web search?

Drop the subreddit and the request changes mechanism, not just scope. This is the part that catches people out.

Arctic Shift cannot keyword-search across all of Reddit — its API requires a subreddit, author or post scope. PullPush could, until it stopped serving automated clients in August 2026. So an unscoped query takes a two-step route: a site-restricted web search finds the matching posts, then those post IDs are read out of the archive.

What comes back is still real archive rows, not search-engine snippets. But three things change, and all three are stated in the response's own notes array:

• Results are ordered by web-search relevance, not by score or date.
• Discovery caps at 10 posts per call, whatever limit you asked for.
• after and before are not applied. The response says so explicitly rather than returning unfiltered results.

That last one matters most in an agent loop. Claude will happily pass after: "7d" on an unscoped search, and the filter is dropped — the note is the only thing that tells either of you the window was ignored.

When should you override Claude's choice?

Rarely, with two exceptions worth learning.

Name a subreddit whenever you can. It is the difference between a 10-post relevance sample and a real archive query with working date filters. "Search Reddit for X" and "search r/webscraping for X" are different operations, not two phrasings of one.

Say "search comments" when you want opinions. mode: "comments" searches comment bodies rather than post titles and selftext, and Claude tends to default to posts. The candid material is usually three replies deep.

What does this cost inside an agent loop?

5 credits per call, whichever route answers — so the free tier's one-time 1,000 credits are 200 searches. A thread read costs the same 5 whether the thread holds 12 comments or 400, which makes "search, then read the top three threads" a predictable 20 credits instead of something that scales with how busy the discussion got.

The accuracy limit to design around: scores and comment counts on content younger than about 36 hours can read 0 or 1. The archive captures a post the moment it appears and does not re-poll it as votes arrive. Sentiment questions are fine. "Top-voted today" is not.