Add blog post announcing SDK betas for 2026-07-28#2988
Conversation
🏠 Remote-Dev: homespace
PreviewPreview deployments for this PR have been cleaned up. |
🏠 Remote-Dev: homespace
SamMorrowDrums
left a comment
There was a problem hiding this comment.
Not mentioning the Golang one? They also released one. I've already integrated it into branches in GitHub MCP.
🏠 Remote-Dev: homespace
Rework the announcement around what server implementers need: a compatibility section up front, runnable install and migration steps for both SDKs, links to the RC and transports posts for context, and pointers to the SDK documentation sites and migration guides. Correct the SEP-2577 deprecation scope and clarify the TypeScript wire opt-in. :house: Remote-Dev: homespace
All four Tier 1 SDKs now have pre-releases implementing 2026-07-28: Go v1.7.0-pre.1 and C# 2.0.0-preview.1 join the Python and TypeScript betas. Add a section with install commands, the Go stateless HTTP opt-in, and links to release notes and docs sites; update the title, intro, issue trackers, and pinning advice accordingly. :house: Remote-Dev: homespace
SamMorrowDrums
left a comment
There was a problem hiding this comment.
Nice, it Will be great to get this out.
It might be worth calling out some of the most obvious footguns.
- Server instructions moving to optional discover method with no requirement for clients to call it.
- MRTR Elicitation
And couple of perks:
- meta client info on every request
- http header routing support
- fields optionally duplicated as headers
Maybe not, the SEP links and other articles do cover it. Just thinking that those are things that impact me a fair bit as server developer at least.
|
Agree, @SamMorrowDrums - this is just a scaffold, so we should cover a bunch of those. Will wait for @maxisbey and @felixweinberger to provide their input before making more changes. |
felixweinberger
left a comment
There was a problem hiding this comment.
LGTM from TS perspective, feels like the right level of detail and pointing at the right crosslinks and docs for people who will want to dig deeper.
|
Only thing I'd like to add before we ship this - for typescript I plan to write some larger release notes once I have the beta release, would be great to be able to link to the https://github.com/modelcontextprotocol/typescript-sdk/releases page in the typescript section pre-emptively |
🏠 Remote-Dev: homespace
kfang-ant
left a comment
There was a problem hiding this comment.
Took a pass through with some structural ques.
Co-authored-by: kfang-ant <[email protected]>
Co-authored-by: kfang-ant <[email protected]>
Co-authored-by: kfang-ant <[email protected]>
…K details Address review feedback: frame the betas as test-and-feedback releases with stable versions recommended for production, spell out why trying a beta is safe (opt-in at install and on the wire), and end with concrete steps for library authors. Move the SEP summary ahead of the per-SDK sections so readers see what changed before the language-specific install instructions. :house: Remote-Dev: homespace
- Add stack.svg showing spec -> SDKs -> clients/servers layering - Lead intro with 'stateless' and Python/TypeScript v2 - Standardize on 'v2' (drop mixed '2.0' in prose) - Rename feedback section to 'Tell us what breaks' - Reflow prose to ~100 chars and fix typos
- Retitle to 'Beta SDKs for the 2026-07-28 MCP Spec Release Candidate Are Here' - Restore 'Give us your feedback' section heading - Separate spec-repo pointer from the C# issue-tracker bullet
|
/lgtm force Pushing this out to get the beta announcements. |
Adds a blog post announcing the beta releases of the Python, TypeScript, Go, and C# SDKs with support for the 2026-07-28 specification.
The Go (v1.7.0-pre.1) and C# (2.0.0-preview.1) versions, install commands, and docs links are verified against the published releases. The Python version string, npm dist-tags, publish date, and author list are placeholders until those betas are cut.