"MCP Was Always a Bad Idea" Hits 323 Points and 322 Comments on Hacker News
A post arguing MCP is now obsolete drew one of the week's most contested HN threads, with comments nearly matching points at 323/322. The argument is that most remote-service MCP servers wrap APIs that already exist, that loading multiple servers' tool schemas bloats context enough to force generic search/execute workarounds, and that current models can call HTTP APIs and CLIs directly. The proposed replacement is content negotiation rather than a protocol: an `Accept: text/markdown` header so servers return agent-readable markdown, and `Accept-Language` for documentation in a preferred programming language. The post cites no token counts or latency measurements, so treat the context-bloat claim as asserted rather than measured.
↳ Follow the thread