The first MCP Dev Summit runs April 2-3 in New York, and the sessions that matter most to Python developers aren't the ones getting the headline treatment.
Most of the attention will land on the big-picture stuff: OpenAI presenting alongside Anthropic, enterprise adoption numbers, ecosystem growth metrics. That's all fine. But if you're building Python applications that use MCP servers or clients, the sessions you actually need to care about are the technical ones — specifically the auth architecture sessions and the SDK V2 roadmap.
Here's what to watch for, and why.
The Python SDK has been frozen for 63 days
As of this writing, the MCP Python SDK (mcp on PyPI) has been at v1.26.0 since January 24. The TypeScript SDK has shipped multiple releases in the same period. No one has formally announced a Python v2 roadmap — until now.
Max Isbey (Anthropic) is presenting "Path to V2 for MCP SDKs" at the summit. This is the first public statement of intent for a v2 of the MCP Python SDK. The specific session detail that matters: it may include changes to mcp.server.auth.
If you're using mcp.server.auth in production — or you've read any of the FastAPI + MCP integration guides — you should treat this session as a potential compatibility gate. There's a non-trivial chance that v2 reframes how auth is wired into MCP servers. Not necessarily breaking, but worth verifying against your current implementation.
The practical outcome: after April 3, check the session recording or transcript before pinning your dependencies.
Six auth sessions in two days
This isn't a coincidence. The summit schedule has six dedicated sessions on MCP authentication — which tells you two things:
- Auth is the dominant unsolved problem in the MCP ecosystem right now.
- The ecosystem is close enough to a solution that Anthropic is ready to present it at a public summit.
Aaron Parecki is attending. If that name sounds familiar, he's the author of the OAuth 2.1 draft specification. His presence at a developer summit about MCP auth means the conversation will be grounded in real spec work, not marketing positioning.
Paul Carleton (Anthropic) is presenting on Cross-App Access (the internally-named XAA/ID-JAG project) — essentially how MCP can enable single sign-on across multiple AI agents and tools. This is the "SSO for agents" problem. If your Python agents need to share identity and authorization context, this session is directly relevant.
The auth story in MCP right now is fragmented: STDIO servers have no auth at all, HTTP servers implement it inconsistently, and most tutorials pretend the problem doesn't exist. The summit looks like the moment Anthropic is trying to close that gap.
OpenAI is in the room
Nick Cooper from OpenAI is presenting a keynote called "MCP x MCP" on April 3. The specific content isn't confirmed yet, but given that OpenAI's agents SDK (openai-agents) has recently added list_resources() and read_resource() for MCP Resources — and the Anthropic Python SDK has a parallel PR pending — there's a reasonable expectation that cross-ecosystem MCP Resource support gets announced or formalized.
Why does this matter for Python developers? Because if MCP Resources land consistently across both the Anthropic and OpenAI SDKs, it opens a new integration pattern: an agent built with anthropic can query context from a server that was designed for openai-agents, and vice versa. The standard is the interop layer.
That's the design intent. Whether the implementation holds up is a different question — and the thing to verify from the session outputs.
What you can do now vs. what to wait on
Do now:
- Review your current
mcp.server.authimplementation and document the exact version and API surface you're depending on. If you're pinned to a specific version, note why. - If you're using any patterns from the FastAPI + MCP auth guides currently circulating, bookmark them — you'll want to know which ones hold after V2 is specified.
- Check your STDIO vs. HTTP split: if you're purely STDIO, the auth sessions are less immediately relevant to you. If you're exposing HTTP MCP endpoints, they're directly relevant.
Wait on:
- Don't pin your MCP Python SDK version as a safety measure before the summit. You're currently on a 63-day-old version regardless.
- Don't refactor your auth implementation based on summit speculation. Wait for the session outputs.
- The
list_resources()/read_resource()patterns from the OpenAI agents SDK are pre-summit — don't build production workflows around them until you know what the post-summit spec says.
What comes after
April 4 is when the post-summit analysis starts. A few things I'll be publishing:
- A synthesis of what the summit's auth sessions mean for the FastAPI + MCP auth patterns I've been documenting — with specific notes on whether
mcp.server.authchanges require any updates to existing implementations. That one publishes April 10. - The Python MCP Server Templates I built for OAuth 2.1, API key, STDIO, SSE streaming, and FastAPI blueprint patterns are already available on Gumroad — those will get a post-summit review pass if the auth spec changes.
In the meantime: if you're building with MCP and want the auth patterns to make sense before the summit, the AI Dev Toolkit has the prompts I use for designing auth flows, writing secure FastAPI middleware, and reasoning through PKCE and token introspection. That part doesn't change regardless of what the summit announces.
If you're planning to watch the summit remotely, the sessions to prioritize are the V2 SDK roadmap and the auth architecture block. Everything else is context. The code impact is in those two.
I'll post a summary of what actually changed on April 4 or 5 once the recordings or transcripts are available.
Top comments (0)