Deprecated, Not Removed: Roots, Sampling, and Logging
Deprecated in MCP 2026-07-28 does not mean gone: roots, sampling, and logging still answer exactly as before, and only a twelve month clock has started. Tell a Deprecated feature from a Removed one under the MCP feature lifecycle, including the twelve month minimum window and how earliest removal is computed. Trace how roots and sampling now travel as MRTR input requests, gated by a client capability the caller must declare on that request. Explain why logging moved to a per-request io.modelcontextprotocol/logLevel key, and when a server may or may not send notifications/message. State the migration path for each deprecated feature: roots, sampling, logging, Dynamic Client Registration, scoped includeContext, and HTTP+SSE. Recognize the small set of methods 2026-07-28 actually deleted, such as logging/setLevel and notifications/roots/listchanged, and explain why a stateless core could not keep them. A candidate who treats "deprecated" as a synonym for "gone" will miss a predictable slice of MCPA questions, and one who treats it as "permanent scaffolding, ignore it" will miss a different slice. MCP 2026-07-28 deprecated three whole client-facing features at once, roots, sampling, and logging, while, in that same revision, deleting a much smaller and different set of methods outright. The two lists do not overlap, and the exam leans on that gap. A tool call that opens an inputrequired result asking for roots/list or…
Deprecated, Not Removed: Roots, Sampling, and Logging: Deprecated in MCP 2026-07-28 does not mean gone: roots, sampling, and logging still answer exactly as…
This free lesson is part of the AI Engineering from Scratch curriculum. Read the full explanation, run the lesson code, and verify the result in the interactive reader or from the repository source.
Browse the complete course catalog or open this lesson on GitHub.