The MCP Reddit server enables fetching and analyzing Reddit content, specifically posts and comments.
Fetch hot threads: Retrieve popular threads from any subreddit with customizable limits
Get detailed post content: Access specific posts with their comments, controlling both the number of comments and the depth of the comment tree
Analyze subreddit activity: View trending discussions and key highlights
Support for different post types: Handle text, link, and gallery posts seamlessly
Allows fetching hot threads from subreddits, getting detailed post content including comments, and supporting different post types (text, link, gallery)
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., "@mcp-reddit show me the top posts in r/technology"
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 Model Context Protocol (MCP) server that provides tools for fetching and analyzing Reddit content.
Fetch hot threads from any subreddit
Get detailed post content including comments
Support for different post types (text, link, gallery)
Related MCP server: Reddit MCP Server
To install Reddit Content for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install @adhikasp/mcp-reddit --client claude{
"reddit": {
"command": "uvx",
"args": ["--from", "git+https://github.com/adhikasp/mcp-reddit.git", "mcp-reddit"],
"env": {}
}
}Using mcp-client-cli:
$ llm what are latest hot thread in r/victoria3
I'll fetch the latest hot threads from the Victoria 3 subreddit for you.
Tool Calls:
fetch_hot_threads
Args:
subreddit: victoria3
Based on the hot threads, here are the key highlights from the Victoria 3 subreddit:
1. Dev Diary #126 - Update 1.8 Overview
- Major updates planned for the game, including:
- Political Movement Rework (Ideological Forces)
- Discrimination Rework
- Food Availability, Famines, and Harvest Incidents
- Additional features like Companies owning buildings and Bulk Nationalization
2. Dev Diary #138 - Pivot of Empire Update
- Update 1.8 "Masala Chai" has been released
- Focuses on India with new Journal Entries, Events, and Immersion Pack
- 10 new achievements added
- Save games from 1.7.7 are not compatible with 1.8
3. Interesting Community Discussions:
- A player shared a detailed experience of retaking Constantinople as Greece, highlighting the complex population dynamics
- Humorous posts about game mechanics, such as investment rights and political movements
- Various memes and gameplay screenshots showcasing unique game situations
The most upvoted thread is the Dev Diary #126, which provides an in-depth look at the upcoming game mechanics improvements, particularly the reworks to political movements and discrimination systems.
Would you like me to elaborate on any of these points or provide more details about the Victoria 3 update?Fetch hot threads from a subreddit
Args: subreddit: Name of the subreddit limit: Number of posts to fetch (default: 10)
Returns: Human readable string containing list of post information
| Name | Required | Description | Default |
|---|---|---|---|
| subreddit | Yes | ||
| limit | No |
| Name | Required | Description |
|---|---|---|
| result | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. While it mentions the return format ('human readable string'), it doesn't address critical behavioral aspects like rate limits, authentication requirements, error conditions, or whether this is a read-only operation. The description is insufficient for a tool that interacts with an external API.
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 appropriately sized and well-structured with clear sections for Args and Returns. Each sentence serves a purpose, though the 'Returns' section could be slightly more informative about the content format beyond 'human readable string'.
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 has an output schema (though not provided in the prompt), the description doesn't need to detail return values extensively. However, for an API interaction tool with no annotations and sibling tools, the description should provide more behavioral context about limitations, errors, and differentiation from alternatives to be truly complete.
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?
With 0% schema description coverage, the description provides essential semantic context for both parameters: 'subreddit' is explained as 'name of the subreddit' and 'limit' as 'number of posts to fetch' with a default value. This compensates well for the lack of schema descriptions, though it doesn't specify format constraints or validation rules.
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 action ('fetch') and resource ('hot threads from a subreddit'), making the tool's purpose immediately understandable. However, it doesn't explicitly differentiate from its sibling 'fetch_reddit_post_content', which appears to fetch content of individual posts rather than lists of hot threads.
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 no guidance on when to use this tool versus alternatives, including its sibling 'fetch_reddit_post_content'. There's no mention of prerequisites, limitations, or contextual factors that would help an agent decide between this tool and other options.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Fetch detailed content of a specific post
Args: post_id: Reddit post ID comment_limit: Number of top level comments to fetch comment_depth: Maximum depth of comment tree to traverse
Returns: Human readable string containing post content and comments tree
| Name | Required | Description | Default |
|---|---|---|---|
| post_id | Yes | ||
| comment_limit | No | ||
| comment_depth | No |
| Name | Required | Description |
|---|---|---|
| result | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. While it states the tool fetches content and returns a human-readable string, it doesn't cover important behavioral aspects like rate limits, authentication requirements, error conditions, pagination, or whether this is a read-only operation. The description is minimal and leaves significant behavioral questions unanswered.
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 extremely well-structured and concise. It begins with a clear purpose statement, then provides a clean 'Args:' section with parameter explanations, followed by a 'Returns:' section. Every sentence earns its place, and the information is front-loaded with the most important details first. No wasted words or 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 that there's an output schema (though not shown), the description doesn't need to explain return values in detail. However, for a tool with 3 parameters, 0% schema description coverage, and no annotations, the description provides adequate but minimal coverage. It explains what the tool does and what parameters mean, but lacks behavioral context and usage guidance that would make it more complete.
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?
The description adds significant value beyond the input schema, which has 0% description coverage. It clearly explains what each parameter means: 'post_id: Reddit post ID', 'comment_limit: Number of top level comments to fetch', and 'comment_depth: Maximum depth of comment tree to traverse'. This provides essential semantic context that the bare schema lacks, though it doesn't specify format details or constraints.
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's purpose: 'Fetch detailed content of a specific post' - a specific verb ('fetch') and resource ('detailed content of a specific post'). It distinguishes from the sibling tool 'fetch_reddit_hot_threads' by focusing on individual posts rather than hot threads. However, it doesn't explicitly contrast with the sibling beyond the inherent difference in scope.
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 no guidance on when to use this tool versus alternatives. It doesn't mention the sibling tool 'fetch_reddit_hot_threads' or explain when to fetch a specific post versus browsing hot threads. There are no usage prerequisites, exclusions, or contextual recommendations provided.
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.0fetch_reddit_hot_threads4 fields changedInput schema / properties / limit / titleRemoved value: -"Limit"Input schema / properties / subreddit / titleRemoved value: -"Subreddit"Output schema / properties / result / titleRemoved value: -"Result"Output schema / titleRemoved value: -"_WrappedResult"fetch_reddit_post_content5 fields changedInput schema / properties / comment_depth / titleRemoved value: -"Comment Depth"Input schema / properties / comment_limit / titleRemoved value: -"Comment Limit"Input schema / properties / post_id / titleRemoved value: -"Post Id"Output schema / properties / result / titleRemoved value: -"Result"Output schema / titleRemoved value: -"_WrappedResult"fetch_reddit_hot_threadsfetch_reddit_post_contentScored across 2 tools
The two tools have clearly distinct purposes: one fetches a list of hot threads from a subreddit, while the other retrieves detailed content for a specific post. There is no overlap in functionality, making it easy for an agent to select the appropriate tool based on whether it needs overview information or detailed content.
Both tools follow a consistent verb_noun pattern with 'fetch_reddit_' prefix, using snake_case throughout. The naming is predictable and readable, with no deviations in style or convention across the tool set.
With only 2 tools, the server feels thin for a Reddit integration. While the tools cover basic fetching of posts and content, there are likely gaps in functionality such as posting, voting, or searching, which limits the server's utility for comprehensive Reddit interactions.
The tool surface is severely incomplete for a Reddit domain. It only supports fetching operations (read-only), with no ability to create, update, or delete content (e.g., posting, commenting, or voting). This will cause agent failures when trying to perform common Reddit actions beyond simple retrieval.
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
Browse and manage Reddit posts, comments, and threads. Fetch user activity, explore hot/new/rising…
Reddit: Reddit Data API offers streamlined access to Reddit’s public data, like posts, comments.
Read-only Reddit search API for AI agents: posts, comments, comment trees, subreddit rules.
Reddit posts, comments, search, users & subreddits as JSON via Apify. No Reddit API key. $1.50/1k
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/adhikasp/mcp-reddit'
If you have feedback or need assistance with the MCP directory API, please join our Discord server