Repository navigation
Document load testing and Active Sessions on modelcontextprotocol.io #2869
Description
Problem
The Inspector pages on modelcontextprotocol.io mention the --load flags only in passing: one dense bullet in the CLI page's CI gates recipe, and one sentence on the mcpdo page (added in modelcontextprotocol/modelcontextprotocol#3483). Nothing explains what a load run does, how to read its summary, how it stops, or how it behaves on an mcpdo daemon connection.
The load mode now spans several releases of work: #2439 (CLI --load), #2744 (mcpdo tools/call --load), #2745 (thresholds), #2746 / #2800 (--load-connections), #2834–#2837 (Ctrl+C partial summary, dead-server stop, success-only latency, --load-rate shortfall fields), and #2868 (the connection_lost abort message).
Active Sessions
#2901 (closing #2831) adds an Active sessions button to the web client's header. It opens a list of every session the backend holds open, across every tab, with each session's status and a Terminate action that closes its connection and ends a stdio server process. Nothing on modelcontextprotocol.io describes it, or the 60-second detach grace (#2824) that lets a session outlive its tab.
Deliverable
A follow-up to #2450 with the same shape: both doc versions (draft and 2026-07-28) change identically, apart from their link prefixes.
tools/inspector/cli: a Load testing a tool section covering the flags, the summary fields, failure and stop behavior (including exit130), CI thresholds (exit10), and multiple sessions.tools/inspector/mcpdo: a Load testing section on how a run behaves on a daemon connection.tools/inspector/configuration: point the load-test flag row at the new section.tools/inspector/web: an Active sessions section with screenshots from feat(web): list and terminate active backend sessions #2901: the header button, what each column and status means, Terminate, the detach grace, and theGET/DELETE /api/mcp/sessionsroutes.
Amended: the load-testing content became a dedicated tools/inspector/load-testing page (see the comment below), and Active Sessions (#2901) was added to the scope.
Sourced from clients/cli/README.md, clients/mcpdo/README.md and clients/web/README.md on v2/main, plus #2901 for Active Sessions.
Activity
cliffhall commentedon Nov 4, 2026
Priority score: severity 2 (missing docs; the READMEs are a workaround) + urgency 3 (wanted this milestone) + milestoned (+1) + assigned (+1) = 7 → Medium.
cliffhall commentedon Nov 5, 2026
Scope change: a dedicated page instead of per-page sections.
Since this issue was filed, the load mode has grown into scenarios, argument placeholders, stepped and ramped load, open loop, baselines, session churn, notification fan-out, and a web-client panel (#2929). Covering all of that as sections on the CLI page would have made load testing roughly half of that page. modelcontextprotocol/modelcontextprotocol#3503 now adds a dedicated page instead,
tools/inspector/load-testing, in both doc versions:The CLI, mcpdo and web pages each keep a short section under their existing anchors that links to the new page. The CLI exit-code table, the CI-gates recipe and the configuration flag row point there too. The page is in the navigation after mcpdo and has a card on the Inspector overview.
Sourced from
clients/cli/README.md,clients/mcpdo/README.mdandclients/web/README.mdonv2/mainate10b1f34.[-]Document load testing (CLI --load, mcpdo tools/call --load) on modelcontextprotocol.io[/-][+]Document load testing and Active Sessions on modelcontextprotocol.io[/+]