MCP: Server, Client & Protocol
summary
GitHub MCP server gets the newest MCP spec live 3 weeks before spec launch and rolls it out with almost no friction, raising new-protocol traffic from 3% to 20% in weeks. Real-world testing exposes wide undefined behavior across other MCP servers, so work focuses on robust fallbacks. The team implements multi-round trip request (MRTR) elicitation with sealed, encrypted metadata to enable stateless servers to ask follow-ups (demo: delete-repo confirmation) and ships server cards and the skills-over-MCP extension.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 1:26Scaling GitHub MCP
- 3:37MCP maintainer role
- 5:21Live demo GitHub MCP
- 7:52MCP elicitation
- 10:48Stateless servers impact
- 12:15Future of MCP
related talks
02h 49mMCP Servers: Best Practices, Design Choices and Their Consequences
25mAre MCP Servers Dead?
18mMCP: Origins and Requests For Startups
23mInside MCP: Live Protocol Messages, Real-Time Flows, and Smarter Agents
24mUnderstanding the Architecture of MCP (Model Context Protocol)
23mBuilding with MCP: How Protocol Primitives Shape Dev Experience
47mMCP Demystified: Cutting Through the Hype-What It Is, What Isn't & Its Role in the Agentic RAG Stack
35mMCP, or not MCP