Last reviewed
Correct answer: C. Sampling is deprecated, and the stated path is for new work to call a model provider directly.
Explanation
The principle — A deprecation with a named migration path is a plan, not an emergency.
Why the key is correct — Sampling allows servers to request language model completions through the client, enabling agentic behaviors while maintaining security and user control, and its appeal was exactly the one described here: sampling enables servers to perform AI-dependent tasks without directly integrating with or paying for AI models. That trade is being withdrawn, and the replacement is stated — new implementations should integrate directly with LLM provider APIs.
Why the others are wrong — Direct integration is available, so sampling was never the only route. There is no renamed in-protocol successor. And the feature remains specified, so an upgrade does not force an immediate removal.
Remember this — The successor to sampling is not another request; it is your own provider integration. Budget for the provider key and the cost that came with it, because that was the burden the deprecated feature was carrying.
Sources — MCP first-party documentation.
Sources
“New implementations should integrate directly with LLM provider APIs.”
“Sampling allows servers to request language model completions through the client, enabling agentic behaviors while maintaining security and user control.”
“Sampling enables servers to perform AI-dependent tasks without directly integrating with or paying for AI models.”
“A Deprecated feature remains part of the specification but is scheduled for removal: new implementations SHOULD NOT adopt it, and existing implementations SHOULD migrate before the feature's earliest removal.”
Practise 10 questions on this topic
Take MCP Fundamentals — Timed Test 1 (10 questions) — scored instantly, explanation for every question, no login.