Warp is not requesting initial `tools/list` for servers advertising dynamic tools | Warp | Page 1

Hi @chilly parcel. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:

I'm sorry, but the knowledge sources do not contain explicit information about how Warp handles the MCP protocol's tools/list request logic, especially in relation to the tools: { listChanged: true } capability advertised by a server. The documentation describes how to add and manage MCP servers in Warp, and notes that Warp will list available tools for each running server, but it does not detail the internal logic for when or why Warp sends a tools/list request versus relying on the initial capabilities object returned by the server Model Context Protocol in Warp.

There are user reports of MCP servers that work in other clients (like Cursor) but fail to show tools in Warp, with logs showing empty tool lists or missing requests, but no official documentation or resolution is provided for this specific scenario Task Master AI mcp server failed to start client.

If you are experiencing this issue, it may be a bug or an unsupported edge case in Warp's current MCP client implementation. The best course of action is to file a detailed bug report with logs and configuration details, as the Warp team is actively working on MCP support and has encouraged users to report such issues for investigation MCP integration.

If you need to ensure compatibility, you might try to match the capabilities object to what is known to work (e.g., `{ tools: {} }`), but the knowledge sources do not provide guidance on how Warp interprets or reacts to `listChanged: true`.

#Warp is not requesting initial `tools/list` for servers advertising dynamic tools

If you need to ensure compatibility, you might try to match the capabilities object to what is known to work (e.g., `{ tools: {} }`), but the knowledge sources do not provide guidance on how Warp interprets or reacts to `listChanged: true`.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

#Warp is not requesting initial `tools/list` for servers advertising dynamic tools

If you need to ensure compatibility, you might try to match the capabilities object to what is known to work (e.g., { tools: {} }), but the knowledge sources do not provide guidance on how Warp interprets or reacts to listChanged: true.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

If you need to ensure compatibility, you might try to match the capabilities object to what is known to work (e.g., `{ tools: {} }`), but the knowledge sources do not provide guidance on how Warp interprets or reacts to `listChanged: true`.