Summary of Notes: Meeting Oct 14, 2025 at 5:58 PM BST

Meeting Overview

This was the first SDK maintainers meeting held on October 14, 2025, bringing together representatives from Python, TypeScript, C#, and PHP SDKs to discuss standardization, support tiers, and compliance testing for the MCP (Model Context Protocol) SDKs.

Key Discussion Topics

1. SDK Support Tiers (00:05:35 - 00:27:51)

The group discussed establishing three tiers of SDK support to set clear expectations for users:

• All criteria should be objective and measurable

Tier 1 (Officially Supported) Requirements:

• Support all protocol features
• Implement new protocol features within 2 weeks of release
• Pass compliance tests
• Timely response to issues (acknowledgment/triage, not necessarily resolution)
• Quick resolution of critical/security issues
• Clear dependency update policy
• Full documentation with examples

Tier 2 Requirements:

• Commitment to reach Tier 1 status
• Longer implementation timeline (6 weeks to 6 months suggested)
• Stable release
• May support client-only or server-only (not necessarily both)

Tier 3:

• Experimental SDKs
• No feature completeness guarantee
• No stable release requirement
• Niche SDKs that may remain at this tier

2. Conformance/Compliance Testing (00:27:51 - 00:39:15)

Paul presented a proposal for conformance testing using protocol traces. Key points:

• Tests would verify JSON RPC layer communication patterns
• Authorization layer testing is also planned
• Goal: Any client passing tests should work with any server that also passed
• Each SDK would need example servers per test case
• Initial focus on features releasing in November
• Priority areas identified: OAuth, structured output, transport layer behavior
• A working group will be formed to develop this further

3. Automatic Log Level Handling (00:39:15 - 00:46:46)

Cliff raised an issue discovered in the TypeScript SDK:

• Servers advertising logging capability must handle the "set level" request
• Failure to implement this causes connection failures with Inspector
• TypeScript SDK implemented automatic handling to reduce boilerplate
• This should potentially be part of conformance testing
• Other SDKs should consider implementing similar automatic handling

4. Meeting Cadence

The group agreed to meet monthly going forward.

Participants

• Inna Harper (facilitator)
• Felix & Paul (Anthropic - Python SDK & Typescript SDK)
• Chip Armstrong (TypeScript SDK)
• Cliff Hall (TypeScript SDK)
• Konstantin Konstantinov (TypeScript SDK, Inspector)
• Christopher Hertel (PHP SDK)
• Peder Holdgaard Pedersen (C# SDK)
• Christian Robitaille (observer)

Action Items

Inna Harper

• Write up a proposal document for the SDK tiering system
• Distribute to all SDK maintainers for feedback
• Create formal specification after feedback collection
• Schedule next monthly meeting

Paul

• Start a working group for conformance testing
• Schedule kickoff meeting for the conformance testing working group
• Post in the working group channel and cross-post to SDK channels

Cliff Hall

• Share Discord message link about automatic log level handling with the group
• Advocate for including log level handling in conformance tests

All SDK Maintainers

• Review the tiering proposal when distributed
• Provide feedback on tier requirements
• Consider implementing automatic log level handling in their respective SDKs
• Join conformance testing working group if interested
• Identify priority features for conformance testing

Future Discussion Topics

• Issue prioritization and triage processes across SDKs
• Best practices for managing issue backlogs
• Convenience abstractions and implementation differences between SDKs
• Non-functional requirements (test coverage, documentation standards)