provide MCP chat support for a cluster

[vobu]

As a user, I can easily chat with my C8 cluster via its MCP gateway using the console. C8 cluster operations, all in one spot, basically.

c8 chat opens a chat session with the defined cluster (using the common ways to switch to another cluster using --profile).

See https://modelcontextprotocol.io/docs/develop/build-client#typescript for a start for an MCP client.

Do it only for 8.9, so people can directly start "talking" to their cluster!
The cluster's MCP gateway sits at <cluster-url>:<REST-port>/mcp, so localhost:8080/mcp for local clusters.

Implement c8 chat as a c8ctl plugin, not as part of the core!

[vobu]

this has been released via #45

[tmetzke]

this has been released via #45

I would say: kind of, maybe 😆

The linked PR allows local MCP clients to use the mcp-proxy function of c8ctl to connect to the cluster's MCP gateway, which is awesome. However, you still need an MCP client (with a defined LLM provider model and key) 😅

This issue was a bit more about adding an MCP client to c8ctl directly, which is a slightly different thing. The shortest path would simply be to use c8ctl to chat with the cluster. I cannot do that with the linked PR. It might be good enough, of course, but it doesn't close this issue here 😅

[maff]

When we decide to pick up the dedicated chat as part of c8ctl, we can ideally reuse the MCP client connection part of #45 🔧

[vobu]

This issue was a bit more about adding an MCP client to c8ctl directly, which is a slightly different thing. The shortest path would simply be to use c8ctl to chat with the cluster. I cannot do that with the linked PR. It might be good enough, of course, but it doesn't close this issue here 😅

ah, sorry, missed that memo 😬
Then let's keep this open.
I need to work some more on the Plugin API anyway. I don't like it enough 😅
Once I do, I'll come back to this guy here.