Claude Desktop is Anthropic’s native desktop app for Claude. It supports the Model Context Protocol (MCP), which lets Claude call external tools — including Reddit data from FetchLayer.

Once configured, you can ask Claude to search Reddit, scrape comment threads, analyze subreddit trends, and more — all inside a normal conversation, with no separate research tab or copy-pasted URLs.


Prerequisites

  • Claude Desktop installed
  • A FetchLayer account — you can create one while connecting (no credit card)

Step 1: Add FetchLayer as a custom connector

Remote MCP servers are added to Claude as custom connectors, not through the config file. Open Customize → Connectors in Claude (claude.ai/customize/connectors — Claude Desktop shows the same list under Settings), choose Add custom connector, and fill in:

  • Name: fetchlayer
  • Remote MCP server URL: https://mcp.fetchlayer.dev

Click Add. A connector added here works in Claude Desktop, on claude.ai and in the mobile apps. Free plans allow one custom connector; paid plans have no such limit.


Step 2: Sign in

Click Connect next to fetchlayer. A FetchLayer page opens in your browser: sign in (a new account comes with free requests, no card) and click Approve. Claude stores the connection itself, so there is no API key to copy or paste.


Step 3: Turn it on in a chat

Start a new conversation, open the tools menu in the message box, and check that fetchlayer is switched on. Its Reddit tools are then available to Claude in that chat.

Why not claude_desktop_config.json? That file only starts local (stdio) servers. An entry with a url is skipped without an error, so the tools never appear. If you need the file — say, to manage every server in one place — run FetchLayer through the mcp-remote bridge instead:

{
  "mcpServers": {
    "fetchlayer": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.fetchlayer.dev", "--header", "Authorization:${FETCHLAYER_AUTH}"],
      "env": { "FETCHLAYER_AUTH": "Bearer ss-your-fetchlayer-key" }
    }
  }
}

Replace ss-your-fetchlayer-key with a key from the FetchLayer dashboard, then quit Claude Desktop completely and reopen it. Keeping the key in env avoids the space in Bearer …, which some platforms split into two arguments.


Step 4: Try it out

Start a new conversation and try:

Search Reddit for posts about “best project management tools” from the last month. Show me the top 5 by score with their subreddits.

Claude will call the FetchLayer search tool and return structured results.

More ideas:

PromptWhat Claude does
“What’s trending on r/programming right now?”Fetches hot posts from r/programming
“Summarize the top comments on this Reddit post: [URL]”Scrapes comments, then summarizes
“Find subreddits about indie game development”Searches communities by keyword
“What’s the sentiment on r/startups about bootstrapping vs VC?”Searches, reads comments, analyzes tone
“Get me u/spez’s Reddit profile”Returns user profile data

Because Claude can chain tool calls with reasoning, it can do multi-step analysis — search for posts, scrape the comments, and synthesize findings in one conversation turn.


What the approval flow looks like

The first time a conversation calls the fetchlayer tool, Claude Desktop shows a confirmation dialog with the exact request before it runs — you can allow it once, or choose “always allow for this chat” so you’re not re-approving every call in a long research session. This is per-conversation, not a global setting, so a fresh chat will ask again the first time it uses the tool. If you want to inspect exactly what was sent and returned, expand the tool-call block in the conversation — Claude Desktop shows the raw request and response, which is the fastest way to debug a result that looks wrong.


Available Tools

Claude Desktop gets access to all FetchLayer Reddit tools:

  • scrape_search — Search posts by keyword
  • scrape_post — Get a full post with comments
  • scrape_community_posts — Browse subreddit posts
  • scrape_community_details — Get subreddit metadata
  • scrape_user_profile — User karma, bio, account age
  • scrape_user_posts — A user’s post history
  • scrape_user_comments — A user’s comment history
  • scrape_search_communities — Find subreddits by keyword
  • scrape_search_users — Find users by name
  • scrape_comment_permalink — Get a specific comment with context
  • scrape_popular — Trending posts from r/popular
  • scrape_leaderboard — Trending communities
  • scrape_explore — Discover communities by topic

What a tool call actually returns

Claude receives structured JSON rather than a web page, which is what makes follow-up questions cheap. A scrape_search result looks roughly like:

{
  "items": [
    {
      "id": "1abc23",
      "subreddit": "ProductManagement",
      "title": "How do you handle feature requests from sales?",
      "author": "u/example_user",
      "score": 312,
      "num_comments": 145,
      "created_utc": 1735689600,
      "url": "https://reddit.com/r/ProductManagement/comments/1abc23/...",
      "previewText": "Our sales team forwards every customer ask directly to..."
    }
  ]
}

Because score and num_comments come back with every result, Claude can reason about which threads matter before opening any of them — and each additional question you ask about data already in the conversation costs nothing further.


A research session, end to end

Claude Desktop is a chat window rather than an editor, which makes it best suited to open-ended research where you don’t know the shape of the answer yet. A session might run:

You: “What are people in r/ProductManagement saying about AI note-takers in meetings?”

Claude calls scrape_search — one request — and summarizes what came back.

You: “Which of those threads has the most disagreement?”

No new request. Claude compares num_comments against score across results it already has; a high comment count on a modest score usually means an argument.

You: “Open that one and tell me both sides.”

One scrape_post call — a second request — returning the full comment tree.

You: “Now write that up as a one-page brief for our product team.”

No request. Claude is working entirely from what’s already in context.

Four exchanges, two billed requests. The pattern worth internalizing: new data costs, re-reasoning doesn’t. Front-load the fetching, then interrogate what you have.


Where the conversation limit bites

Reddit threads are large. A scrape_post on a 500-comment thread returns a lot of text, and two or three of those will fill a conversation’s context.

Practical habits that help:

  • Ask for a summary of each thread as you go, so the useful conclusions survive even after the raw data falls out of context
  • Start a new conversation for each research question rather than accumulating one long session
  • Use scrape_search first and scrape_post selectively — fetching every thread “to be thorough” is what fills context fastest, and usually adds nothing

If Claude starts giving vaguer answers partway through a long session, that’s context pressure, not the tool failing.


Troubleshooting

fetchlayer not in the tools menu?

  • Check it is listed under Customize → Connectors and shows as connected; if it asks you to connect, click Connect and approve again
  • Start a new conversation — tools are not added to chats that were already open
  • If you put a url entry in claude_desktop_config.json, that is the cause: the file only takes local servers. Use the connector above, or the mcp-remote entry

Claude says it can’t access Reddit?

  • Check that the connection’s key has not been revoked in the dashboard; if it has, click Connect again
  • Make sure you’re in a new conversation — MCP tools aren’t retroactively available in old chats started before the config change

Getting errors in tool calls?

  • Expand the tool call in Claude’s response to see the raw error message
  • Most common: a revoked key or an account out of requests — the error text says which

What’s Next