modelcontextprotocol/python-sdk
Watch
1
0
Fork
You've already forked python-sdk
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs: convert bold cross-references into links, link SEP and RFC mentions (#3017)

Browse source
This commit is contained in:
Max 2026-06-29 13:07:26 +02:00 • committed by GitHub
commit 24fdd909ac
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 167 additions and 167 deletions
Download patch file Download diff file Expand all files Collapse all files

10
docs/advanced/uri-templates.md
View file

@ -4,7 +4,7 @@ This is the reference for the URI-template syntax that
[`@mcp.resource`](../tutorial/resources.md) accepts, and for the
path-safety policy the SDK applies to extracted values. For an
introduction to what resources are and when to use them, start with
**Resources**; this page assumes you're already comfortable declaring a
**[Resources](../tutorial/resources.md)**; this page assumes you're already comfortable declaring a
resource and want the full operator set, the security knobs, or the
low-level wiring.
@ -17,7 +17,7 @@ details (message formats, lifecycle, pagination) see the
## The full operator set
**Resources** showed one placeholder, `{user_id}`. There are four more
**[Resources](../tutorial/resources.md)** showed one placeholder, `{user_id}`. There are four more
operator forms; here they are on one server so you can see them next to
each other:
@ -201,13 +201,13 @@ These checks are a heuristic pre-filter; for filesystem access,
!!! tip
If your handler can't fulfil the request (the file doesn't exist,
the id is unknown), raise an exception. The SDK turns it into an
error response. See **Handling errors** for the difference between a
error response. See **[Handling errors](../tutorial/handling-errors.md)** for the difference between a
protocol error and a tool error.
## Resources on the low-level Server
If you're building on the low-level `Server` (see **The low-level
Server**), you register handlers for the `resources/list` and
If you're building on the low-level `Server` (see **[The low-level
Server](low-level-server.md)**), you register handlers for the `resources/list` and
`resources/read` protocol methods directly. There's no decorator; you
return the protocol types yourself.