FetchLayer fetchlayer.dev Get started

+ Integration Guide

· Updated August 29, 2026

How to Connect Reddit MCP to KiloCode

Add FetchLayer's Reddit MCP server to KiloCode so your AI assistant can search Reddit, scrape posts, and pull subreddit data from inside VS Code.

Written by Alex P.

  • MCP
  • KiloCode
  • reddit scraping
  • AI agent
  • VS Code extension

KiloCode is an AI coding assistant that runs as a VS Code extension and supports the Model Context Protocol (MCP). It reads its own MCP settings independently of VS Code’s native .vscode/mcp.json used by GitHub Copilot — the two are separate systems even though they live in the same editor — so if you’ve already set up MCP for Copilot in the same workspace, you still need this guide’s steps for KiloCode to see FetchLayer too.

Connect FetchLayer’s Reddit MCP server and KiloCode’s agent gets access to all 13 Reddit tools directly inside your coding sessions.

Prerequisites

Setup

KiloCode reads MCP server configurations from its own settings. You can configure it through the VS Code settings UI or by editing your settings JSON.

Option 1: Via KiloCode settings

  1. Open VS Code Settings (Ctrl+,)
  2. Search for “KiloCode MCP”
  3. Add a new MCP server with:
    • Name: fetchlayer
    • URL: https://mcp.fetchlayer.dev
    • Headers: Authorization: Bearer ss-your-api-key

Option 2: Via MCP config file

Create or edit .vscode/mcp.json in your workspace:

{
  "servers": {
    "fetchlayer": {
      "url": "https://mcp.fetchlayer.dev",
      "headers": {
        "Authorization": "Bearer ss-your-api-key"
      }
    }
  }
}

Replace ss-your-api-key with your key from the FetchLayer dashboard.

Reload VS Code after saving (Ctrl+Shift+P → “Reload Window”).

Approving tool calls

Like other assistants in this lineage, KiloCode asks before running a tool the first time you use it in a session — you’ll see a prompt to allow the fetchlayer call once, or to auto-approve it for the rest of the session. If you’re running a longer research task and don’t want to click through a dozen approvals, check KiloCode’s auto-approve settings for MCP tools before you start — it’s a per-server toggle, not global, so approving fetchlayer doesn’t silently approve every other MCP server you’ve connected.

Which mode to use

KiloCode’s mode system (Architect / Code / Ask / Debug, depending on your version) affects how it plans work, but MCP tools are available across all of them — you don’t need to be in a specific mode to call FetchLayer. In practice, Ask mode is the fastest way to test a connection since it skips code-editing intent entirely, while Architect mode is where Reddit research tends to be most useful — pulling real user complaints or feature requests before you commit to a design.

Try it out

Open KiloCode’s chat panel and try:

Search Reddit for “best VS Code themes 2026” and show me the top results.

KiloCode will call FetchLayer’s Reddit search tool and return structured data.

More examples:

  • “What do people on r/node recommend for ORMs?”
  • “Get the latest posts from r/reactjs about Server Components”
  • “Find subreddits related to indie hacking”
  • “Before we build this feature, check r/webdev for existing complaints about the approach we’re about to take”

That last pattern — checking Reddit before writing code, not just for marketing copy — is where MCP access earns its keep in an editor like KiloCode: the agent can ground a technical decision in what real developers have already hit, instead of relying only on training data that may be stale.

Available tools

All 13 FetchLayer Reddit endpoints: scrape_search, scrape_post, scrape_community_posts, scrape_community_details, scrape_user_profile, scrape_user_posts, scrape_user_comments, scrape_search_communities, scrape_search_users, scrape_comment_permalink, scrape_popular, scrape_leaderboard, and scrape_explore. See the full endpoint list.

What a tool call actually returns

Reddit tools return structured JSON, not a page you have to parse. A scrape_search call for something like “self-hosted url shortener” returns an array of post objects shaped roughly like this:

{
  "results": [
    {
      "id": "1abc23",
      "subreddit": "selfhosted",
      "title": "What is your favorite self-hosted URL shortener?",
      "author": "u/example_user",
      "score": 214,
      "num_comments": 87,
      "created_utc": 1735689600,
      "url": "https://reddit.com/r/selfhosted/comments/1abc23/...",
      "selftext": "Looking for something lightweight that supports custom domains..."
    }
  ]
}

That structure is why an agent can reliably sort by score, filter by subreddit, or pull num_comments to decide whether a thread is worth a follow-up scrape_post call — none of which is reliable when an agent is scraping rendered HTML itself, where class names and layout change without warning.

A worked example across modes

Because KiloCode separates modes, the same research task splits naturally across two of them — and that split also keeps the request count down.

In a research/ask-style mode, gather:

“Search Reddit for what people say about migrating from Express to Fastify. Open the two threads with the most comments and summarize the migration problems people actually hit.”

That’s one scrape_search and two scrape_post calls — three billed requests — producing a summary grounded in real threads.

Then switch to a code mode and act on it:

“Using those migration problems, write a checklist in MIGRATION.md covering each one, with the thread URL as a reference.”

Zero additional requests. The findings are already in context; this step only writes files.

Keeping gathering and editing in separate modes isn’t just tidiness — a code-focused mode asked to research will often interleave fetches with edits, and interleaved runs tend to fetch more than they need because the agent hits a gap mid-edit and reaches for the tool instead of reasoning from what it has.

Mode permissions and tool access

Modes differ in what they’re allowed to do, and MCP tool access follows those permissions. If a mode is restricted from tool use, the agent will answer from the model instead of calling Reddit — and it usually won’t announce that it did so.

The symptom is an answer that arrives instantly and reads plausibly but cites nothing current. If you asked about recent discussion and got no tool-call block in the transcript, the mode is the first thing to check, before the server config.

Controlling cost in auto-approve mode

Auto-approving tool calls makes multi-step research much smoother, and it removes the last checkpoint before a billed request. Two guardrails worth keeping:

Bound the run in the prompt. “Open no more than three threads” is a limit the agent will respect; “research this properly” is not.

Keep auto-approve off for exploratory prompts. When you don’t yet know how many threads a question needs, manual approval is a cheap way to find out. Turn it on once the shape of the task is predictable.

Each scrape_search is one request no matter how many results return; each scrape_post is one per page of comments. Searching broadly and opening selectively is nearly always cheaper than the reverse.

Troubleshooting

Server not appearing in KiloCode?

  • Confirm you used KiloCode’s own MCP settings (Option 1 or 2 above), not VS Code Copilot’s separate .vscode/mcp.json config — they don’t share configuration even in the same workspace
  • Make sure any JSON you edited by hand is valid (no trailing commas)
  • Reload the window completely rather than just closing the KiloCode panel

Getting 401 errors?

  • Verify your API key is correct and starts with ss-
  • Make sure the Authorization header includes the Bearer prefix exactly as shown

Every tool call asks for approval and it’s slowing you down?

  • Check KiloCode’s auto-approve settings for the fetchlayer MCP server specifically — this is a per-server setting, not a blanket “trust everything” switch

Using more than one platform in the same session

The fetchlayer MCP server you just connected is Reddit-specific, but the same account and API key work across FetchLayer’s other platform servers too — Twitter/X, App Store reviews, YouTube comments, Google Maps, and Google Play Store. If your workflow needs more than Reddit (comparing what people say on Reddit vs. X about the same topic, for example), you can add the Twitter MCP server alongside this one with the same API key and a different server URL. Nothing about the setup above changes — it’s the same config shape, just a second entry in your mcpServers block.

What’s Next