What MCP Is Building Next: Server-Side Webhooks and .well-known Discovery

TL;DR: MCP's August 22 roadmap targets server-initiated webhooks (ending long-polling), .well-known server discovery, and Tasks extension graduation — three directions worth knowing before you architect a new server.

The Model Context Protocol team published an updated roadmap on August 22. Three things worth knowing if you are building MCP servers today:

Server-initiated events (next specification release). MCP will add webhooks and channels so servers can push to clients. Today, the client initiates every exchange. The upcoming release lifts that constraint, enabling progress notifications, streaming results, and asynchronous multi-step workflows without client polling. If you are currently queuing events server-side to work around this gap, the protocol-level fix is on the roadmap.

Server Card discovery. The .well-known working group is defining metadata conventions so a client can discover what a server offers without connecting to it first. The target format is /.well-known/mcp-server.json. The spec is not finalized, but the direction is clear enough to plan around.

Tasks extension graduation. The Tasks extension (SEP-2663) was reworked based on early-adopter feedback and is on track to move from an extension into the core specification.

What this doesn't change now: timelines are roadmap directions, not release commitments. The July 28 spec (stateless core, authorization hardening, Multi Round-Trip Requests) is what you migrate to today. The August 22 roadmap describes where the next release is heading — not what shipped.

Why it matters: Server-initiated events unlock patterns that the current polling model handles awkwardly: progress from a long tool call, streaming partial results, background job completion. Design your event handling layer now so the upgrade is a configuration change rather than a rewrite.

Sources: MCP Updated Roadmap (August 22, 2026) — blog.modelcontextprotocol.io · 2026-07-28 Specification — blog.modelcontextprotocol.io · MCP 2026-07-28: What Breaks and How to Migrate — Stacktree