Expose resources and parameterized resource templates (URI templates) from a Python MCP server

Documented steps

1. Static resource: @mcp.resource("config://app") on a function returning str — name from the function, description from the docstring. The function only runs on resources/read for that exact URI, never during resources/list, so listing stays cheap. Docs: https://py.sdk.modelcontextprotocol.io/servers/resources/
2. Template: put a {placeholder} in the URI matching a function parameter name exactly: @mcp.resource("users://{user_id}/profile") def get_user_profile(user_id: str) -> str. Templated resources are advertised under resources/templates/list as a uriTemplate; one function serves every matching concrete URI.
3. Use RFC 6570 operators for richer matching: plain {name} stops at the first '/'; {+path} captures multi-segment values with slashes; {?limit,sort} binds optional query params; {/path*} splits segments into a list parameter. Docs: https://py.sdk.modelcontextprotocol.io/servers/uri-templates/
4. Type conversion is automatic from annotations: orders://{order_id} with order_id: int converts the extracted string for you.
5. Return type controls the wire format: str → TextResourceContents; bytes → base64 BlobResourceContents; other JSON-serializable values (dict, list, Pydantic model, dataclass) → JSON text. Set mime_type= on the decorator (default text/plain) — the SDK never guesses from the return value.
6. Verify with uv run mcp dev server.py — static resources appear under Resources, templated ones under Resource Templates (fill the placeholder before reading).