Support for local servers

[tremblerz]

Our host right now is a webpage (frontend) that talks to the backend and connects to the MCP servers that are hosted somewhere else by establishing connection between the backend (client) and the remote MCP server. This makes our system incompatible with the most popular way of playing with MCP, downloading a package and running it locally.

Therefore, we might have to migrate from the web version to a locally hosted version (probably electron or react-native). However, we can also take an existing client such as open-mcp client and modify that one instead.

The good thing with an online host is that the distribution is easier. Furthermore, if we think about the future of MCP, it is likely that people will connect to trusted servers and provide their API keys to perform interesting tasks. A good middle ground is to create a separate software that can be downloaded as a desktop app and connects with the backend client. That way people can run multiple servers locally but still talk to it via our backend.

What do people think? What are some other trade-offs?

[clu5]

PR #20

[qkchambers]

@tremblerz I think it is good move to be able to run the chat software locally. For me personally I would like to be as privacy minded as possible, so i would like to avoid sending sensitive info outside of my computer. I was considering implementing chat history as well and would prefer to keep this data local. If I run this code locally I can keep the same architecture to store history but want to consider the direction of the project as well and it seems like current use case is more directed to a remotely hosted instance.

Modifying an existing client would definitely be easier and depending on the client, you would get additional benefits like RAG. Once a direction is decided I can contribute to the development of this functionality.