Repository navigation
fix(site): prevent MCP subscription timeouts - #3596
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
This branch had an error being deployed
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.
Problem
MCP
subscriptions/listenrequests return 200 and hold a notification stream open until Vercel's 10-second timeout. A live request reproduced this at approximately 10.5 seconds. The SDK advertises tool-list changes by default, although this site's documentation tools do not change during an invocation.Change
Disable the
tools.listChangedcapability and setmaxSubscriptions: 0so subscription attempts receive an immediate JSON error. Keep normal MCP tool calls and legacy protocol support unchanged.Validation
apps/sitewith Node 22:node ../../node_modules/vitest/vitest.mjs run --root . --config ../../vitest.config.js 'app/api/mcp/[transport]/route.test.ts'.Production logs identify Copilot CLI among timed-out requests but do not expose their MCP method. After deployment, verify that
/mcptimeout rate and billed duration fall; this reproduces and fixes the subscription timeout, but does not establish that every observed timeout had that cause.