modelcontextprotocol / modelcontextprotocol/typescript-sdk
MCP tool calls timeout after 60 seconds for long-running requests
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 using the TypeScript MCP SDK for a chatbot application and I'm encountering timeout errors when a tool call takes longer than 60 seconds to complete.
Some user queries require retrieving data from multiple sources and performing additional processing before generating a response. In these cases, the request may legitimately take more than a minute, but the MCP client times out before the response is returned.
Is there a recommended way to configure or increase the timeout for tool calls without affecting other request types? If not, would it make sense to support a configurable timeout specifically for long running tool executions?
Any guidance would be appreciated.
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 tracing how the TypeScript SDK handles MCP client tool-call timeouts and reproduce a request that runs longer than 60 seconds. Check whether timeout configuration is exposed for tool calls separately from other request types; done means long-running tool executions can be configured without changing unrelated request behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100