bug: MCP Connection Closed Error After Upgrading to v0.27.3 #42

New issue

Closed

opened 2025-10-14 15:39:19 -06:00 by navan · 0 comments

navan commented

2025-10-14 15:39:19 -06:00

Owner

Originally created by @paulreijnierse on 10/3/2025

Description

The Taskmaster MCP server connection is consistently closing/failing after upgrading to version 0.27.3, resulting in "{"error":"MCP error -32000: Connection closed"}" and "Not connected" errors for all MCP tools. When I disable and enable the mcp in Cursor settings it shows all the toolcalls, but when Cursor executes one I only get the error. On a second toolcall after this I see "{"error":"Not connected"}"

This did not happen for me on previous versions (I ran 0.27.2 before). I updated the mcp.json to follow the latest setup (without the --package setup). I restarted Cursor and even my machine but the behaviour remains consistent.

The cli works just fine.

Steps to Reproduce

Open Cursor IDE with Taskmaster MCP server configured
Attempt to use any Taskmaster MCP tool (e.g., get_task, add_subtask, set_task_status)
Error occurs consistently across all MCP tool calls

Expected Behavior

MCP tools should work reliably without connection drops. Expected commands like mcp_taskmaster-ai_get_task, mcp_taskmaster-ai_add_subtask, etc. should execute successfully and return proper responses.

Actual Behavior

All MCP tool calls fail with one of these errors:
MCP error -32000: Connection closed Not connected
The connection appears to drop after any operation.

Screenshots or Logs

{"error":"MCP error -32000: Connection closed"}
{"error":"Not connected"}

Environment

Task Master version: 0.27.3
Node.js version: v22.12.0
Operating system: macOS (darwin 23.6.0)
IDE (if applicable): Cursor version: 1.7.33

*Originally created by @paulreijnierse on 10/3/2025* ### Description The Taskmaster MCP server connection is consistently closing/failing after upgrading to version 0.27.3, resulting in "{"error":"MCP error -32000: Connection closed"}" and "Not connected" errors for all MCP tools. When I disable and enable the mcp in Cursor settings it shows all the toolcalls, but when Cursor executes one I only get the error. On a second toolcall after this I see "{"error":"Not connected"}" This did not happen for me on previous versions (I ran 0.27.2 before). I updated the mcp.json to follow the latest setup (without the --package setup). I restarted Cursor and even my machine but the behaviour remains consistent. The cli works just fine. ### Steps to Reproduce 1. Open Cursor IDE with Taskmaster MCP server configured 2. Attempt to use any Taskmaster MCP tool (e.g., get_task, add_subtask, set_task_status) 3. Error occurs consistently across all MCP tool calls ### Expected Behavior MCP tools should work reliably without connection drops. Expected commands like mcp_taskmaster-ai_get_task, mcp_taskmaster-ai_add_subtask, etc. should execute successfully and return proper responses. ### Actual Behavior All MCP tool calls fail with one of these errors: `MCP error -32000: Connection closed Not connected` The connection appears to drop after any operation. ### Screenshots or Logs `{"error":"MCP error -32000: Connection closed"}` `{"error":"Not connected"}` ### Environment - Task Master version: 0.27.3 - Node.js version: v22.12.0 - Operating system: macOS (darwin 23.6.0) - IDE (if applicable): Cursor version: 1.7.33