I just finished a developer-sentiment MCP server for Reddit. Thirty-two tests green. Deterministic scoring. Four agent-callable tools. Clean Standby deploy. And it's not going to the marketplace.
Not because the build failed. Because the launch would have. Here's the reasoning — it's worth more than the code.
What it does
One call, and an AI agent gets a read on how developers actually feel about a tool, library, or brand: sentiment, mention volume, recurring themes, feature requests — mined from public developer subreddits and returned as structured JSON.
No LLM in the analysis path. Sentiment is a transparent lexicon-plus-rules scorer, so the same posts always produce the same answer. Every aggregate ships with the raw posts behind it. Deterministic and auditable, on purpose.
Four tools: a headline sentiment summary, per-post matched mentions, grouped feature requests, and trending discussions. The kind of thing an agent calls before drafting a comparison post, or a DevRel team runs the morning after a release.
The build was solid. That was never the problem.
{
"build": "reddit-dev-sentiment-mcp",
"tests": "32/32 green",
"tools": 4,
"scoring": "deterministic lexicon + rules, no LLM in the path",
"deploy": "Standby, clean",
"launch_status": "blocked — Reddit Responsible Builder Policy"
}
The wall
Reddit's Responsible Builder Policy. Commercial use of the API requires written approval, and in practice that means a 2–4 week per-user review that ends only when someone on Reddit's internal team signs off.
Now run that through a bring-your-own-key product. Every user needs their own approval before the tool returns a single row. The funnel: discover the actor → hit a credential wall → apply to Reddit → wait two to four weeks → maybe get approved → remember you cared. Conversion through that gauntlet rounds to zero. And the alternative — routing everyone through my one approved key — is a commercial-use posture I'm not taking on at solo scale.
A marketplace listing under those constraints doesn't greet visitors with value. It greets them with a credential error. That's not a neutral portfolio piece. It's an actively bad one.
The reframe that saved the work
I almost filed the whole thing under sunk cost. Then I looked at the architecture again.
The Reddit dependency was one file. Everything that mattered — the sentiment scorer, theme extraction, feature-request mining, aggregation, ranking, caching — operated on a single normalized Post type. All of it source-agnostic. Reddit was just one adapter feeding a deterministic engine.
The liability was never the engine. It was the adapter.
That changes the question from "demo it or shelve it" to "where else can this engine point that doesn't have a month-long gate in front of it?" The answer was sitting right there: Hacker News. Its search API is open. No auth. No approval queue. No policy gate. Point the same tested engine at HN and you get the same product minus every ounce of the friction — it boots and returns data with zero setup. The fatal flaw becomes the headline feature.
The actual lesson
The hard part of most tools isn't the integration. It's the judgment layer you build on top of the data — the scoring, the extraction, the ranking. Keep that layer clean and source-agnostic, and a policy change at one provider is an adapter swap, not a teardown.
I'm keeping the Reddit build public as a reference. The launchable version speaks to Hacker News. Shipping that next.
Built as part of a small slate of agent-focused Apify actors. The engine is the asset; the source is just a plug.
Top comments (0)