At the very least, make it clear in the UI or docs that multiple private MCP connectors aren't supported. I bought the Premium license this morning, set up a networked MCP connector that works perfectly, and then spent the next three hours trying to debug why I couldn't add a local one for the same machine I'm running TypingMind on.
The only error message I received was: "Update required. Please restart your MCP Connector to upgrade to the latest version that supports Remote MCP servers with authentication." This feels completely misleading, it implies a versioning problem and not an architectural limitation. There's nothing to update; the feature simply doesn't exist.
The ability to add custom connectors via Plugins —> MCP Connectors —> "+ Add connector" makes it feel naturally possible to connect to a second machine. There's no indication anywhere in the UI or docs that this path won't work for a second local bridge. It’s a silent dead-end...
I'd love to see either: (a) proper support for multiple private connectors, or (b) at minimum, a clear error message or doc note explaining the limitation.
Log in to comment and vote
Comments2
Rose Vine
Mar 12
At the very least, make it clear in the UI or docs that multiple private MCP connectors aren't supported. I bought the Premium license this morning, set up a networked MCP connector that works perfectly, and then spent the next three hours trying to debug why I couldn't add a local one for the same machine I'm running TypingMind on.
The only error message I received was: "Update required. Please restart your MCP Connector to upgrade to the latest version that supports Remote MCP servers with authentication." This feels completely misleading, it implies a versioning problem and not an architectural limitation. There's nothing to update; the feature simply doesn't exist.
The ability to add custom connectors via Plugins —> MCP Connectors —> "+ Add connector" makes it feel naturally possible to connect to a second machine. There's no indication anywhere in the UI or docs that this path won't work for a second local bridge. It’s a silent dead-end...
I'd love to see either: (a) proper support for multiple private connectors, or (b) at minimum, a clear error message or doc note explaining the limitation.
Sapphire Crab
Jun 18, 2025
You mean connector but yeah this would be cool