René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"MCPServer as a thin composition of the 2026 helpers","articleBody":"`MCPServer` composes the public helpers from the feature issues (MRTR, caching hints, HTTP headers, subscriptions/listen — and the existing schema-inference / registry helpers) into the high-level decorator API — thin, not a monolith with private machinery. Someone using lowlevel `Server` should be able to reach for the same building blocks.\n\n## What's in it\n\n- Compose the public helpers: tool/resource/prompt registries, schema inference, cache hints, `x-mcp-header` annotations, MRTR signaling, listen publishing — exposed via `@server.tool()` / `@resource()` / `@prompt()` kwargs and ctx verbs.\n- **Design needed:** how `MCPServer` presents MRTR and `subscriptions/listen` given the stateless/distributed nature of 2026 — there's no per-connection state to lean on and servers may be horizontally scaled (e.g. where does `requestState` live between rounds; how do listen publishers reach a stream that might be on another instance).\n- Keep `MCPServer` itself thin: anything it does should be a public helper a lowlevel-`Server` user could call directly.\n\n## Conformance\n\n- (SDK API surface — proven via in-repo / interaction tests)\n\n## Dependencies\n\n- Depends on: #2895\n- Depends on: #2898\n- Depends on: #2899\n- Depends on: #2900\n- Depends on: #2901\n\n## References\n\n- [python-sdk MCPServer](https://github.com/modelcontextprotocol/python-sdk/blob/main/src/mcp/server/mcpserver/server.py)\n","author":{"url":"https://github.com/maxisbey","@type":"Person","name":"maxisbey"},"datePublished":"2026-06-17T11:12:05.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/2897/python-sdk/issues/2897"}