Key Topics Discussed

1. Conformance Testing (Paul)

• Paul demonstrated the conformance testing framework located in the model-context-protocol/conformance repository
• Tests can be run against both clients and servers using npm commands
• Tests provide detailed logs in both pretty-printed and raw JSON formats
• Can be run via npx, with plans for Docker image distribution

2. SDK Abstractions and Standardization

• Discussion about standardizing convenience features across SDKs
• Client Manager/Session Group concept exists in Python and Go SDKs but not uniformly implemented
• Go SDK implemented client sessions for symmetry with server-side sessions
• Cloudflare has a client manager in their agents SDK that they're willing to move upstream
• Need for standardization around connection definitions and transport abstractions
• Different SDKs have varying approaches to defining connections (JSON vs. other types)

3. SDK Version 2 Plans

• Python SDK: Originally planned for end of 2025, now likely early 2026. Will focus on V2 after current spec release
• Go SDK: No concrete timeline yet. Waiting for stateless transport to warrant breaking changes
• TypeScript SDK: No specific timeline mentioned
• All SDKs want to coordinate on standardization before V2 releases

4. Issue Management and Triaging

• Go SDK reported relatively quiet issue activity (49 issues, 13 PRs)
• PHP SDK not yet at V1, so manageable issue volume
• Python and TypeScript SDKs have higher volume requiring systematic triage
• Proposed triage system (Felix):
  • Categorize by type: bug, feature request, or question
  • Assess readiness: Does it have enough information/repro to work on?
  • Prioritize: P0 (critical/security), P1, P2
• Need for consistent labeling across SDKs for automated tracking
• Current label system has too many duplicates and needs cleanup

5. SDK Tiering Requirements

• Tier 1 requirements include triaging all issues within 2 days and resolving P0 bugs within one working week
• Conformance testing will be part of tiering system, starting with simplified server-only tests
• November 14th deadline for tier declaration has been removed - no rush to declare tiers
• Tiering guidance will be released separately from spec changes as it's part of the governance, not spec changes

6. Semantic Versioning and SDK-Spec Compatibility

• Discussion of SEP 1309 regarding semantic versioning table
• Need to reconcile versioning table with SDK tiering requirements
• Goal to automate table generation using conformance testing
• Team to review SEP 1309 and incorporate relevant parts into SDK governance

Attendees

• Inna (core maintainer)
• Max (MCP team, Python SDK)
• Felix (MCP team, Python → TypeScript)
• Paul (MCP team, auth/security, conformance testing)
• Matt (Cloudflare, TypeScript SDK)
• Constantine (TypeScript SDK)
• Rob (Go SDK)
• Christopher Hertel (PHP SDK)
• Anurag Pant (Java SDK)
• Luca Chang

Action Items

Immediate Actions

1. Felix: Clean up and share internal issue triage documentation with SDK maintainers group
2. All SDK maintainers: Review conformance testing framework and provide feedback in Discord #conformance channel
3. Go SDK team: Implement conformance tests and provide feedback on tooling/wrappers needed
4. All SDK maintainers: Review SEP 1309 and discuss relevant points in SDK general chat
5. Inna: Include issue triage guidance in SDK governance documentation

Short-term (Next Few Weeks)

1. Python/TypeScript teams: Clean up duplicate labels in issue tracking
2. All teams: Establish consistent labeling system across SDK repositories
3. Cloudflare (Matt): Continue work on disentangling client manager from infrastructure primitives for potential upstream contribution
4. All maintainers: Propose additional topics for next SDK maintainers meeting via Discord or direct message to Inna

Medium-term

1. All teams: Discuss and document standardized abstractions for:
   • Client Manager/Session Group implementation
   • Connection definitions and transport abstractions
   • Common terminology (transport, connection, etc.)
2. Python SDK team: Focus on V2 planning after current spec release
3. All teams: Begin implementing conformance tests for their SDKs