You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Docs: document the new io.modelcontextprotocol.modern stateless server package #1273
This looks already delivered, in a form worth checking before writing a new section: docs/server.md line 27 carries a note under the 2026-07-28 warning that points at server-modern.md, that page is in the mkdocs nav (line 48), and it is a full page rather than a stub, with Quick Start, transports, the repositories model, request context, streaming, multi round trip requests, caching and custom headers.
So the residue is narrower than the original ask, and one piece of it is worth the issue staying open: there is no runnable sample and no modern client, so a reader can copy the Quick Start server and has no way to check it. The example on the page is a snippet, the repository has no examples module, and the only thing that runs a modern server end to end is conformance-tests/server-servlet-modern, an embedded Tomcat on port 8081 that starts with exec:java on that module and is exercised by the official conformance runner with requirements 2026-07-28.
The smallest useful addition is a short "Verify it" subsection linking that module and that command, not a second page. Two lines it should carry, because each costs a first-time reader an hour:
with no modern client, the only way to hit the server is hand-written HTTP, and a request that declares a protocol version in its _meta has to send a matching MCP-Protocol-Version header. The page does say this, but only inside the transport section, after the Quick Start
the conformance servlet is the behavioural reference, so a divergence between it and the Quick Start snippet is a docs bug rather than a server bug
That closes the ask with about ten lines and no duplication. If you would rather add the runnable example itself, the conformance module is the shape to copy: it already shows the servlet transport plus repositories wired into a real container.
Activity
Kehrlann commentedon Oct 26, 2026
The server is not stable yet, we don't want to start documenting it already.
Kehrlann commentedon Nov 3, 2026
Preview was documented here: b8f43af
We'll do a second pass later on.
media-ctrl commentedon Nov 9, 2026
This looks already delivered, in a form worth checking before writing a new section: docs/server.md line 27 carries a note under the 2026-07-28 warning that points at server-modern.md, that page is in the mkdocs nav (line 48), and it is a full page rather than a stub, with Quick Start, transports, the repositories model, request context, streaming, multi round trip requests, caching and custom headers.
So the residue is narrower than the original ask, and one piece of it is worth the issue staying open: there is no runnable sample and no modern client, so a reader can copy the Quick Start server and has no way to check it. The example on the page is a snippet, the repository has no examples module, and the only thing that runs a modern server end to end is conformance-tests/server-servlet-modern, an embedded Tomcat on port 8081 that starts with exec:java on that module and is exercised by the official conformance runner with requirements 2026-07-28.
The smallest useful addition is a short "Verify it" subsection linking that module and that command, not a second page. Two lines it should carry, because each costs a first-time reader an hour:
That closes the ask with about ten lines and no duplication. If you would rather add the runnable example itself, the conformance module is the shape to copy: it already shows the servlet transport plus repositories wired into a real container.