Enables browsing subreddits (hot, new, top, rising, controversial), searching posts globally or within a subreddit, and reading comments on posts via Reddit's RSS feeds, without requiring API keys or authentication.
Provides access to Reddit's RSS feeds, allowing retrieval of subreddit posts, search results, and comments in Atom XML format, parsed without external dependencies.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@reddit-rss-mcp show me the hot posts in r/selfhosted"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
A tiny, dependency-free MCP server that reads Reddit through its still-open RSS feeds. No API key, no OAuth, no scraping service.
As of 2025–2026, Reddit blocks anonymous access to its JSON API at the network-security layer. A plain request to www.reddit.com/r/.../hot.json returns a 403 "blocked by network security" page — and this happens from residential IPs, VPNs, and even commercial residential-proxy scrapers. Self-service API key creation also ended (Responsible Builder Policy, pre-approval now required).
But Reddit's RSS feeds and search RSS still return 200. This server uses only those, so it works with zero credentials, even from a blocked IP.
Related MCP server: reddit-mcp
Tool | What it does |
| Search posts (globally or within one subreddit). |
| Fetch a subreddit's posts (hot/new/top/rising/controversial). |
| Read the user comments on a post (flat list). |
Each returns clean JSON: title, author, link, subreddit, date, and a text excerpt.
Requires Node.js 18+ (uses the built-in fetch). No npm install needed.
Add to your MCP config (claude_desktop_config.json, or ~/.claude/settings.json for Claude Code).
Run directly from GitHub (no install step):
{
"mcpServers": {
"reddit-rss": {
"command": "npx",
"args": ["-y", "github:ninjackster/reddit-rss-mcp"]
}
}
}Or run from a local clone:
{
"mcpServers": {
"reddit-rss": {
"command": "node",
"args": ["/absolute/path/to/reddit-rss-mcp/server.js"]
}
}
}Restart the app (quit fully, then relaunch) to load the server.
Search r/technology for "local LLM" sorted by new.
Show me the hot posts in r/selfhosted.
Read the comments on this post: https://www.reddit.com/r/technology/comments/abc123/title/
Comments are flat — no parent/child threading.
No scores — RSS carries no upvote/downvote counts.
~25 results per call — RSS feed cap.
For nested comment trees, scores, and unlimited depth you need Reddit's authenticated API (an approved OAuth app). This server is the no-credentials option that covers search, browse, and comment reading.
It maps tool calls to Reddit RSS endpoints:
Browse: https://www.reddit.com/r/<sub>/<sort>.rss
Search: https://www.reddit.com/search.rss?q=<q> (add restrict_sr=1 for a single subreddit via /r/<sub>/search.rss)
Comments: <post-permalink>.rss
It parses the Atom XML with no external dependencies and speaks MCP over stdio (JSON-RPC 2.0).
MIT
Fetch posts from a subreddit via RSS (no API key). Returns title, author, link, date, excerpt. ~25 results max. No scores or comment trees (RSS limitation). Use "all" or "popular" for cross-Reddit feeds.
| Name | Required | Description | Default |
|---|---|---|---|
| subreddit | Yes | Subreddit name without r/ (e.g. "technology", "all") | |
| sort | No | hot | |
| time | No | Time window (for top/controversial) | |
| limit | No | Max results (1-25, default 25) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses key behaviors: uses RSS (no API key), returns specific fields, max 25 results, no scores/comment trees. This is transparent given no annotations exist. Could mention potential rate limits or error handling, but sufficient for simple use.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise (4 sentences), front-loaded with the main purpose, then output details, limitation, and a tip. Every sentence adds value without redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no output schema and 4 parameters, the description covers purpose, output fields, limitation, and provides a usage tip. It lacks error handling or rate limit info, but is complete enough for a simple RSS-based tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 75% (3/4 params documented). The description adds context beyond schema: no API key, RSS, returned fields, max results, limitation, and the 'all'/'popular' hint. This enhances understanding of parameters like subreddit and limit.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool fetches posts from a subreddit via RSS, lists the returned fields, and mentions the limitation of no scores/comment trees. It distinguishes from siblings by specifying it's for browsing subreddits and that 'all' or 'popular' can be used for cross-Reddit feeds.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides clear context on when to use the tool (fetching posts via RSS, no API key) and gives a tip for cross-Reddit feeds. However, it does not explicitly state when not to use it or offer alternatives like search_reddit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Read the user comments on a Reddit post via RSS (no API key). Pass the post URL/permalink. Returns the post plus a FLAT list of comments (author + text). Limitations: not threaded (no parent/child nesting), no upvote scores, ~25 comments max. For full nested trees + scores, use OAuth.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Reddit post URL or permalink (e.g. https://www.reddit.com/r/technology/comments/abc123/title/) | |
| limit | No | Max comments (1-25, default 25) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description fully discloses behavioral traits: it is read-only, uses RSS, returns a flat comment list, has no threading, no upvote scores, and a ~25 comment limit. This gives the agent clear expectations for behavior and limitations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise (two sentences plus a brief limitations list), front-loaded with the primary action, and every sentence adds value—purpose, input, output format, limitations, and alternative tool. No unnecessary words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's low complexity (2 parameters, no output schema), the description covers all necessary aspects: purpose, required input, result format, limitations, and alternative. It is complete for effective agent decision-making.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so the baseline is 3. The description adds marginal value by restating the parameter purposes and mentioning the limit constraint (1-25, default 25) already covered in the schema. No new semantic information beyond the schema is provided.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly specifies the tool's function: reading user comments on a Reddit post via RSS without an API key. It states the required input (post URL/permalink) and distinguishes from sibling tools (browse_subreddit, search_reddit) by focusing on comments for a specific post.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides context on when to use the tool (simple comments without auth) and when not to (if threaded comments or scores are needed, use OAuth). It implicitly differentiates from siblings by focusing on single-post comments. However, it does not explicitly list exclusions or prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Search Reddit posts via RSS (no API key). Optionally restrict to one subreddit. Returns title, author, link, subreddit, date, and a text excerpt. ~25 results max. No comment trees or scores (RSS limitation).
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Search query | |
| subreddit | No | Optional: restrict search to this subreddit (without r/) | |
| sort | No | relevance | |
| time | No | Time window (for top/relevance) | |
| limit | No | Max results (1-25, default 25) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description fully carries behavioral transparency: it discloses RSS usage, no API key needed, return fields, max 25 results, and missing features (comment trees, scores). No mention of rate limits or auth, but adequate for a public RSS feed tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, front-loaded with the core action, each sentence adds distinct information. No redundancy or filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no output schema, the description explicitly lists return fields and notes the max results and RSS limitations. It misses error handling or pagination details, but is reasonably complete for a simple search tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema descriptions cover 4 of 5 parameters (80%). The description adds context for subreddit and limit (max 25), but does not elaborate on query, sort, or time beyond what the schema provides. Adequate but minimal added value.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool searches Reddit posts via RSS, specifies what it returns (title, author, link, etc.), and implicitly distinguishes from siblings by noting RSS limitations and no comment trees/scores.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description mentions optional subreddit restriction and RSS limitations, but does not explicitly compare with 'browse_subreddit' or 'get_post_comments' or provide when-not-to-use guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
v1.0.0browse_subredditget_post_commentssearch_redditEach tool has a distinct purpose: browsing a subreddit, reading comments on a specific post, and searching across Reddit. No overlap in functionality.
All tool names follow a consistent verb_noun pattern in snake_case (browse_subreddit, get_post_comments, search_reddit), making them predictable and clear.
With only 3 tools, the server feels slightly sparse but is appropriate for its RSS-based scope. Each tool covers a core operation, and adding more would require capabilities beyond RSS.
The tool set covers the primary Reddit actions achievable via RSS: viewing posts, searching, and reading comments. Missing features like nested comments or scores are acknowledged as RSS limitations, so the surface is reasonable for its domain.
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
Reddit MCP server: search posts, subreddit feeds, comments & user profiles as JSON. No API key.
Reddit MCP — public Reddit data via JSON endpoints (no auth required)
An MCP server that provides read access to your cloud storage providers, bank accounts and more.
Public MCP server for discovering open jobs. Search, filter, and get application links.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/ninjackster/reddit-rss-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server
