Resources changedspecification/draft/server/resources
Nearest release: v2.1.305, published under an hour 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 20 Oct 2026 20:02 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 22 Oct 2026 20:37 UTC.
Upstream edited
Recorded here
Lines+8added
Lines−8removed
From line
81
where the diff opens
First seen
26 Aug 2026
this site's first read of the page
Recorded edits4to this page, all time
The whole hunk
from line 81, old and new numbered
/
from line 81
8181### Listing Resources
8282
8383To discover available resources, clients send a `resources/list` request. This operation
84supports [pagination](/specification/draft/server/utilities/pagination) and [caching](/specification/draft/server/utilities/caching).
84supports [pagination](/specification/draft/server/utilities/pagination.md) and [caching](/specification/draft/server/utilities/caching.md).
8585
8686**Request:**
8787
from line 130
130130### Reading Resources
131131
132132To retrieve resource contents, clients send a `resources/read` request. This operation
133supports [caching](/specification/draft/server/utilities/caching).
133supports [caching](/specification/draft/server/utilities/caching.md).
134134
135135**Request:**
136136
from line 170
170170`resources/read` request. For example, a server could return the contents of
171171several files when a directory resource is read.
172172
173Servers **MAY** also respond to `resources/read` with an [`InputRequiredResult`](/specification/draft/basic/patterns/mrtr#inputrequiredresult) to indicate that additional input is needed before the resource can be read. This follows the [multi round-trip requests](/specification/draft/basic/patterns/mrtr#multi-round-trip-requests) mechanism. When retrying the request, clients include `inputResponses` and, if provided by the server, `requestState` in the request parameters.
173Servers **MAY** also respond to `resources/read` with an [`InputRequiredResult`](/specification/draft/basic/patterns/mrtr#inputrequiredresult) to indicate that additional input is needed before the resource can be read. This follows the [multi round-trip requests](/specification/draft/basic/patterns/mrtr.md#multi-round-trip-requests) mechanism. When retrying the request, clients include `inputResponses` and, if provided by the server, `requestState` in the request parameters.
174174
175175Alternatively, if the scheme of `uri` is `https://`, clients may fetch the resource directly from the web. See the [Common URI Schemes section](#https%3A%2F%2F) for more information.
176176
from line 178
178178
179179Resource templates allow servers to expose parameterized resources using
180180[URI templates](https://datatracker.ietf.org/doc/html/rfc6570). Arguments may be
181auto-completed through [the completion API](/specification/draft/server/utilities/completion).
182This operation supports [pagination](/specification/draft/server/utilities/pagination) and [caching](/specification/draft/server/utilities/caching).
181auto-completed through [the completion API](/specification/draft/server/utilities/completion.md).
182This operation supports [pagination](/specification/draft/server/utilities/pagination.md) and [caching](/specification/draft/server/utilities/caching.md).
183183
184184**Request:**
185185
from line 259
259259See [Subscriptions][subscriptions] for the full protocol mechanics (acknowledgment,
260260`subscriptionId` correlation, and cancellation).
261261
262[subscriptions-listen]: /specification/draft/schema#subscriptionslistenrequest
262[subscriptions-listen]: /specification/draft/schema.md#subscriptionslistenrequest
263263
264[subscriptions]: /specification/draft/basic/patterns/subscriptions
264[subscriptions]: /specification/draft/basic/patterns/subscriptions.md
265265
266266## Message Flow
267267
No line in this hunk matches that.