What to compare
- package, repository and pinned version
- target release and publication date
- breaking changes and deprecations
- protocol revision supported
- integration test result and rollback version
Read the sources
MCP specification changelog ↗
Changes in the current Model Context Protocol revision compared with the previous one, including breaking changes and deprecations.
Public documentation. This address follows the latest revision; each revision also has its own dated page. The project is moving from the MIT licence to Apache-2.0; read its licence file before copying specification text. A published revision does not mean your SDK or host supports it yet.
MCP Python SDK releases ↗
Tagged releases and change notes for the official MCP Python SDK.
Read the release notes on GitHub, or use the GitHub Releases API with its request limits. MIT-licensed. Pin the version and run server and client tests before upgrading, especially across a major version.
MCP TypeScript SDK releases ↗
Tagged releases and change notes for the official MCP TypeScript SDK.
Read the release notes on GitHub, or use the GitHub Releases API with its request limits. The repository licence file describes a move from MIT to Apache-2.0. Pin the package version and run an integration test before upgrading.
OpenAI Agents SDK releases ↗
Tagged releases and change notes for OpenAI's Agents SDK for Python.
Read the release notes on GitHub, or use the GitHub Releases API with its request limits. MIT-licensed. The project is still before version 1.0, so read each release note for breaking changes before upgrading.
Claude Agent SDK for Python releases ↗
Tagged releases and change notes for Anthropic's Claude Agent SDK for Python.
Read the release notes on GitHub, or use the GitHub Releases API with its request limits. The SDK code is MIT-licensed; using Claude through it is governed by Anthropic's terms. Releases are frequent, so pin a version and test before upgrading.
LangGraph releases ↗
Tagged releases for LangGraph and related packages, including its CLI, SDK and checkpoint libraries.
Read the release notes on GitHub. One releases page covers several packages, so match the package name in each tag. MIT-licensed. Pin each package version separately and test saved checkpoints before upgrading.
Pydantic AI releases ↗
Tagged releases and change notes for the Pydantic AI agent framework.
Read the release notes on GitHub. Pre-releases and fixes for an older major version appear beside current stable releases. MIT-licensed. Use a stable release for production and test structured outputs and tool calls before upgrading.
GitHub Releases API ↗
Release metadata for a chosen repository, including tags and published assets.
Use the documented API with its authentication, pagination and request limits. Pin the repository and release identity. A release asset remains subject to its own licence and integrity checks.
When to look again
When a pinned framework, SDK or MCP revision publishes a release, and before you update dependencies.
Give your agent this question
Compare the pinned version with the target release for each named package. Link the relevant release notes, separate stable releases from pre-releases, and list the integration tests to run before upgrading. Do not install or upgrade anything.