Task Master AI mcp server failed to start client

[QATOURI]

Pre-submit Checks

• [x] I have searched Warp bugs and there are no duplicates
• [x] I have searched Warp known issues page and my issue is not there
• [ ] I have included the logs (optional, but helps expedite the bug fix). Log gathering intructions

Describe the bug

I configured Task Master AI mcp server in the "Settings" menu but it "Failed to start client". Task Master AI mcp server is correctly installed and being used in the other IDEs, except for Warp Terminal.

To reproduce

1. Go to the AI section of Settings menu.
2. Press "Manage MCP servers".
3. Press "+ add" button.
4. Paste the following:

{ "mcpServers": { "taskmaster-ai": { "command": "npx", "args": ["-y", "--package=task-master-ai", "task-master-ai"], "env": { "ANTHROPIC_API_KEY": "YOUR_ANTHROPIC_API_KEY_HERE", "PERPLEXITY_API_KEY": "YOUR_PERPLEXITY_API_KEY_HERE", "OPENAI_API_KEY": "YOUR_OPENAI_KEY_HERE", "GOOGLE_API_KEY": "YOUR_GOOGLE_KEY_HERE", "MISTRAL_API_KEY": "YOUR_MISTRAL_KEY_HERE", "OPENROUTER_API_KEY": "YOUR_OPENROUTER_KEY_HERE", "XAI_API_KEY": "YOUR_XAI_KEY_HERE", "AZURE_OPENAI_API_KEY": "YOUR_AZURE_KEY_HERE" } } } }

5. Add an API key.
6. Press "Save".
7. The status of Task Master AI mcp server is "Failed to start client" instead of "Running," like the other mcp servers.

Expected behavior

The status should be "Running" and the AI agent of Warp Terminal should be able to use it for manaing tasks.

Screenshots, videos, and logs

Operating system (OS)

Windows

Operating system and version

Windows 11

Shell Version

No response

Current Warp version

v0.2025.05.28.08.11.stable_03

Regression

No, this bug or issue has existed throughout my experience using Warp

Recent working Warp date

No response

Additional context

No response

Does this block you from using Warp daily?

Yes, this issue prevents me from using Warp daily.

Is this an issue only in Warp?

Yes, I confirmed that this only happens in Warp, not other terminals.

Warp Internal (ignore): linear-label:b9d78064-c89e-4973-b153-5178a31ee54e

None

[dannyneira]

Hi @QATOURI, sorry to hear about this, I don't have all the API keys to reproduce this thoroughly, but what do you see when you click on the "View logs" for the failing MCP server? You may be able to provide the logs to Agent Mode to troubleshoot the issue for you.

To anyone else facing this issue, please add a 👍 to the original post at the top or comment with your details, and subscribe if you'd like to be notified.

[arowan]

These are the logs I get. (I'm on Ubuntu)

2025-06-10 21:53:07.266 | [note] Attention! There may be sensitive information (such as API keys) in these logs. Make sure to redact any secrets before sharing with others.
2025-06-10 21:53:07.266 | [info] MCP CLI: Spawned MCP server with pid 1486628
2025-06-10 21:53:07.266 | [info] MCP CLI: Sending request: {"jsonrpc":"2.0","id":6,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"warp","version":"1.0.0"}}}
2025-06-10 21:53:07.986 | [info] MCP CLI: Received response: {"result":{"protocolVersion":"2024-11-05","capabilities":{"tools":{},"resources":{},"logging":{}},"serverInfo":{"name":"Task Master MCP Server","version":"0.16.2"}},"jsonrpc":"2.0","id":6}

2025-06-10 21:53:07.986 | [info] MCP CLI: Sending notification: "{\"jsonrpc\":\"2.0\",\"method\":\"notifications/initialized\"}"
2025-06-10 21:53:07.986 | [info] MCP CLI: Sending request: {"jsonrpc":"2.0","id":7,"method":"resources/list","params":{}}
2025-06-10 21:53:07.988 | [info] MCP CLI: Received response: {"result":{"resources":[{}]},"jsonrpc":"2.0","id":7}

my MCP settings:

{
  "taskmaster-ai": {
    "command": "npx",
    "args": [
      "-y",
      "--package=task-master-ai",
      "task-master-ai"
    ],
    "env": {
      "OPENAI_API_KEY": "KEY",
      "GOOGLE_API_KEY": "KEY"
    },
    "working_directory": null,
    "start_on_launch": true
  }
}

I also get "This MCP server contains secrets" every time i try to save it, so IU've had to turn the privacy settings off to test it. because I can't figure out a regex that works to redact them.

PS @QATOURI I got round using the MCP, by using workflows with a few commands which appears to work just fine.

[benvenker]

Same exact issue for me. I have Task Master running successfully in multiple instances of Cursor and Claude Code just fine, FIWIW.

System details

• MacBook Air M2
• MacOS Sequoia 15.5
• Warp v0.2025.06.25.08.12.stable_01a

{
  "warp:task-master-ai": {
    "command": "npx",
    "args": [
      "-y",
      "--package=task-master-ai",
      "task-master-ai"
    ],
    "env": {
      "GOOGLE_API_KEY": "GOOGLE_API_KAY",
      "PERPLEXITY_API_KEY": "PERPLEXITY_API_KEY",
      "ANTHROPIC_API_KEY": "ANTHROPIC_API_KEY",
      "OPENAI_API_KEY": "OPENAI_API_KEY"
    },
    "working_directory": null,
    "start_on_launch": true
  }
}

Initial config in docs:

Recommended simple config if startup fails

Logs

2025-06-28 10:32:51.118 | [note] Attention! There may be sensitive information (such as API keys) in these logs. Make sure to redact any secrets before sharing with others.
2025-06-28 10:32:51.118 | [info] MCP CLI: Spawned MCP server with pid 39266
2025-06-28 10:32:51.118 | [info] MCP CLI: Sending request: {"jsonrpc":"2.0","id":19,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"warp","version":"1.0.0"}}}
2025-06-28 10:32:51.993 | [info] MCP CLI: Received response: {"result":{"protocolVersion":"2024-11-05","capabilities":{"tools":{},"resources":{},"logging":{}},"serverInfo":{"name":"Task Master MCP Server","version":"0.18.0"}},"jsonrpc":"2.0","id":19}

2025-06-28 10:32:51.994 | [info] MCP CLI: Sending notification: "{\"jsonrpc\":\"2.0\",\"method\":\"notifications/initialized\"}"
2025-06-28 10:32:51.994 | [info] MCP CLI: Sending request: {"jsonrpc":"2.0","id":20,"method":"resources/list","params":{}}
2025-06-28 10:32:51.995 | [info] MCP CLI: Received response: {"result":{"resources":[{}]},"jsonrpc":"2.0","id":20}

[ChrisThompsonTLDR]

I'm experiencing the same on a Windows 11 host machine.

2025-06-28 16:15:57.574 | [info] MCP CLI: Received response: {"result":{"protocolVersion":"2024-11-05","capabilities":{"tools":{},"resources":{},"logging":{}},"serverInfo":{"name":"Task Master MCP Server","version":"0.18.0"}},"jsonrpc":"2.0","id":15}

2025-06-28 16:15:57.574 | [info] MCP CLI: Sending notification: "{\"jsonrpc\":\"2.0\",\"method\":\"notifications/initialized\"}"
2025-06-28 16:15:57.574 | [info] MCP CLI: Sending request: {"jsonrpc":"2.0","id":16,"method":"resources/list","params":{}}
2025-06-28 16:15:57.576 | [info] MCP CLI: Received response: {"result":{"resources":[{}]},"jsonrpc":"2.0","id":16}

[cmdaltctr]

I'm on Mac OS - 15.5 (24F74) Same issue.

2025-06-30 03:59:31.961 | [note] Attention! There may be sensitive information (such as API keys) in these logs. Make sure to redact any secrets before sharing with others.
2025-06-30 03:59:31.961 | [info] MCP CLI: Spawned MCP server with pid 2113
2025-06-30 03:59:31.962 | [info] MCP CLI: Sending request: {"jsonrpc":"2.0","id":15,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"warp","version":"1.0.0"}}}
2025-06-30 03:59:32.966 | [info] MCP CLI: Received response: {"result":{"protocolVersion":"2024-11-05","capabilities":{"tools":{},"resources":{},"logging":{}},"serverInfo":{"name":"Task Master MCP Server","version":"0.18.0"}},"jsonrpc":"2.0","id":15}

2025-06-30 03:59:32.966 | [info] MCP CLI: Sending notification: "{\"jsonrpc\":\"2.0\",\"method\":\"notifications/initialized\"}"
2025-06-30 03:59:32.966 | [info] MCP CLI: Sending request: {"jsonrpc":"2.0","id":16,"method":"resources/list","params":{}}
2025-06-30 03:59:32.967 | [info] MCP CLI: Received response: {"result":{"resources":[{}]},"jsonrpc":"2.0","id":16}

[Mharlin]

same for me but when running this in the terminal I get all the tools echo '{"jsonrpc": "2.0", "id": 1, "method": "tools/list", "params": {}}' | GOOGLE_API_KEY="xxxxx" GEMINI_API_KEY="xxx" taskmaster" npx -y --package=task-master-ai task-master-ai

[baslie]

Same issue for shadcn-ui-mcp-server, Windows 10.

{ "shadcn-ui": { "command": "npx", "args": ["-y", "@jpisnice/shadcn-ui-mcp-server", "--github-api-key", "ghp_my_access_key"], "start_on_launch": false } }

[stex]

The same happens for paperless-mcp:

"paperless": {
  "command": "npx",
  "args": [
    "-y",
    "@baruchiro/paperless-mcp@latest",
  ],
  "env": {
    "PAPERLESS_URL": "http://your-paperless-instance:8000",
    "PAPERLESS_API_KEY": "your-api-token"
  }
}

When using stdio mode, there was another problem as the server prints out a log message before the actual JSON response, but after removing that, it is working fine with Claude Desktop and mcphost.

I also tested using the http version, exactly the same result. The tools response looks good to me.

[DelicateAlchemy]

Same issue. Just adding to the list for a maybe bump on it. TaskMaster is lush and I could make your 03 Task Planning stuff much more useful for me by using it.

[Crunchyman-ralph]

Hey !

Task Master co-founder here, can you guys maybe try to remove the --package=task-master-ai and see if that does anything.

We're going to try working on an better integration soon, seems like a lot of people are asking for it

[DelicateAlchemy]

@Crunchyman-ralph - thanks for contributing to this thread. A lot of people have tried that '--package=task-master-ai' already - thank you for coming here to support Warp though as I really like the product vision

[yilmazer]

I get "Failed to start client" error for shadcn-ui-mcp-server, mac.

{ "shadcn-ui": { "command": "npx", "args": [ "@jpisnice/shadcn-ui-mcp-server" ], "env": { "GITHUB_PERSONAL_ACCESS_TOKEN": "..." }, "working_directory": null } }

Log file:

2025-08-05 23:35:22.588 | [warn] MCP CLI [pid: 34445] stderr: INFO: Transport initialized: stdio 2025-08-05 23:35:22.589 | [warn] MCP CLI [pid: 34445] stderr: INFO: Server started successfully 2025-08-05 23:35:22.592 | [info] MCP CLI: Received response: {"result":{"protocolVersion":"2024-11-05","capabilities":{"resources":{"get_components":{"description":"List of available shadcn/ui components that can be used ... 2025-08-05 23:35:22.592 | [info] MCP CLI: Sending notification: "{"jsonrpc":"2.0","method":"notifications/initialized"}" 2025-08-05 23:35:22.592 | [info] MCP CLI: Sending request: {"jsonrpc":"2.0","id":5,"method":"resources/list","params":{}} 2025-08-05 23:35:22.594 | [info] MCP CLI: Received response: {"result":{"resources":[{"name":"get_components","description":"List of available shadcn/ui components that can be used in the project","uri":"resource:get_components","contentType":"text/plain"}]},"jsonrpc":"2.0","id":5}

[AlniyatYang]

Hello everyone, I have indeed encountered situations where I needed to switch Node.js versions during project development. I previously used context7, but it kept failing to start. Later, I tried switching back to the 18+ version of Node.js, and context7 started working properly. This issue might be due to compatibility problems between context7 and certain versions of Node.js. If you also encounter similar issues, you can try switching to a higher version of Node.js to see if it resolves the startup failure problem.