MCP Dev Summit 2026: What Actually Changed for Python Developers

The MCP Dev Summit NYC ran April 2-3. If you're building Python AI tools with MCP, here's the short version of what happened and what it means for your code. The summit shipped Python SDK v1.27.0 (with OAuth resource validation), established OAuth 2.1 as the auth consensus across the ecosystem, and previewed V2 as in active development — your existing mcp.server.auth code is stable, and the direction is clear. The longer version is below. The Python SDK V2 story The MCP Python SDK had been at v1.26.0 since January 24 — 68 days without a release while the TypeScript SDK shipped multiple updates. The summit was the first public statement of intent for what comes next. Max Isbey (Anthropic) presented "Path to V2 for MCP SDKs" on April 3. Here's what came out of it: V2 is in active development on the main branch, with v1.x maintenance on a separate v1.x branch — but no Python V2 release or firm timeline was announced. The most concrete output was v1.27.0 itself (shipped April 2, summit day