Provides tools for searching Reddit conversations using semantic AI, exploring subreddits, and discovering trending topics.
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 Insights MCP Server What are people saying about Rust vs Go?"
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 AI-powered Reddit search and discovery capabilities. Search millions of Reddit posts with semantic AI, explore subreddits, and discover trending topics.
npm install -g reddit-insights-mcpOr run directly with npx:
npx reddit-insights-mcpRelated MCP server: Reddit MCP Server
Add to your Claude Desktop config file:
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"reddit-insights": {
"command": "npx",
"args": ["reddit-insights-mcp"],
"env": {
"REDDIT_INSIGHTS_API_KEY": "your_api_key_here"
}
}
}
}Variable | Required | Description |
| No | API key for premium features |
Get your API key at reddit-insights.com
reddit_searchSearch Reddit conversations using semantic AI search.
Parameters:
query (string, required): Natural language search query
limit (number, optional): Maximum results (1-100, default: 20)
Example:
Search for discussions about mechanical keyboards for programmingreddit_list_subredditsGet a paginated list of available subreddits.
Parameters:
page (number, optional): Page number (default: 1)
limit (number, optional): Results per page (1-100, default: 20)
search (string, optional): Filter by name, title, or description
reddit_get_subredditGet detailed information about a specific subreddit.
Parameters:
subreddit (string, required): Subreddit name without r/ prefix
reddit_get_trendsGet Reddit trend articles and insights.
Parameters:
page (number, optional): Page number (default: 1)
perPage (number, optional): Results per page (default: 12)
filter (string, optional): Time period - "latest", "today", "week", "month"
category (string, optional): Filter by category
Research a topic:
You: What are developers saying about React Server Components?
Claude: [Uses reddit_search] Found 45 results...Explore a community:
You: Tell me about r/typescript
Claude: [Uses reddit_get_subreddit] r/typescript has 285,432 subscribers...Find trends:
You: What's trending in tech this week?
Claude: [Uses reddit_get_trends] Top trending topics...MIT
Get detailed information about a specific subreddit including recent posts.
| Name | Required | Description | Default |
|---|---|---|---|
| subreddit | Yes | Subreddit name without r/ prefix (e.g., 'programming', 'webdev') |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, and the description only mentions that it gets information, lacking disclosure of behavioral traits like rate limits, authentication needs, or error handling for missing subreddits.
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 a single, concise sentence that front-loads the purpose without any wasted 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?
For a simple tool with one parameter and no output schema, the description provides the basic purpose but lacks details about what 'detailed information' includes or potential return format.
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 schema covers the parameter fully with a clear description and example. The tool description adds no additional meaning beyond the schema.
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 gets detailed information about a specific subreddit including recent posts. It distinguishes itself from sibling tools like reddit_get_trends, reddit_list_subreddits, and reddit_search.
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 implicitly suggests using this tool for a specific subreddit details, but it does not explicitly state when to use it over siblings or provide exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Get Reddit trend articles and insights about what's trending.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page number (default: 1) | |
| perPage | No | Results per page (default: 12) | |
| filter | No | Time period filter: 'latest', 'today', 'week', 'month' | |
| category | No | Filter by category |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description should fully disclose behavior. It only mentions getting 'trend articles and insights' but omits details like response format, pagination behavior (though hinted by params), or any side effects. It is insufficient for understanding the tool's operation.
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 a single, concise sentence that conveys the main purpose without wasted words. However, it could be slightly expanded to include key details without losing conciseness.
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 lack of output schema and the presence of four optional parameters, the description does not adequately inform about what the tool returns (e.g., structure of trend articles, pagination metadata). It feels incomplete for an agent to fully understand the tool's capabilities.
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 description coverage is 100% with clear parameter descriptions in the schema. The tool description adds no extra meaning beyond the schema, so it meets the baseline but does not enhance understanding or provide usage hints for parameters.
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 it retrieves Reddit trend articles and insights, which distinguishes it from sibling tools focused on specific subreddits, listing, or search. However, 'what's trending' is somewhat vague and could be more specific about the type of trend data returned.
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?
No guidance is provided on when to use this tool over alternatives like reddit_get_subreddit or reddit_search. The description implies it's for trends, but lacks explicit context for choosing it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Get a paginated list of available subreddits with their information.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page number (default: 1) | |
| limit | No | Results per page (1-100, default: 20) | |
| search | No | Filter subreddits by name, title, or description |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full behavioral disclosure burden. It states it returns a 'paginated list with information' but does not specify what information is returned, sorting order, or mention that it is a read-only operation. This is insufficient for a tool with no annotations.
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 a single well-formed sentence of 10 words. It is concise and front-loaded, containing no fluff. Every word earns its place.
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 presence of 3 optional parameters, no output schema, and no annotations, the description lacks completeness. It does not specify the return format or any behavioral traits (e.g., rate limits, whether results are sorted). A listing tool needs more context to be useful.
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 description adds little beyond the schema. It implies pagination (page, limit) but provides no additional meaning for the 'search' parameter (e.g., matching behavior). Baseline 3 is appropriate.
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 verb 'Get' and the resource 'paginated list of available subreddits' with 'information'. It distinguishes from siblings that focus on single subreddit, trends, or search. However, it could be more explicit about listing all subreddits system-wide.
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 does not provide guidance on when to use this tool versus siblings like 'reddit_search' or 'reddit_get_subreddit'. No exclusions or context are given.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Search Reddit conversations using semantic AI search. Find relevant discussions, opinions, and insights from millions of Reddit posts.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Natural language search query (e.g., 'best programming languages for beginners') | |
| limit | No | Maximum number of results (1-100, default: 20) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description must disclose all behavioral traits. It mentions semantic AI search and broad coverage, but omits critical details like authentication requirements, rate limits, or any side effects. The read-only nature is implied but not stated.
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 ('Search Reddit conversations'), followed by value proposition. No redundant information.
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?
With only two simple parameters and no output schema, the description covers the basic use case. However, it omits details about the return format (e.g., fields returned), which would be helpful. No annotations to supplement.
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 description coverage is 100%, so the tool description adds no additional meaning beyond the schema's own parameter descriptions. Baseline of 3 is appropriate.
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?
Description clearly states it searches Reddit conversations using semantic AI, and distinguishes from sibling tools like reddit_get_subreddit, reddit_get_trends, and reddit_list_subreddits which serve different purposes.
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?
Description implies use for finding discussions and insights, but does not explicitly state when to use this tool versus the siblings. It gives a general context but lacks explicit when-not or alternative descriptions.
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.
v0.1.2reddit_get_subredditreddit_get_trendsreddit_list_subredditsreddit_searchEach tool targets a distinct operation: getting subreddit details, fetching trends, listing subreddits, and searching. There is no overlap in purpose.
All tools follow a consistent 'reddit_verb_noun' pattern (e.g., reddit_get_subreddit, reddit_list_subreddits) with the exception of reddit_search which uses a verb only, but the pattern is still clear and predictable.
With 4 tools covering key Reddit insight operations (subreddit info, trends, listing, search), the count is well-scoped and neither too few nor excessive.
The set covers core read operations for Reddit insights, but lacks ability to fetch individual post details or user information, which are minor gaps. Agents can work around using search and subreddit tools.
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
Read-only Reddit search API for AI agents: posts, comments, comment trees, subreddit rules.
Reddit & X data for AI agents over MCP. Semantic search, hosted, no Reddit API.
Post + comment + subreddit search with comment-level depth for sentiment work.
Browse and manage Reddit posts, comments, and threads. Fetch user activity, explore hot/new/rising…
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/lignertys/reddit-insights-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server
