Opportunity dossier O-1387

Recurring need documented in 1 independent public source item.

First seen 2026-07-27 · Last updated 2026-07-27 · Recalculated daily

5.5

Evidence confidence, not a return forecast

Independent source items, deduplicated by post

Public source families

Payment evidence: current spend or explicit intent

ProblemThe source-linked evidence below documents the recurring problem.

People affectedPeople represented in the linked public discussions.

Named alternativesposthog

Weekly mentions · 12 weeksNEW

05-1106-0807-0607-27

Trend factor ×1.0, capped at 2.0.

Representative evidence

1 public excerpts · 1 items in the full chain

Need★★★★☆Product gap

Post title: MCP analytics: handle multiple MCP servers in one project

Teams increasingly instrument several MCP servers into a single PostHog project: a public one, internal ones backing their own agent, and proxies. MCP analytics has no notion of which server an event …

GitHub Issues2026-07-27View source ↗

Follow how this opportunity evolves

Every item traceable · free access · meaningful changes go into the weekly brief

Get weekly changes

Scoring summary

Evidence confidence = strength × evidence volume × source diversity × payment × competition × trend × 10. Counts use independent content items; only first-hand pain, current spend, explicit willingness to pay and concrete feature requests affect the score. Repeated posts by one author are discounted. Scoring and status changes follow deterministic rules.

“Evidence-backed” means the problem appears real, recurring and connected to spending. It does not mean the business is worth building. Read the full methodology.