Pipe Reddit Opportunities Into Your Stack With APIs and MCP

The dashboard is one way to consume your opportunities. If you'd rather they flow into your own systems — an AI assistant, a Slack bot, a cron job, a spreadsheet — that's what the API layer is for.

The REST surface

Personal API keys (created in Settings → API Keys) authenticate as you — same data, same permissions:

GET /api/v1/opportunities?status=NEW&minScore=7
POST /api/v1/opportunities/{id}/draft
GET /api/v1/replies

Bearer auth, JSON responses, scoped to your projects only.

The MCP endpoint

/api/mcp implements the Model Context Protocol — meaning Claude Desktop, Cursor, and any MCP-aware tool can call CommentSurge directly. The tools exposed map to the real workflow:

• list_opportunities — your scored threads, filtered
• generate_draft — an AI reply draft for a specific opportunity
• get_visibility — your current AI visibility scores
• get_reply_stats — posted-reply performance and removal tracking

Point your assistant at the endpoint with your API key and "what should I reply to today?" becomes a real query, not a fantasy.

Automations worth building

• Morning cron: pull NEW opportunities scored ≥8, format a summary, push to your task list
• Slack triage: pipe high-intent alerts into a channel your co-founder also watches
• Weekly review: pull posted replies, join against signups, compute your own conversion stats
• Assistant-in-the-loop: have your AI assistant draft alternatives on demand — then you review and post from the app

The boundary (same as everything else)

The API can fetch and draft. Publishing still happens inside the app with your explicit click — automation fetches, humans post. Extending programmatic access to everything except auto-publishing is the deliberate design, not a missing feature.