Full Support for Externally-Managed (Non-npm) MCP Servers

Please add full support for MCP servers that are managed externally and not started via Node.js/npm from TypingMind. Many valuable MCP integrations (such as the Python-based Home Assistant MCP proxy) are not available as npm modules and must be run independently.

Currently, TypingMind lists these servers and their tools when detected, but users cannot actually use them in chat—attempting to do so results in a connection error.

Justification:

• There are MCP servers (like the Home Assistant proxy) written in Python and widely used in automation and IoT contexts.

• Allowing TypingMind to connect to and utilize any live/discovered MCP server (not just npm-based ones) would dramatically increase compatibility and unlock real-world use for enterprise and smart home users.

• The UI is misleading if discovered tools can’t be used.

Example:
I run the Python Home Assistant MCP proxy, which TypingMind discovers (all 26 tools show up), but plugin actions fail unless the server is npm-based, which is not possible for this setup.

Enabling support for externally-managed MCP servers would allow TypingMind to become a much more flexible automation and integration platform. Thank you!