docs(mcp): document new session reclamation behavior#13
Open
mgoldsborough wants to merge 1 commit into
Open
Conversation
`MCP_MAX_SESSIONS` is now a soft cap: a new initialize at capacity evicts the least-recently-used session via LRU instead of returning `429 Too many active sessions`. `MCP_SESSION_TTL_SECONDS` now drives a local sweep on the serving pod in addition to the session-store TTL. Updates the env-var reference and the `/mcp` endpoint docs to match, and replaces the "session limits prevent exhaustion" line with one that notes runaway clients can no longer deny service to others under LRU.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Companion docs update for nimblebrain#229.
MCP_MAX_SESSIONSis no longer a hard cap that returns429 Too many active sessions— it's a memory-budget knob with LRU eviction.MCP_SESSION_TTL_SECONDSnow also drives a local idle sweep on the serving pod (not just the session-store TTL).Pages updated
config/environment.mdx— rewrites theMCP_MAX_SESSIONSrow to reflect LRU and points operators at the[mcp] evicting transport reason=pressurelog line as the signal to raise the cap. TightensMCP_SESSION_TTL_SECONDSto mention the local sweep alongside the session-store TTL.api/mcp-endpoint.mdx— same change in the Sessions table; updates the "Session limits" security bullet so it doesn't claim 429 prevents runaway clients (LRU does, and more correctly).Builds cleanly via
npm run build. No content removed; no link targets changed.Test plan
npm run build— 72 pages built, no errors