MCP Client – Capabilities Always Empty ({}) and Missing MCP 2024-11-05 Features

[sysam68]

MCP Client – Capabilities Always Empty ({}) and Missing MCP 2024-11-05 Features

Hi Flowise team,

I recently developed several MCP servers following the MCP 2024-11-05 specification, and I hit a limitation when integrating them with Flowise.

Flowise sends the following initialize request:

{
  "method": "initialize",
  "params": {
    "protocolVersion": "2024-11-05",
    "capabilities": {},
    "clientInfo": {
      "name": "flowise-client",
      "version": "1.0.0"
    }
  },
  "jsonrpc": "2.0",
  "id": 0
}

This means that Flowise announces no MCP capabilities at all.

As a result, only very simple tool invocation works, while the rest of the MCP spec is not supported.

---

Missing MCP Features

Based on my tests and the Flowise codebase, the MCP client currently does not implement:

• prompts/list, getPrompt
• resources/list, resource streaming
• completions, sampling
• MCP over HTTP transport
• Capability negotiation
• Dynamic registration

Environment variable:

CUSTOM_MCP_PROTOCOL = sse  #(stdio | sse)

…only switches the transport, not the capabilities.

---

Question

Is there any configuration to extend the MCP capabilities declared by the Flowise MCP client?

Or alternatively:

Is there a planned evolution toward fuller MCP 2024-11-05 support (prompts, resources, completions, HTTP, etc.)?

At the moment, Flowise always announces:

"capabilities": {}

…which prevents compliant MCP servers from exposing anything beyond basic tools.

---

Thanks

Flowise already does an impressive job as an orchestrator.
I’d love to use it with full MCP features, and I’m happy to help test or contribute if needed.