Skip to content

docs: update client concept guides for the 2026-07-28 protocol changes#3067

Draft
claude[bot] wants to merge 1 commit into
docs/2026-07-28-releasefrom
claude/rc-client-concepts
Draft

docs: update client concept guides for the 2026-07-28 protocol changes#3067
claude[bot] wants to merge 1 commit into
docs/2026-07-28-releasefrom
claude/rc-client-concepts

Conversation

@claude

@claude claude Bot commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

Requested by Den Delimarsky · Slack thread

Readers of the draft client concept guides previously saw elicitation and sampling described as direct server-to-client requests, with no mention of URL mode elicitation or of tools in sampling. These pages now walk through the tool-call retry flow for those interactions and cover the new URL elicitation mode and tool-capable sampling. The deprecated client features now carry warning callouts with suggested migrations.

Motivation and Context

This is part of preparing the client documentation for the 2026-07-28 protocol release. The draft guides still described server-initiated request flows that the spec has since replaced with the MRTR tool-call retry pattern, and they referenced removed features such as logging/setLevel runtime adjustment and the roots/list_changed notification. New behavior like URL mode elicitation and tool-capable sampling was missing entirely, as were the deprecation notices from the draft changelog.

Closes #3029
Closes #3030
Closes #3032
Closes #3033
Closes #3042

How Has This Been Tested?

Documentation-only change. npm run check:docs passes in full on this branch, covering the prettier format check, the MDX comment check, and the mint broken-links check. docs/docs.json fails prettier --check on the base already, so the edit there was limited to the single redirect line instead of reformatting the whole file.

Breaking Changes

None.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update

Checklist

  • I have read the MCP Documentation
  • My code follows the repository's style guidelines
  • New and existing tests pass locally
  • I have added appropriate error handling
  • I have added or updated documentation as needed

Additional context

Other rc-high-priority bundle PRs also touch docs/docs/draft/learn/architecture.mdx, docs/docs/draft/tools/debugging.mdx, and docs/docs.json, so merge order between those PRs may need care.

AI assistance disclosure: the documentation edits and this PR description were drafted by an AI coding agent working from the bundled issues and the draft specification, and the full diff receives human review before merge.


Generated by Claude Code

- describe the form and URL elicitation modes and reframe the privacy
  guidance around URL mode
- rewrite the elicitation and sampling flows for Multi Round-Trip
  Requests (InputRequiredResult / inputRequests)
- mention tool calling in sampling and retarget the
  /docs/concepts/sampling redirect to the latest spec
- drop roots/list_changed and logging/setLevel references and document
  the per-request io.modelcontextprotocol/logLevel _meta field
- add deprecation callouts for Roots, Sampling, and Logging with
  suggested migrations

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016WBaED7Rta4YsYVz66Qoru
@github-actions github-actions Bot added the documentation Improvements or additions to documentation label Jul 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant