Key Topics Discussed

1. Documentation Standardization

• Agreed to standardize documentation structure across SDKs using native/idiomatic doc generators (TypeDoc for TS, DOC FX for C#, etc.)
• Key elements: conformance score in README, documentation in docs folder, standardized sections
• Jonathan Hefner driving completion of docs folder structure across repos
• Will move SDK-specific guides from main MCP site into respective SDK repos
• Main MCP site will link to each SDK's documentation

2. Tiering System Rollout

• Timeline shifted: conformance tests ready by January 22nd, then 4-week implementation period
• Three tiers: Tier 1, Tier 2, Tier 3
• Tier 2 will be the minimum bar for an SDK to be considered "official"
• Metrics include:
  • Automated: conformance test pass rates, issue triage/resolution times
  • Self-reported: stable release, documentation, dependency policy, roadmap
• P0 bug resolution: 1 week (Tier 1), 2 weeks (Tier 2)

3. Client vs Server Conformance

• Discussion on whether to separate client and server conformance scoring
• Go SDK passes server tests but struggles with client auth tests
• May consider separate tier classifications (e.g., "Tier 1 Server SDK")
• Will evaluate after seeing initial results

4. API Stability & Semantic Versioning

• "Stable release" means SDK is ready for use, with commitment to API stability
• Breaking changes require new major version (V1 → V2)
• This applies to Tier 1 and Tier 2 SDKs

5. Swift SDK Maintainership

• Stephen Tallent and team have officially taken over Swift SDK maintenance
• Will use Swift SDK as test case for reaching Tier 2

Attendees

• Felix Weinberger, Inna Harper, Paul Carleton, Max Isbey (MCP team)
• Jonathan Hefner
• Christopher Hertel (PHP SDK)
• Robert (Go SDK)
• Cliff Hall
• Mike Kistler (C# SDK)
• Kryspin Ziemski
• Stephen Tallent (Swift SDK)
• Ievgen Pyvovarov

Action Items

1. Jonathan Hefner: Drive completion of docs folder with idiomatic generators across SDK repos
2. Felix Weinberger: Reach out to Jonathan separately about documentation; clarify API stability expectations in tiering docs
3. Robert (Go SDK): Post conformance suite and tiering system plan in SEP issue
4. Kryspin Ziemski: Follow up with Felix in Discord about contributing guidelines