Understanding MCP clients changeddocs/2024-11-05/learn/client-concepts

Nearest release: v2.1.284, published 4 hours before upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.

Upstream edited this page at 28 Sep 2026 21:57 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 28 Sep 2026 22:07 UTC.

Upstream edited 28 Sep 2026 21:57 UTC

Recorded here 28 Sep 2026 22:07 UTC

Lines+3added

Lines−3removed

From line 8 where the diff opens

First seen 26 Aug 2026 this site's first read of the page

Recorded edits2to this page, all time

The whole hunk

from line 8, old and new numbered

lines

from line 8

99In addition to making use of context provided by servers, clients may provide several features to servers. These client features allow server authors to build richer interactions.

1010

11| Feature | Explanation | Example |

12| ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- |

13| **Roots** | Roots allow clients to specify which directories servers should focus on, communicating intended scope through a coordination mechanism. | A server for booking travel may be given access to a specific directory, from which it can read a user's calendar. |

11| Feature | Explanation | Example |

12| - | - | - |

1414| **Sampling** | Sampling allows servers to request LLM completions through the client, enabling an agentic workflow. This approach puts the client in complete control of user permissions and security measures. | A server for booking travel may send a list of flights to an LLM and request that the LLM pick the best flight for the user. |

1515

1616### Roots