BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//pretalx.com//pycones-2026//talk//YDSZY9
BEGIN:VTIMEZONE
TZID:Europe/Madrid
BEGIN:STANDARD
DTSTART:20251107T000000
TZNAME:CET
TZOFFSETFROM:+0100
TZOFFSETTO:+0100
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20260329T030000
RDATE:20270328T030000
TZNAME:CEST
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
END:DAYLIGHT
BEGIN:STANDARD
DTSTART:20261025T030000
RDATE:20271031T030000
TZNAME:CET
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
SUMMARY:What I've Learned Maintaining the MCP Python SDK - Marcelo Trylesi
 nski
DTSTART;TZID=Europe/Madrid:20261107T114000
DTEND;TZID=Europe/Madrid:20261107T122000
DTSTAMP:20260726T232829Z
UID:pretalx-pycones-2026-YDSZY9@pretalx.com
DESCRIPTION:After months of maintaining the MCP Python SDK and reviewing m
 any community contributions\, I’ve seen some architectural hiccups in re
 peat. Developers struggle with questions that seem simple but have nuanced
  answers: When should one tool become three? When does a server need to sp
 lit into two? How do you test an MCP server without spinning up a full cli
 ent? When should you use resources or prompts instead?\n\nIn this talk\, w
 e will explore my learnings and understand how to design tool boundaries t
 hat scale with your server’s complexity\, structure your codebase for lo
 ng-term maintainability\, and build a testing strategy for your MCP server
  that works. I’ll share real examples from the wild\, both the antipatte
 rns to run away from and the implementations worth adopting.\n\nIn 2026\, 
 the MCP Python SDK v2 will bring improved typing\, a refined API\, and bet
 ter testing primitives. The architectural decisions you make today will de
 termine whether that migration takes a day or a month.\n\nWhether you’re
  maintaining an internal tool or publishing to the community\, you’ll le
 ave with a clear framework for evaluating your own server’s design and c
 oncrete next steps to improve it.
LOCATION:Track 05
URL:https://pretalx.com/pycones-2026/talk/YDSZY9/
END:VEVENT
END:VCALENDAR
