An argument for deleting your MCP servers, and one thing to do instead today

Patel's case is that MCP was built for models that could not yet write and run their own code, that most remote-service MCP servers "ultimately wrap APIs that already exist," and that models have now learned to discover a CLI by running --help. He notes that the context-bloat workarounds sold by Composio, MintMCP and Pipedream are useful in the short term and are still work spent on a layer he thinks should go away. His prescription is one line: "We delete most of our MCP servers." No measurement is offered for that, and the piece does not claim one. The concrete part is his second proposal, that agents and servers content-negotiate over ordinary HTTP. He reports that a growing number of documentation sites already honor Accept: text/markdown, and quotes an exchange in which Vercel's Malte Ubl asks harnesses to also send the caller's preferred programming language in Accept-Language, and Shopify's Tobi Lutke replies that Shopify docs will support it. We have not verified that Shopify shipped it.

Why it matters: The deletion argument is an assertion and should be read as one. The header convention is already running. If your harness fetches documentation, asking for Markdown costs nothing and is honored today, and the language header is the same idea one step further. That is a change you can make this week. Tearing out a working tool surface on the strength of an essay is not.