Небольшой некоммерческий MCP-сервер с доступом только для чтения, выполняющий по инициативе пользователя поиск по публичным обсуждениям об устранении неполадок в r/comfyui.
Проект существует для того, чтобы помогать людям находить более ранние решения и исходные ссылки на Reddit, прежде чем создавать повторяющиеся вопросы в поддержку. Он предназначен для локальных ИИ-ассистентов, таких как Codex, но каждый поиск должен быть инициирован пользователем.
Сервер предоставляет один инструмент: search_comfyui_support.
Он может:
искать публичные посты в r/comfyui;
возвращать небольшой набор результатов с заголовками, фрагментами и прямыми ссылками на Reddit;
обрабатывать результаты в памяти для текущего запроса.
Он не может:
публиковать, комментировать, голосовать, модерировать или отправлять сообщения;
искать в закрытых сообществах или личной переписке;
составлять пользовательские профили или делать выводы о чувствительных характеристиках пользователя;
хранить контент Reddit или использовать его для обучения моделей;
выполнять автономный или запланированный сбор данных.
Этот репозиторий является публичным источником сведений о заявленной области доступа приложения. Локальная интеграция, использующая тот же OAuth-клиент Reddit, не должна добавлять более широкие действия Reddit без обновления этой реализации и предварительного получения необходимого одобрения Reddit.
Related MCP server: Reddit MCP Server
Рекомендуемые значения для формы приложения Reddit:
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:8080Создание учётных данных OAuth не заменяет получение одобрения доступа от Reddit. Используйте приложение только для той цели, которая одобрена Reddit, и следуйте Responsible Builder Policy, Developer Terms и Data API Terms Reddit.
Node.js 20 или новее
приложение Reddit OAuth, одобренное для этого варианта использования;
REDDIT_CLIENT_ID
REDDIT_CLIENT_SECRET
правдивый и описательный REDDIT_USER_AGENT
Пример User-Agent:
windows:comfyui-reddit-support-finder:v0.1.0 (by /u/your_username)Храните учётные данные в переменных окружения или в менеджере секретов. Не сохраняйте их в системе контроля версий.
После того как вы зададите три обязательные переменные окружения через свой менеджер секретов:
node .\server.mjsПример конфигурации Codex:
[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 = trueПерезапустите MCP-клиент после изменения его конфигурации.
Сервер не записывает содержимое Reddit на диск и не ведёт базу данных. Токен доступа OAuth кэшируется только в памяти процесса до истечения срока действия. Подробнее см. в PRIVACY.md.
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.
Search public Reddit posts, browse subreddit feeds, and read posts, comments, and profiles.
Search and read public Reddit and X posts, comments, threads, profiles and Articles; run monitors.
Reddit posts, comments, keyword search and historical archives as tools. Runs on Apify.
