Don't build another app — build an MCP server: the real signal of MCP's biggest update

Anthropic just shipped the biggest MCP update since launch (MCP 2026-07-28). Most write-ups read like a changelog: stateless core, extensions, auth hardening.

But if you actually build things, the update has one real signal: **your distribution channel just got upgraded.**

MCP is now the HTTP of the AI era — and the pipe is enterprise-grade, runs on serverless, and can render your UI *inside Claude itself*. Which points at a very concrete move: **stop building another app to fight for attention. Build an MCP server, and let the agent ecosystem be your distribution.**

(Based on a 新智元 / 36kr write-up and Anthropic's official MCP blog; specs per Anthropic.)

The standard war is over

• 400M+ **monthly** SDK downloads (4x this year).
• TypeScript and Python each past **1 billion** cumulative downloads.
• **950+** MCP servers in the Claude store, used by millions daily.

As Anthropic frames it: HTTP wired the world's computers into the internet; MCP is wiring the world's software, data, and APIs into a network an AI orchestrates. For builders, "should I use MCP" is settled. The question is whether you're on the rail.

Signal 1: the core went stateless — so your server can run serverless

The change developers wanted most: MCP moved from **stateful** (session state, connection handshakes, hard to scale in cloud-native setups) to a pure **request/response** model. Every request is self-describing (identity and capabilities live in `_meta`).

The payoff:

• **Serverless / edge**: deploy the server to AWS Lambda, Vercel, Cloudflare Workers — no renting a persistent box for a few KB of session state.
• **Unlimited horizontal scaling**: put it behind a plain round-robin load balancer; any machine can handle any request.
• Need state? Generate an explicit **Handle** the model passes back as a parameter — not hidden in the transport layer. Cleaner, and it fits how the model thinks.

Translation: **building an MCP server now costs about as much as writing one serverless function.** The channel got bigger *and* the bar to get on it dropped — those two happening together is the actual opportunity window.

Signal 2: extensions are first-class — you may not need a front-end

Anthropic promoted **Extensions** to first-class citizens with an official framework. Three launch features, and the first is the one that should reframe how you think about products:

• **MCP Apps**: your server renders an **interactive UI right inside the Claude chat** (a sandboxed iframe). Ask Claude for revenue data → it renders a live interactive dashboard in the thread. Ask it to run a cloud server → a control panel pops up. No more tab-switching between Claude and every SaaS app.
• **Tasks**: long-running async work (analyze 100GB of logs, render a 3D video) via polling + a subscription stream.
• **Enterprise Managed Auth (EMA)**: central access control through Microsoft Entra, Okta; zero-touch SSO.

MCP Apps is the punchline: **your interface can live inside Claude.** You d