Fix claude code connectivity timeouts#3830
Merged
Merged
Conversation
KoolADE85
force-pushed
the
bugfix/claude-mcp-timeouts
branch
from
48f8f84 to
c793778
Compare
Member
|
Is an e2e test connecting a Dash MCP to Claude Code in scope for our test suite? |
Contributor
Author
No, we don't have any plumbing in place to connect Claude to the MCP server in an integration test. I think that will be a heavier lift. |
|
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
3 participants
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.
Recent versions of Claude Code have intermittent issues connecting to a Dash MCP server when run on localhost.
This PR adds a workaround that allows Claude to connect reliably.
Issue:
The MCP server previously responded to GET requests with a
405 Not Allowed. While the spec does allow this, the dev server automatically closes connections with this response. Depending on the timing, Claude would attempt to reuse the already-closed connection which caused connectivity failures.Solution:
The 405 response code is replaced with a 200 and an empty, completed stream which Claude accepts and correctly moves on.