RedditAPIs is a Reddit MCP server and Reddit API alternative for AI agents and developers. One npx line (redditapis-mcp) gives Claude, Cursor, VS Code, Windsurf or Codex 55 Reddit tools, or connect the hosted server at api.redditapis.com/mcp with OAuth sign in. Agents search posts, comments, communities, users and media, read subreddits, rules, wikis and full comment trees, and run monitors that push new matches to a webhook or email. Under the tools is a Reddit data API with 74 REST endpoints and an OpenAPI 3.1 spec: listings, typed and deep comment search, user history, batch lookups, posting, commenting, voting, scheduled posts and Reddit direct messages. Use it as a Reddit scraper API or a Pushshift alternative for live data, without OAuth setup or waiting on Reddit app approval. Reddit API pricing is per call: reads $0.0015, votes $0.005, writes $0.012, DMs $0.025, with $0.50 free credit at signup and no card.

Hi, Emma here. RedditAPIs is a Reddit MCP server and Reddit API alternative for AI agents. One npx line gives Claude or Cursor 55 Reddit tools: search, comment trees, users, monitors with webhooks, even posting and DMs. Prefer HTTP? The same 74 endpoints take one bearer key with no Reddit app approval, from $0.0015 a read with $0.50 free credit. Which tools should we add next?
The per-call pricing ($0.0015 per read, $0.02 per write, $0.50 free credit) makes this easy to test before committing. One question: for the webhook monitors, does a match that fires a webhook count as a billable read, or only the API calls an agent makes? That would help me estimate costs for a brand-monitoring setup.

The local npx MCP server plus a hosted OAuth option is a smart split — agents get live Reddit context without the app-approval wait. One question for the team: with write actions (posts, comments, votes, DMs) available to agents, how do you handle Reddit's rules on automated activity and bot disclosure? Curious whether there are guardrails or rate policies built in, since that's the part that usually gets agent projects in trouble.
The split between a local npx MCP server and a hosted OAuth endpoint is a smart design choice — local for prototyping in Claude or Cursor, hosted for production agents that need persistent access. The webhook-based mention monitoring stands out as the killer feature: it removes polling entirely, which matters when per-call pricing is in play. One suggestion: with 55 tools exposed to the agent, a read-only tool group or a couple of task presets (research, social listening, engagement) would help cut context overhead and keep agents from wandering into write actions unintentionally. Curious whether rate limits from Reddit's side are handled automatically or surfaced to the agent for backoff decisions.
The split between the local npx MCP (55 tools) and the hosted REST API (74 endpoints with an OpenAPI 3.1 spec) is the part that matters if you do not want to wait on Reddit app approval. Per-call pricing is unusually explicit: reads at $0.0015, votes $0.005, writes $0.012, DMs $0.025, plus $0.50 free credit and no card. Does a monitor webhook delivery count as a read against that credit, or is each pushed match billed separately?
came here from the official Reddit API and this is the alternative i wish existed two years ago. PRAW still works but the official pricing and the app-approval wait killed it for side projects, and pushshift has been dead for ages. 74 REST endpoints behind one bearer key, no app approval, $0.0015 a read is exactly the gap. ran a few thousand reads for basically nothing. this is the pushshift replacement a lot of us have been hunting for.

The Pushshift-alternative positioning is what caught my eye — since Reddit restricted cheap historical access, every research pipeline I know of has been hunting for a replacement, so live plus historical comment search behind one bearer key is genuinely useful. Two practical questions: how far back does the deep comment search go, and for the 55 MCP tools, do you support any namespacing or read-only tool profiles? A few comments here mention tool overload eating context window, and a trimmed read-only profile would make agent setups a lot safer. The per-call pricing with the $0.50 free credit and no card required is the right shape for this — usage-based tools should bill like utilities.
The npx redditapis-mcp line just worked in cursor, had claude pulling live subreddit threads in a couple of minutes with no oauth dance. most reddit api options make you register an app and wait days, so dropping 55 tools straight into the agent is the part that sold me. been using it for product-feedback mining off comment threads. does the hosted oauth endpoint expose the same tool set as the local npx one, or a subset?
The deep comment search and full comment trees are underrated. i'm building a rag pipeline and most reddit scraper options only hand you top-level posts, not the whole thread, so pulling typed comment search plus user history from one api saved me writing a scraping layer. at this reddit api cost it's cheaper than running my own scraper on proxies. is there a cap on ids per call on the batch lookup endpoint?
Offering both a local npx MCP server and a hosted OAuth endpoint is a thoughtful split — local for privacy-sensitive work, hosted when you just need it running in Cursor or Claude quickly. The monitor webhooks for brand mentions are the feature I would use most. One question: is there a spend cap or alert so per-call monitor costs cannot quietly run up?
The MCP server plus a hosted OAuth endpoint is a sensible pairing, most agent setups land on one or the other. The part I'd want spelled out is how you stay on the right side of Reddit's API terms and rate limits, since that's usually what breaks these at scale. A spend cap per key would ease that worry too.
Shipping both a local `npx redditapis-mcp` path and a hosted OAuth MCP endpoint is a thoughtful setup for agent workflows — I have wasted too many hours on Reddit app approval just to prototype. Full comment trees plus monitors that can push to a webhook are the two features I would actually use first for research agents. For write actions like posting or DMs, can you scope a key so an agent can read and comment but never send DMs, or is permission all-or-nothing per key?
Offering the same data through both an MCP server and a REST API with an OpenAPI spec is a smart choice, since it covers agent workflows and traditional integrations. The monitors that push new matches to a webhook or email look especially useful for tracking brand mentions without polling. Per-call pricing with free starter credit also makes it easy to test before committing.

Set up and configure the MCP server (npx redditapis-mcp) for Claude, Cursor, VS Code, Windsurf, or Codex. https://www.kpschedule.com.co
his is such a relatable problem—re-explaining project stacks and personal preferences to Claude, ChatGPT, and coding agents every single day becomes exhausting. Having a portable, tool-agnostic memory layer via MCP makes total sense. Love the focus on data control and exportability too. Great launch

Hi, Emma here. RedditAPIs is a Reddit MCP server and Reddit API alternative for AI agents. One npx line gives Claude or Cursor 55 Reddit tools: search, comment trees, users, monitors with webhooks, even posting and DMs. Prefer HTTP? The same 74 endpoints take one bearer key with no Reddit app approval, from $0.0015 a read with $0.50 free credit. Which tools should we add next?
The per-call pricing ($0.0015 per read, $0.02 per write, $0.50 free credit) makes this easy to test before committing. One question: for the webhook monitors, does a match that fires a webhook count as a billable read, or only the API calls an agent makes? That would help me estimate costs for a brand-monitoring setup.

The local npx MCP server plus a hosted OAuth option is a smart split — agents get live Reddit context without the app-approval wait. One question for the team: with write actions (posts, comments, votes, DMs) available to agents, how do you handle Reddit's rules on automated activity and bot disclosure? Curious whether there are guardrails or rate policies built in, since that's the part that usually gets agent projects in trouble.
The split between a local npx MCP server and a hosted OAuth endpoint is a smart design choice — local for prototyping in Claude or Cursor, hosted for production agents that need persistent access. The webhook-based mention monitoring stands out as the killer feature: it removes polling entirely, which matters when per-call pricing is in play. One suggestion: with 55 tools exposed to the agent, a read-only tool group or a couple of task presets (research, social listening, engagement) would help cut context overhead and keep agents from wandering into write actions unintentionally. Curious whether rate limits from Reddit's side are handled automatically or surfaced to the agent for backoff decisions.
The split between the local npx MCP (55 tools) and the hosted REST API (74 endpoints with an OpenAPI 3.1 spec) is the part that matters if you do not want to wait on Reddit app approval. Per-call pricing is unusually explicit: reads at $0.0015, votes $0.005, writes $0.012, DMs $0.025, plus $0.50 free credit and no card. Does a monitor webhook delivery count as a read against that credit, or is each pushed match billed separately?
came here from the official Reddit API and this is the alternative i wish existed two years ago. PRAW still works but the official pricing and the app-approval wait killed it for side projects, and pushshift has been dead for ages. 74 REST endpoints behind one bearer key, no app approval, $0.0015 a read is exactly the gap. ran a few thousand reads for basically nothing. this is the pushshift replacement a lot of us have been hunting for.

The Pushshift-alternative positioning is what caught my eye — since Reddit restricted cheap historical access, every research pipeline I know of has been hunting for a replacement, so live plus historical comment search behind one bearer key is genuinely useful. Two practical questions: how far back does the deep comment search go, and for the 55 MCP tools, do you support any namespacing or read-only tool profiles? A few comments here mention tool overload eating context window, and a trimmed read-only profile would make agent setups a lot safer. The per-call pricing with the $0.50 free credit and no card required is the right shape for this — usage-based tools should bill like utilities.
The npx redditapis-mcp line just worked in cursor, had claude pulling live subreddit threads in a couple of minutes with no oauth dance. most reddit api options make you register an app and wait days, so dropping 55 tools straight into the agent is the part that sold me. been using it for product-feedback mining off comment threads. does the hosted oauth endpoint expose the same tool set as the local npx one, or a subset?
The deep comment search and full comment trees are underrated. i'm building a rag pipeline and most reddit scraper options only hand you top-level posts, not the whole thread, so pulling typed comment search plus user history from one api saved me writing a scraping layer. at this reddit api cost it's cheaper than running my own scraper on proxies. is there a cap on ids per call on the batch lookup endpoint?
Offering both a local npx MCP server and a hosted OAuth endpoint is a thoughtful split — local for privacy-sensitive work, hosted when you just need it running in Cursor or Claude quickly. The monitor webhooks for brand mentions are the feature I would use most. One question: is there a spend cap or alert so per-call monitor costs cannot quietly run up?
The MCP server plus a hosted OAuth endpoint is a sensible pairing, most agent setups land on one or the other. The part I'd want spelled out is how you stay on the right side of Reddit's API terms and rate limits, since that's usually what breaks these at scale. A spend cap per key would ease that worry too.
Shipping both a local `npx redditapis-mcp` path and a hosted OAuth MCP endpoint is a thoughtful setup for agent workflows — I have wasted too many hours on Reddit app approval just to prototype. Full comment trees plus monitors that can push to a webhook are the two features I would actually use first for research agents. For write actions like posting or DMs, can you scope a key so an agent can read and comment but never send DMs, or is permission all-or-nothing per key?
Offering the same data through both an MCP server and a REST API with an OpenAPI spec is a smart choice, since it covers agent workflows and traditional integrations. The monitors that push new matches to a webhook or email look especially useful for tracking brand mentions without polling. Per-call pricing with free starter credit also makes it easy to test before committing.

Set up and configure the MCP server (npx redditapis-mcp) for Claude, Cursor, VS Code, Windsurf, or Codex. https://www.kpschedule.com.co
his is such a relatable problem—re-explaining project stacks and personal preferences to Claude, ChatGPT, and coding agents every single day becomes exhausting. Having a portable, tool-agnostic memory layer via MCP makes total sense. Love the focus on data control and exportability too. Great launch
Find your next favorite product or submit your own. Made by @FalakDigital.
Copyright ©2026. All Rights Reserved