MCP Server Fails to Start (ERR_UNHANDLED_ERROR, -32001: Request timed out) #1033

New issue

Closed

opened 2025-10-14 16:40:45 -06:00 by navan · 0 comments

navan commented

2025-10-14 16:40:45 -06:00

Owner

Originally created by @vnesin on 4/8/2025

Hello,

We're encountering an issue trying to run the Task Master MCP server within Cursor.

Problem:
When configured in Cursor's mcp.json according to the documentation, the Task_Master server shows a "Client closed" status and fails to connect.

Configuration Used (mcp.json):

{
  "Task_Master": {
    "command": "npx",
    "args": ["-y", "--package", "task-master-ai", "task-master-mcp-server"],
    "env": {
      "ANTHROPIC_API_KEY": "YOUR_KEY_WAS_HERE", // Actual key was provided
      "DEBUG": "true"
    }
  }
}

(Note: We confirmed task-master-mcp-server is the correct binary name from package.json)

Troubleshooting Steps Taken:

Cloned the repository (main branch).
Ran npm install (observed npm WARN EBADENGINE for undici needing node >=20.18.1, user is on v20.11.1).
Exported ANTHROPIC_API_KEY and DEBUG=true environment variables.
Ran the server directly using node mcp-server/server.js.

Error When Running Directly:
The process crashes with the following unhandled error:

Error [ERR_UNHANDLED_ERROR]: Unhandled error. ({
  error: McpError: MCP error -32001: Request timed out
      at FastMcpSession.request (/Users/admin/Documents/Coding Heaven/claude-task-master/node_modules/fastmcp/dist/mcp/session.js:75:23)
      at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
      at async TaskMasterMCPServer.initializeSession (/Users/admin/Documents/Coding Heaven/claude-task-master/mcp-server/src/index.js:90:26)
      at async TaskMasterMCPServer.start (/Users/admin/Documents/Coding Heaven/claude-task-master/mcp-server/src/index.js:40:7)
      at async startServer (/Users/admin/Documents/Coding Heaven/claude-task-master/mcp-server/server.js:31:5)
})
    at FastMcpSession.emit (node:events:515:28)
    at Timeout._onTimeout (/Users/admin/Documents/Coding Heaven/claude-task-master/node_modules/fastmcp/dist/mcp/session.js:116:18)
    at listOnTimeout (node:internal/timers:569:17)
    at process.processTimers (node:internal/timers:512:7)

Analysis:
It seems the server starts but encounters an internal timeout (-32001 from fastmcp) before a connection is fully established or during initialization (initializeSession). This timeout is not caught by the server's error handling, leading to the unhandled error crash.

Environment:

Node.js: v20.11.1
npm: v10.2.4
OS: macOS (darwin 23.4.0)

Could you please investigate this? The unhandled timeout prevents the MCP server from running.

Thanks!

*Originally created by @vnesin on 4/8/2025* Hello, We're encountering an issue trying to run the Task Master MCP server within Cursor. **Problem:** When configured in Cursor's `mcp.json` according to the documentation, the Task_Master server shows a "Client closed" status and fails to connect. **Configuration Used (`mcp.json`):** ```json { "Task_Master": { "command": "npx", "args": ["-y", "--package", "task-master-ai", "task-master-mcp-server"], "env": { "ANTHROPIC_API_KEY": "YOUR_KEY_WAS_HERE", // Actual key was provided "DEBUG": "true" } } } ``` *(Note: We confirmed `task-master-mcp-server` is the correct binary name from `package.json`)* **Troubleshooting Steps Taken:** 1. Cloned the repository (`main` branch). 2. Ran `npm install` (observed `npm WARN EBADENGINE` for `undici` needing node >=20.18.1, user is on v20.11.1). 3. Exported `ANTHROPIC_API_KEY` and `DEBUG=true` environment variables. 4. Ran the server directly using `node mcp-server/server.js`. **Error When Running Directly:** The process crashes with the following unhandled error: ``` Error [ERR_UNHANDLED_ERROR]: Unhandled error. ({ error: McpError: MCP error -32001: Request timed out at FastMcpSession.request (/Users/admin/Documents/Coding Heaven/claude-task-master/node_modules/fastmcp/dist/mcp/session.js:75:23) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async TaskMasterMCPServer.initializeSession (/Users/admin/Documents/Coding Heaven/claude-task-master/mcp-server/src/index.js:90:26) at async TaskMasterMCPServer.start (/Users/admin/Documents/Coding Heaven/claude-task-master/mcp-server/src/index.js:40:7) at async startServer (/Users/admin/Documents/Coding Heaven/claude-task-master/mcp-server/server.js:31:5) }) at FastMcpSession.emit (node:events:515:28) at Timeout._onTimeout (/Users/admin/Documents/Coding Heaven/claude-task-master/node_modules/fastmcp/dist/mcp/session.js:116:18) at listOnTimeout (node:internal/timers:569:17) at process.processTimers (node:internal/timers:512:7) ``` **Analysis:** It seems the server starts but encounters an internal timeout (-32001 from `fastmcp`) before a connection is fully established or during initialization (`initializeSession`). This timeout is not caught by the server's error handling, leading to the unhandled error crash. **Environment:** - Node.js: v20.11.1 - npm: v10.2.4 - OS: macOS (darwin 23.4.0) Could you please investigate this? The unhandled timeout prevents the MCP server from running. Thanks!