modelcontextprotocol / modelcontextprotocol/typescript-sdk
Request time out issue repeatedly
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13.4k
- Forks
- 2.2k
- Avg merge
- 3d 15h
- Merged PRs (30d)
- 4
Description
I'm getting this issue repeatedly , at first it was going so smooth , after some time , it has stuck at endless loop of request time out issue , pls help I have searched everywhere but still didn't figure out how to resolve this issue
-
@modelcontextprotoco….js?v=21582edf:6526 Uncaught (in promise) McpError: MCP error -32001: Request timed out
at timeoutHandler (@modelcontextprotoco…?v=21582edf:6526:43) -
content-all.js:1 Uncaught (in promise) Error: Could not establish connection. Receiving end does not exist.
at y (content-all.js:1:49937)
Repeatedly getting these two issues , pls resolve someone
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the repeated MCP request timeout and inspect the timeout stack location in @modelcontextprotocol…js?v=21582edf:6526. Also investigate the content-all.js connection error and determine whether it is related. Done means identifying a reproducible cause, documenting the relevant environment, and adding or updating a regression test if the SDK path is confirmed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100