feature: Integrate with warp

[cmdaltctr]

Description

Task Master AI MCP server fails to start or connect properly in certain terminal environments, such as Warp Terminal, despite working in Windsurf. The issue includes warnings like FastMCP warning could not infer client capabilities.

Steps to Reproduce

1. Install Task Master AI via npm on a Mac. 2. Configure MCP server settings with API keys and environment variables. 3. Attempt to start the MCP server in Warp Terminal (it has MCP support now). 4. Observe the warning FastMCP warning could not infer client capabilities and failure to detect MCP server in Warp. 5. Try connecting to the MCP server from Windsurf and observe successful connection.

Expected Behavior

The MCP server should start without warnings and be detected by all terminals and IDEs supporting MCP, including Warp Terminal.

Actual Behavior

The MCP server starts but shows warnings about client capabilities and is not detected by Warp Terminal, though it works in Windsurf.

Screenshots or Logs

Attached.

Environment

• Task Master version: 0.18.0
• Node.js version: v23.11.0
• Operating system: Mac OS 15.5
• IDE (if applicable): Warp Terminal (v0.2025.06.20.22.47.stable_05)

Additional Context

What it looks like in Warp MCP settings:

{ "task-master-ai": { "command": "npx", "args": [ "-y", "--package=task-master-ai", "task-master-ai" ], "env": { "ANTHROPIC_API_KEY": "ANTHROPIC_API_KEY_HERE", "XAI_API_KEY": "XAI_API_KEY_HERE", "PERPLEXITY_API_KEY": "my-api-used-here", "MISTRAL_API_KEY": "MISTRAL_API_KEY_HERE", "AZURE_OPENAI_API_KEY": "AZURE_OPENAI_API_KEY_HERE", "OLLAMA_API_KEY": "OLLAMA_API_KEY_HERE", "OPENAI_API_KEY": "OPENAI_API_KEY_HERE", "GOOGLE_API_KEY": "my-api-used-here", "OPENROUTER_API_KEY": "OPENROUTER_API_KEY_HERE" }, "working_directory": null, "start_on_launch": true } }