A Brief History of MCP and Where the Spec Is Going in 2026

MCP went from announcement to industry standard in under 12 months. Here's what shipped, what's shipping, and what insurance leaders should plan for.

The Model Context Protocol moved faster than any open standard in recent memory. Here's the timeline and the roadmap.

Timeline

  • Nov 2024: Anthropic announces MCP, ships Claude Desktop support and SDKs in TypeScript and Python.
  • Dec 2024: Cursor adds MCP support. Continue, Cline follow.
  • Q1 2025: Hundreds of community MCP servers ship — filesystem, git, Slack, Postgres, Notion, etc.
  • Q2 2025: Auth standards firm up (OAuth 2.1 flow for MCP).
  • Q3 2025: Streaming responses, prompts, and resources mature. mcp-lite and other lightweight implementations land.
  • Q4 2025: First wave of vertical-SaaS MCP servers. unLocked CRM ships the first insurance CRM MCP server.
  • 2026: OpenAI, Google adopt MCP officially. Carrier and AMS vendors begin shipping.

What's Shipping Next

  • Streaming bidirectional tool calls (lower latency for voice)
  • Standardized capability negotiation between client and server
  • OAuth 2.1 with dynamic client registration as the default auth flow
  • Tool-call sandboxing for untrusted servers

What This Means for Insurance Buyers

The spec is stable enough to bet on. Vendors that don't ship in 2026 will be paying down architectural debt for years. Pick partners shipping today.