MCP Has a Product Analytics Problem

If you build a web app today, you have dozens of tools to understand how people use it. PostHog, Amplitude, Mixpanel. Page views, funnels, retention, cohorts. You can answer almost any product question within minutes. Now try doing the same for an MCP server. My friend Johann and I have been building MCP servers and ChatGPT integrations for the past year. We shipped tools, deployed them, and then realized: we had error logs and basic monitoring, but zero insight into how people were actually using our product. We could see when things broke. We couldn't see what was working. The observability layer exists. The product analytics layer doesn't. Let's be fair: MCP developers aren't completely blind. You can hook up Sentry for error tracking. You can pipe logs to Datadog. You can build basic request counting yourself. The engineering observability side of MCP is solvable with existing tools. But product analytics is a completely different thing. Observability tells you "is my server health