[EdidiongA]

While building a Streamable HTTP server that pushes alerts, I lost time to this: sendLoggingMessage() resolves successfully and sends nothing unless the server declared the logging capability. There is no warning. This adds one sentence saying so, next to the existing instruction to declare the capability. MCP logging is deprecated in 2026-07-28 but stays functional through the deprecation window, so the note is useful for as long as the method exists. Happy to adjust the wording.

Also adds one sentence to the sessions page: notifications sent before a client opens its standalone GET stream cannot be replayed by an event store, because the first GET carries no Last-Event-ID.

[pkg-pr-new]

Open in StackBlitz

@modelcontextprotocol/client

npm i https://pkg.pr.new/@modelcontextprotocol/client@3052

@modelcontextprotocol/codemod

npm i https://pkg.pr.new/@modelcontextprotocol/codemod@3052

@modelcontextprotocol/core

npm i https://pkg.pr.new/@modelcontextprotocol/core@3052

@modelcontextprotocol/server

npm i https://pkg.pr.new/@modelcontextprotocol/server@3052

@modelcontextprotocol/server-legacy

npm i https://pkg.pr.new/@modelcontextprotocol/server-legacy@3052

@modelcontextprotocol/express

npm i https://pkg.pr.new/@modelcontextprotocol/express@3052

@modelcontextprotocol/fastify

npm i https://pkg.pr.new/@modelcontextprotocol/fastify@3052

@modelcontextprotocol/hono

npm i https://pkg.pr.new/@modelcontextprotocol/hono@3052

@modelcontextprotocol/node

npm i https://pkg.pr.new/@modelcontextprotocol/node@3052

commit: ed7caa6