‹ BackHN Continuity

Thread

You said no MCP

682 points · 362 comments · yarapavan

  1. CharlieDigital · · focus · HN ↗
    This was the easiest call and many like me made it in March[0] among all of the anti-MCP wave of influencers claiming it dead (many, many prominent folks in tech including Garry Tan). Literally every tech influencer in every social feed in March was calling MCP dead and crowning CLI the winner (completely ignoring every reasonable argument around security, observability/telemetry, ease of deployment and operations, etc.)

    A direct quote from March, 2026[1]:

        > If you’re still not convinced that a lot of this discourse [regarding the death of MCP] lacks nuance and is just hype, congrats on buying into the current AI-influencer FOMO hype cycle; see you in 6 months when the influencers move on to the next revelation of the moment to stay relevant and get your eyeballs and dollars.
    
    It was fairly obvious why MCP would be needed once AI engineering and uptake moved beyond the solo developer and single harness stack of "what works for Me" versus "what works for My Team", particularly in an enterprise context. The key mistake people made was thinking in terms of their own workflows and own local stacks instead of a team's workflow and a team's operational stack. There was also an ignorance of MCP's stateless HTTP mode (yes, it was already a thing in March; the 2026-07-28 revision of the spec just prioritizes it as the primary focus moving forward) versus local `stdio`.

    My biggest complaint right now is that OpenAI has still refused to implement the MCP Prompts spec[2] and in general, the major clients have spotty implementation for some of the features in the spec.

    [0] <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=47380270">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=47380270

    [1] <a href="https:&#x2F;&#x2F;chrlschn.dev&#x2F;blog&#x2F;2026&#x2F;03&#x2F;mcp-is-dead-long-live-mcp&#x2F;" rel="nofollow">https:&#x2F;&#x2F;chrlschn.dev&#x2F;blog&#x2F;2026&#x2F;03&#x2F;mcp-is-dead-long-live-mcp&#x2F;

    [2] <a href="https:&#x2F;&#x2F;github.com&#x2F;openai&#x2F;codex&#x2F;issues&#x2F;5059" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;openai&#x2F;codex&#x2F;issues&#x2F;5059

    1. deadbabe · · focus · HN ↗
      There is no reason to think about team workflows. Focus on your workflow. Your own custom local workflow is basically your competitive advantage as an employee. The moment everyone else can do exactly the same things you do, there is no reason to really keep you around.

      The game has changed in the AI era. Horde secrets, skills, custom processes. Don’t share everything. Stop giving things away or you will have nothing left.

      1. moonsu · · focus · HN ↗
        If that works for you great but I am where I am in my career by helping everyone I can around me. Making my team and the company better pays dividends and you stand out from people that only work for themselves.
        1. deadbabe · · focus · HN ↗
          This is now an outdated mentality in the AI era, where people will quickly use whatever you put out to make themselves better but little to no benefit will return to you beyond maybe a fuzzy feeling. People already feel proud just prompting huge projects out and claiming it as their own work. You will not be recognized.

          “When a favor becomes too large to repay, the gratitude turns to resentment.”

          1. moonsu · · focus · HN ↗
            It sounds like you and I are having very different experiences in the AI era.

            Good luck

Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.