Are MCP Servers Dead?
summary
Argues MCP servers aren’t dead and gives concrete fixes and features: a stateless V2 spec released recently adds multi‑roundtrip calls, cachable tool lists with TTL, and stricter auth tokens (ISS validation); V1’s stateful registration was the scaling pain. Shows MCP apps (HTML/JS/CSS) in the wild — Starbucks, Tubi, GitKraken’s commit graph and status UI — and warns about context pollution and token cost from large toolsets. Describes WebMCP as discoverable site JS that can act using the user session (WebMCP uses site session) and mentions A2 UI JSON rendering.
AI-written summary · about
chapters (20)
- 0:00MCP servers introduction
- 0:29Clickbait title explained
- 1:10MCP servers explained
- 2:32MCP server types
- 3:14Where to find MCP servers
- 4:15MCP vs skills
- 5:41Criticism of MCP servers
- 6:44Painful MCP implementation
- 7:25MCP v2 changes
- 9:11MCP apps introduction
- 10:33MCP apps examples
- 11:57GitKraken's MCP apps
- 12:58When to use MCP apps
- 13:39HTML output limits
- 14:20MCP app client limits
- 15:02A2 UI specification
- 16:27WebMCP vs MCP servers
- 17:55WebMCP integration
- 19:19Q&A on WebMCP
- 23:54Q&A on MCP
related talks
04h 11mA half-day livestream about the latest in MCP
29mMCP in 2026: Context is All You Need
35mMCP, or not MCP
55mYour MCP Server is Bad (and you should feel bad)
13mMCP: Server, Client & Protocol
28mState of MCP
47mMCP Demystified: Cutting Through the Hype-What It Is, What Isn't & Its Role in the Agentic RAG Stack
17mMCP Is Not Good Yet