Thanks for the thoughtful comment! Really appreciate you highlighting the conformance testing angle — it's one of the most painful parts of maintaining multi-language SDKs today. Manual parity work works until drift creeps in, and a robust shared test suite for schema equivalence is exactly what turns "eventually consistent" into reliable consistency.
MCP is a perfect example of the protocol-first approach you mentioned. By defining clear, standardized interfaces for context and tools, it paves the way for SDKs to be largely auto-generated from the protocol spec rather than hand-crafted per language. This aligns closely with what I'm building in apcore: treating the protocol (and patterns) as the source of truth for both behavior and security boundaries.
In the long run, I believe most mature agentic frameworks will move toward this model — auto-generation + strong conformance testing — to minimize the Language Tax.
Have you seen any promising tools or generators for MCP-based SDKs yet? Would love to hear your experience with it.
Aamer Mehaisi
Making AI accessible, ethical, and culturally aware
The Language Tax framing captures something important. The conformance testing angle is key - most teams solve parity manually until drift creeps in. A shared test suite for schema equivalence is the difference between eventually consistent and actually consistent. MCP takes a similar protocol-first approach. Do you see SDKs eventually auto-generated from protocol definitions?