Searches public troubleshooting discussions in the r/comfyui subreddit, returning titles, excerpts, and direct Reddit links for read-only support discovery.
Click on "Deploy 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., "@comfyui-reddit-support-finder Find past r/comfyui posts about 'CUDA out of memory' issues."
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 small, non-commercial, read-only MCP server for user-initiated searches of
public troubleshooting discussions in r/comfyui.
The project exists to help people find earlier solutions and original Reddit links before creating duplicate support questions. It is designed for local AI assistants such as Codex, but the user must initiate every search.
The server exposes one tool: search_comfyui_support.
It can:
Search public posts in r/comfyui.
Return a small result set with titles, excerpts, and direct Reddit links.
Process results in memory for the current request.
It cannot:
Post, comment, vote, moderate, or send messages.
Search private communities or private communications.
Build user profiles or infer sensitive user characteristics.
Store Reddit content or use it for model training.
Run autonomous or scheduled collection.
This repository is the public authority for the app's declared access scope. A local integration using the same Reddit OAuth client must not add broader Reddit actions without updating this implementation and obtaining any required Reddit approval first.
Related MCP server: Reddit MCP Server
Suggested values for the Reddit app form:
name: comfyui-reddit-support-finder
type: script
description: Personal, non-commercial, read-only ComfyUI support thread finder used by a local AI assistant.
about url: https://github.com/woodenriver05/comfyui-reddit-support-finder
redirect uri: http://localhost:8080Creating OAuth credentials does not replace Reddit's required access approval. Use the app only for the purpose approved by Reddit and follow Reddit's Responsible Builder Policy, Developer Terms, and Data API Terms.
Node.js 20 or newer
A Reddit OAuth app approved for this use case
REDDIT_CLIENT_ID
REDDIT_CLIENT_SECRET
A truthful, descriptive REDDIT_USER_AGENT
Example User-Agent:
windows:comfyui-reddit-support-finder:v0.1.0 (by /u/your_username)Keep credentials in an environment or secret manager. Do not commit them.
After providing the three required environment variables through your secret manager:
node .\server.mjsExample Codex configuration:
[mcp_servers.comfyui_reddit_support]
command = "node"
args = ["C:\\path\\to\\comfyui-reddit-support-finder\\server.mjs"]
env_vars = ["REDDIT_CLIENT_ID", "REDDIT_CLIENT_SECRET", "REDDIT_USER_AGENT"]
enabled = trueRestart the MCP client after changing its configuration.
The server does not write Reddit content to disk or maintain a database. An OAuth access token is cached only in process memory until expiration. See PRIVACY.md for details.
MIT
Search public r/comfyui posts for user-requested troubleshooting discussions. Read-only, no storage.
| Name | Required | Description | Default |
|---|---|---|---|
| sort | No | relevance | |
| time | No | all | |
| limit | No | ||
| query | Yes | A ComfyUI support or troubleshooting question. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description states 'Read-only, no storage,' which reinforces the readOnlyHint annotation and adds the small extra context that no storage is used. This is useful, but the annotation already covers the core safety trait, so the description only modestly adds beyond the structured data. No rate limits, pagination, or return format details are disclosed.
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 two concise sentences with no filler. The main action and object are front-loaded, and the read-only/no-storage behavior is stated in a compact second sentence. 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?
For a simple search tool with four parameters, an output schema absent, and clear defaults/enums on the schema side, the description gives enough context to select and invoke it. It identifies the resource, topic, and safety profile; the only missing piece is a more explicit description of how sort/time values affect results, but those are still inferable from the schema.
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 only 25%, and the description does not explain the 'sort', 'time', or 'limit' parameters; only 'query' is partially reflected via the phrase 'user-requested troubleshooting discussions.' The schema itself only documents 'query', leaving the other three parameters under-specified for an agent, and the description fails to compensate.
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 names a specific verb and resource: 'Search public r/comfyui posts' and defines the scope as 'user-requested troubleshooting discussions.' It is clearly a search tool for a particular community and topic, which is enough to distinguish it even though no sibling tools are listed.
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 makes the intended use clear: finding troubleshooting discussions in r/comfyui that match user-requested issues. It does not explicitly state when not to use it or list alternatives, but because there are no sibling tools provided, the clear context is sufficient for a correct call.
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.
v0.1.0search_comfyui_supportScored across 1 tool
With a single tool, there is no possibility of confusion between overlapping tools. The tool's purpose is clearly focused on searching r/comfyui support discussions, so an agent can readily understand what it does.
The tool name follows a consistent verb_noun pattern with 'search_comfyui_support'. Since it is the only tool, there are no naming style conflicts to evaluate.
One tool is at the thin lower bound for an MCP server. It may be sufficient for a narrowly focused finder, but it lacks any additional tools that could enhance flexibility or support follow-up requests.
The search tool directly satisfies the server's stated purpose of finding troubleshooting discussions. Some minor gaps exist, such as the inability to fetch specific post details or comments, but the core search functionality is well covered.
Read-only Reddit search API for AI agents: posts, comments, comment trees, subreddit rules.
Browse and manage Reddit posts, comments, and threads. Fetch user activity, explore hot/new/rising…
Search, organize, and chat with your saved Reddit posts from Claude, Cursor, and any MCP client.
Search ATProto writing, annotations, identity, agents, and forum posts. 12 read-only tools.