I don't mean irreplaceable. I mean it's become the default communication layer for a huge number of people, which gives it a level of importance beyond a typical social app.Sure, people would move. But the value isn't WhatsApp itself it's the fact that everyone you need to talk to is already there. That's what makes it hard to replace overnight.
WhatsApp feels like one of the few products where people might actually pay. It's become critical infrastructure for communication in many countries, not just another social app.
AI has made it much easier to build an app, but distribution hasn't gotten any easier. Getting through App Store review, acquiring users, and retaining them still feels like 90% of the battle.
Getting an app running is rarely the hard part. Keeping it healthy a few months later usually is. How much thought has gone into things like incident response, monitoring, and operational tooling?
Really appreciate this — handshake drift is a real issue in MCP setups. Also love the health badge idea (showing last transport + error count would be super helpful).
Inspector is the right tool for local STDIO servers — use it. We're complementary, not competing.
MCP Playground fills a different gap: no install (browser tab, nothing to run), built for remote HTTP/SSE endpoints rather than local processes, and includes hosted test servers so you can verify your client implementation without needing a server at all. Plus a registry if you're trying to discover what's out there.
Inspector ideal for: STDIO, local debugging, open source, deeper protocol introspection.
MCP Playground for: zero setup, remote servers, client testing, browsing mcp registry/server list.