Search Reddit for posts matching a query.
ConnectorOAuth
569,407 tools. Updated 2026-09-14 23:27
"reddit" matching MCP tools:
- Get detailed content of a specific Reddit post with comments.ConnectorOAuth
- Get comments submitted by a specific Reddit user.ConnectorOAuth
- Get posts submitted by a specific Reddit user.ConnectorOAuth
- Get posts from a subreddit.ConnectorOAuth
- Rewrite YOUR drafted comment so it reads like a real person typed it, not an AI: strips AI tells, compresses to the 1-2 points that matter, varies rhythm, and lightly "dirties" it (lowercase sentence starts, no markdown). Best AFTER you draft a reply — write the real substance, then humanize it. INPUT RULES for best results: (1) put every fact/number/name you want kept IN the text — it never invents any; (2) keep it to ONE or TWO points — it cuts hard and drops the rest; (3) plain text only — markdown, bullet lists, and em-dashes are stripped; (4) shorter is better, ≤2000 chars; (5) one comment per call, do NOT include the post you are replying to. Pick `character` for the voice. Returns the rewrite, the AI "tells" found in your draft (so you can draft cleaner next time), and remaining daily quota. Output is intentionally imperfect + non-deterministic — do NOT "fix" it or retry for a cleaner version. Free · daily-capped · no Reddit credits. (usable right now without an account, daily-capped per IP)ConnectorNo auth
Matching MCP Servers
- AlicenseAqualityAmaintenanceEnables browsing Reddit, searching posts, reading comment threads and user history, with opt-in posting and voting through the Reddit API.1420 npmMIT
- AlicenseAqualityAmaintenanceEnables reading Reddit content (posts, comments, search) via RSS feeds without an API key or account, supporting subreddit browsing and post retrieval with minimal setup.41MIT
Matching MCP Connectors
Reddit: Reddit Data API offers streamlined access to Reddit’s public data, like posts, comments.
Reddit MCP — public Reddit data via JSON endpoints (no auth required)
- Search all of Reddit by keywords. type picks the target: posts (default), comments (what people actually say about a product, problem, or brand -- unique to Reddit search), subreddits (find communities), users. Pass query as free text up to 256 characters; decompose broad topics into several narrower queries, since result depth per query is capped upstream around a few hundred results. sort applies to posts (relevance|top|new|hot|comment_count) and comments (relevance|top|new); range (past_hour..all_time) applies to posts only; both are rejected with INVALID_INPUT elsewhere. Costs 6 credits per page; a cursor page is a NEW call priced the same way. Returns one page of summaries (author, title or comment text, upvotes, comment_count, created_at, permalink, id) with a cursor; there is no server-side time window on comment search, so for monitoring filter on created_at yourself and poll with sort=new. Fetch full post bodies and discussion threads with reddit_get_post; read one community's feed with reddit_get_subreddit_posts. For high-volume recency sweeps across X instead, use x_search.ConnectorOAuth
- Search a single network for posts matching a query, returned as the unified Post[] schema and tagged with its platform. Keyless on TikTok, YouTube, and Pinterest. Instagram, Twitter/X, Reddit, and Facebook need operator-side credentials (returns credentials_required until set). Snapchat and Threads do not support keyless search (returns not_supported); LinkedIn is quarantined. To fan one query across every network at once, use search_all.ConnectorNo auth
- [DEPRECATED — renamed tag_rule_list. Will be removed after 2026-10-07.] List your org's TAGGING RULES (the dashboard's 'Tagging rules') — labels applied to posts your Watchers already ingest. NOT the dashboard's Keyword Monitor: for the keywords that search all of Reddit daily, use keyword_monitor_list. Each rule tags matching Dataset records whose title or body mentions its term as a whole word. Returns the term, active status, and match statistics. Changes take effect on the next scheduled processing cycle. Existing opportunity scores and matches are not retroactively updated. (requires a free Prowlo account — call it to get a signup link)ConnectorNo auth
- List records in your Dataset (Prowlo’s indexed posts from crawled sources). NOT a live Reddit call — free, rate-limited only. Filter by view (all/matched), subreddits, platforms, tags, keyword, `any` (brand-variant OR-group), include/exclude, intent, score/comments, date range, watcherId. Paginated via cursor. Note: tags / watcherId are record-level, so passing either uses the "matched" view automatically. Records whose keyword match was AI-judged coincidental are hidden by default (pass includeSuppressed:true to see them; each record carries a `verification` field). A filtered page can hold fewer than `limit` items — page until nextCursor is null. Long record bodies are trimmed to keep the page scannable — use get_record for a record’s full body. (requires a free Prowlo account — call it to get a signup link)ConnectorNo auth
- List your org's TAGGING RULES (the dashboard's 'Tagging rules') — labels applied to posts your Watchers already ingest. NOT the dashboard's Keyword Monitor: for the keywords that search all of Reddit daily, use keyword_monitor_list. Each rule tags matching Dataset records whose title or body mentions its term as a whole word. Returns the term, active status, and match statistics. Changes take effect on the next scheduled processing cycle. Existing opportunity scores and matches are not retroactively updated. (requires a free Prowlo account — call it to get a signup link)ConnectorNo auth
- List your Keyword Monitor entries (the dashboard's "Keywords" page): each searches all of Reddit once a day for its query and ingests matches into your Dataset. Returns your keyword quota (used/max; max -1 = unlimited). Add via keyword_monitor_create; pause via watcher_update; delete via watcher_delete (ids are Watcher ids). NOT the tagging rules — see tag_rule_list. Not a live Reddit call — free, rate-limited only. (requires a free Prowlo account — call it to get a signup link)ConnectorNo auth
- Fetch one page of posts from a single subreddit, the community-monitoring primitive. subreddit_name is the name without the r/ prefix. sort defaults to the subreddit's own front-page order (best); use sort=new for monitoring. sort=top and controversial need a range, but the window is currently not applied upstream on this feed: top returns the subreddit's all-time top posts whatever range says (time-windowed tops are a known gap here; reddit_search's range DOES work for keyword queries). Costs 4 credits per page; a cursor page is a NEW call priced the same way. Reddit splices about one promoted ad into every feed page; these are dropped by default, so set include_promoted=true only when ads ARE the data you want (ad intelligence, who targets this community) -- kept ads carry is_promoted=true. Returns post summaries (title, author, upvotes, comment_count, created_at, permalink, id) with a cursor for older posts; bodies and discussions come from reddit_get_post with the returned ids. For keyword search across all of Reddit use reddit_search; this tool takes no query.ConnectorOAuth
- Fetch full post content for up to 100 Reddit posts by their t3_ ids in one call -- the follow-up loop after reddit_search or reddit_get_subreddit_posts. Costs 4 credits for up to 10 ids, +1 credit per further 10 ids; every post comes back with its full body text. With exactly ONE id you may set detail to 'full' for +4 credits to also get the discussion tree (comments flattened in tree order with depth, about 200 per page, with a comments_cursor to continue), or pass comment_id (a t1_ id, also +4 credits) to fetch one specific comment in its post context. Post ids come from the other Reddit tools or from reddit_resolve_url on a post URL. Not for discovering posts; search first, then batch-fetch here.ConnectorOAuth
- ACCOUNT REQUIRED (free — sign in via GitHub at https://pipeworx.io/signup; depth:"thorough" needs a paid plan). If you are not signed in, use ask_pipeworx instead — it works on every tier. Grounded multi-source research across Pipeworx's 1552 STRUCTURED data sources (SEC filings, FRED/BLS economics, FDA, USPTO patents, markets, science, government records, etc.) in ONE call — this is NOT open-web search. Decomposes your question into focused facets, routes each to the right one of 5,961 tools IN PARALLEL, and returns a findings packet: verbatim evidence + confidence + source + fetched_at + a stable pipeworx:// citation per finding, with explicit gaps[] for facets the data couldn't answer (never invented). Best for broad/multi-part questions over structured data ("compare X and Y's regulatory + financial exposure", "research the filings + market picture for ACME"). For a single lookup use ask_pipeworx (one LLM call, not many). For BREAKING or colloquial CURRENT-NEWS / "what's the world saying about X" topics, prefer ask_pipeworx — it routes to live news APIs and the *-news-feeds packs; deep_research returns mostly empty gaps[] when the topic isn't in the structured catalog. Second-hop iteration: depth:"standard" re-angles unanswered gaps (gap recovery); depth:"thorough" additionally chases the best leads from the first pass — so multi-step questions resolve in one call. Every finding carries a `hop` field and a citation_uri — a resolvable pipeworx:// record URI, present only when the source emits one that resources/read can actually serve, so a citation you get back is always fetchable. "standard" and "thorough" also return contradictions[] flagging findings that disagree. Large records are semantically excerpted to the passages relevant to each facet (not head-truncated), so answers deep in a long filing/series aren't missed. Expect 15-60s (thorough with its follow-up + contradiction pass: up to ~90s).ConnectorNo auth
- Cross-venue spread between Kalshi and Polymarket for the same resolving question. The two venues sometimes price the same outcome 2-25pp apart because their participant pools differ — when the bet shapes are equivalent that delta is a real signal, when they aren't the tool says so. TWO MODES: (1) `topic` — 11 pre-mapped macro subjects ("fed", "btc", "eth", "cpi", "gdp", "sp500", "recession", "next_pope", "next_uk_pm", "next_israel_pm", "2028_president") auto-fetch the matching event on each venue. You do NOT have to use those exact keys: the topic is resolved through aliases and keywords, so "bitcoin", "fed rate decision", "inflation", "s&p 500" and "next pope" all land on the right subject, and `resolution.topic_matched_by` tells you whether it was an exact key, a known alias, a phrase found inside a longer question, or a single-keyword guess — treat "phrase" and "token" as a GUESS at what you meant. An unresolvable topic returns error:"mapping_failed" with mapping_stage:"topic_unrecognized" and known_topics[]; it never silently falls back to a default subject. (2) explicit `kalshi_event_ticker` + `polymarket_event_slug` for custom pairings — BOTH modes run the identical token-overlap matcher, so the same disclosures apply to both. `resolution` is returned in BOTH modes and says how each side's identifier was picked (which Kalshi series was queried, how many events came back, whether the chosen one had quoted markets; which Polymarket search query ran and why that event won). RESPONSE: each venue's leg-by-leg prices (raw probability 0-1) plus matched spread[].top_spreads_pp (Kalshi − Polymarket) where the same outcome shows up on both sides. SAFETY FIELDS: compatibility_warning is a sentence and compatibility_codes[] the machine-readable form; BOTH can be non-empty on returned pairs, so read them even when matched_pairs>0. Codes: event_subject_mismatch (the two event titles share no subject words — probably not the same question), temporal_mismatch (they resolve in different months), temporal_alignment_unknown (the resolution month could not be parsed on one or both sides — NOT the same as confirmed-aligned; check each event's close/strike date yourself), non_equivalent_bet_shapes, no_candidate_pairs, unclassified_legs_excluded, pairing_unverified (set in EITHER mode whenever pairs are returned: the legs were matched by keyword and word overlap, not a shared resolution source). Each entry in top_spreads_pp carries its own flags[] (temporal_mismatch, temporal_alignment_unknown, event_subject_mismatch, low_token_overlap). A leg whose metric_type or match_subtype is "unknown" is NEVER paired — those comparisons land in spread.skipped_unclassified and, when the wording lined up, in spread.low_confidence_pairs[] for inspection only. temporal_alignment{polymarket_month,kalshi_month,aligned} tells you whether the two events resolve in the same calendar period, in EITHER mode; null means it could not be computed (see temporal_alignment_unknown), not that the two sides align. spread.fees_note is a standing disclosure: Kalshi charges per-contract trading fees, Polymarket does not, and this tool does not model Kalshi's fee schedule — every spread_pp is gross, not a net tradeable edge. spread.resolution_source_note is the second standing disclosure: the two venues' RESOLUTION SOURCES are never compared, so a Polymarket market settling on a Binance 1-minute candle and a Kalshi event striking on Kalshi's own index at a different hour will still be shown side by side — part of any spread_pp may be a difference in contract rather than in opinion. skipped_cross_type / skipped_cross_subtype counters expose how many leg-pair comparisons were dropped (cross-type = metric_type mismatch like MoM vs YoY; cross-subtype = inequality mismatch like cum_ge vs cum_le). Real cross-venue spreads are rarer than the macro-shortcut list suggests — most pre-mapped topics return compatibility_warning today; pre-mapped ≠ tradeable.ConnectorNo auth
- Create Watchers — including KEYWORD MONITOR entries (the dashboard's "Keywords" page): pass platform "reddit_search" with the search query as `channel`; each searches all of Reddit daily and draws from its own per-plan keyword limit (keyword_monitor_create is the one-query shortcut). Community watchers (a subreddit or HN feed) are the default platform. A Watcher watches exactly ONE community/query, so each `sources` entry creates its own Watcher (its name is derived from the source, e.g. "r/saas"). Subject to your plan's Watcher limits. Not metered. (requires a free Prowlo account — call it to get a signup link)ConnectorNo auth
- Semantic + keyword search over Prowlo's own pre-crawled subreddit catalog (~1,200 tracked, active, non-NSFW communities) — NOT a live Reddit call and NOT your org's Dataset. The same index behind prowlo.com's public Subreddit Finder. Use this FIRST when discovering candidate communities for a product or niche; describe the audience or problem, not just keywords. Returns ranked cards with subscribers, posts/day, 30-day growth, and promoTolerance (low/medium/high; null = not yet profiled, NOT "no restrictions"). Free, cached, NOT metered. Next steps: catalog_get_subreddit for the full stat card, catalog_top_subreddits to browse rankings, watcher_create to start watching. For a LIVE Reddit subreddit search (subs outside this catalog), use social_find_channels (1 credit). For an evidence-backed, ranked report with rules and an engagement plan, use research_run / research_get. (requires a free Prowlo account — call it to get a signup link)ConnectorNo auth
- JSON matrix of data types (metadata, insights, transcript, frames, comments) per platform — YouTube (+Shorts), TikTok, Instagram Reels, Pinterest, Reddit. Call before framefetch_extract to confirm support. No input.ConnectorNo auth
- Fetches operational status of major dev infrastructure (GitHub, Cloudflare, Discord, OpenAI, Vercel, npm, Reddit, Atlassian, Anthropic). Cache TTL 60s. Use when the agent needs to know if a dependency is up or to explain a recent outage.ConnectorNo auth
- Get Reddit post by ID with its comments. Returns both the post data and comments in a single response. FAST (default, omit responseType or responseType="fast"): Returns post and up to 300 comments directly (use limit param to reduce, e.g. limit=5). Auto API fallback for fresh data. Results include guidance for full mode. PAGING (responseType="paging"): Async paginated results (100 comments/page), returns operationId for polling via checkOperationStatus. Supports pageNumber/tableName for subsequent pages. RESPONSE STRUCTURE: Returns { results: { post: {...}, comments: [...] }, count, guidance }. PAGING MODE DETAILS: FIRST CALL: Omit pageNumber and tableName. Creates cached table for comments, returns page 1 with post data and pagination metadata. SUBSEQUENT PAGES: Use tableName from first response with pageNumber (2, 3, etc.) to fetch additional comment pages. Post data is NOT returned on subsequent pages. FIELD SELECTION: Use postFields for post data optimization, commentFields for comment data optimization. First searches database for both post and comments, then external API if data is stale or missing. This is a safe, read-only tool for analyzing searchable information.ConnectorOAuth