Document MCP 2026-07-28 protocol compatibility - #464
Merged
Conversation
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
thebiglabasky
marked this pull request as ready for review
July 31, 2026 08:35
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
2026-07-28and2025-06-18on the existing Checkly endpointWhy
checkly/monorepo#3426 added and shipped the new stateless protocol path while retaining the previous compatibility path. This is user-visible as broader client compatibility, but it does not require a migration.
The note stays in the setup page rather than duplicating backend implementation details across the MCP docs.
Validation
python3 .github/scripts/check_redirect_destinations.pypython3 .github/scripts/check_frontmatter.pynpm run generate-sitemapwith no sitemap diffnpx mint broken-linksgit diff --check