MCP's Tasks and Skills are officially Beta now. Breaking changes are still allowed.
By Lior AharonovFounder, 7IT Solutions ·
What happened
On 29 October the MCP project merged SEP-3392, now Final, which gives official extensions three stages: Experimental, Beta and Stable. Apps and Auth were classified Stable; Skills, Tasks and Server Card went to Beta. In the extension support matrix, 3 of 16 listed clients mark Tasks support: Claude (web), Claude Code and MCPJam.
Why it matters
A Beta extension may still make breaking changes under the same identifier. If your server ships Tasks or Skills today, a client upgrade can change the contract under you, and only three clients mark Tasks at all.
What to do
If your server advertises Tasks or Skills, pin the extension revision you test against and watch for the revision string the SEP asks breaking changes to add or bump.

My take
Lior Aharonov
Founder, 7IT Solutions
Beta is an honest word. Build on it, but keep a note of exactly which version you built on.
Sources
| SEP-3392: Extension Lifecycle | modelcontextprotocol.io |
| MCP Extension Support Matrix | modelcontextprotocol.io |
Researched with AI tools; every fact is checked against the linked sources.