From e746665eb6891334a6b391c47bd774e716415d27 Mon Sep 17 00:00:00 2001 From: cliffhall Date: Sat, 15 Aug 2026 18:10:16 -0400 Subject: [PATCH] docs: mark initialLoggingLevel as legacy-era only (#1990) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Copilot review: the option's doc still promised the level is set "if server supports logging" — after the era gate that is exactly the case which now silently does nothing, since a modern server can advertise `logging` and still ignore the option. Document it as legacy-only and point modern callers at the per-request `io.modelcontextprotocol/logLevel` opt-in (`modernLogLevel` / `setModernLogLevel()`). Signed-off-by: cliffhall --- core/mcp/types.ts | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/core/mcp/types.ts b/core/mcp/types.ts index b89f117b..3873ecea 100644 --- a/core/mcp/types.ts +++ b/core/mcp/types.ts @@ -919,8 +919,16 @@ export interface InspectorClientOptions { pipeStderr?: boolean; /** - * Initial logging level to set after connection (if server supports logging) - * If not provided, logging level will not be set automatically + * Initial logging level to set after connection, via `logging/setLevel`. + * If not provided, the logging level will not be set automatically. + * + * **Legacy era only (#1990).** `logging/setLevel` is a legacy-era method, and + * the modern (2026-07-28) era rejects it — so this option is ignored on a + * modern connection even when the server advertises `logging`. Modern has no + * session-scoped level at all: the equivalent is the per-request + * `io.modelcontextprotocol/logLevel` `_meta` opt-in, configured through the + * `modernLogLevel` server setting and applied via + * `InspectorClient.setModernLogLevel()`. */ initialLoggingLevel?: LoggingLevel;