A widely discussed argument that MCP should be retired in favour of CLIs and HTTP APIs

Sources: primary, discussion
Summary: The post argues MCP was designed for less capable models, and that the generic search and execute patterns built around it exist mainly to contain context bloat from many servers each carrying many tool schemas. It states that most remote-service MCP servers wrap APIs that already exist, and proposes content negotiation for agents instead of a new protocol, citing the Accept: text/markdown header that documentation sites already honour and a proposal to carry a preferred programming language in Accept-Language. The post is dated 2026-09-14 and reached the Hacker News front page on 2026-09-20 with 267 points and 249 comments.
Why it matters: The argument reframes agent tool access as an HTTP content-negotiation problem, which would move the work from server authors to documentation and API owners.
Follow-up: One practitioner's argument, not a project decision. Open question is whether any agent runtime adopts the content-negotiation path.