Hub tool calling journey (Lightspeed + MCP Chat)
Evidence that Guest Hub AI can call Kubernetes/OpenShift MCP tools with LiteMaaS Qwen (litemaas-qwen). Shared Granite/Qwen stay chat-only.
litemaas-qwen, ask to list pods in this namespace. The UI shows Tool response chips (pods_list_in_namespace, events_list).
litemaas-qwen, OpenShift MCP (19 tools) and Kubernetes MCP (23 tools) enabled.
pods_list_in_namespace in your Sandbox namespace. Reply lists chart pods (Hub, LiteLLM, MCP, applier, PostgreSQL) plus Golden Path workloads and shows Tools used (1) pods_list_in_namespace. Cluster-wide tools like pods_list are disabled for the namespace-scoped MCP ServiceAccount.
Models
| Alias | Tools | Use for |
|---|---|---|
granite / qwen3 |
Dropped by LiteLLM | Everyday Hub chat |
litemaas-qwen → LiteMaaS Qwen3.6-35B-A3B |
ON | Lightspeed + MCP Chat tool demos |
Store the LiteMaaS key only in cluster Secret litemaas-credentials (never in git). See Lightspeed & models.
Related journeys
- Golden Path journey — Deploy Agent / DevSpaces / AI Service templates
- OpenClaw journey — Sandbox OpenClaw + LiteMaaS kubectl tools
DevSpaces Continue Secret
The chart also creates rhdh-agent-sandbox-continue for Che Code Continue → LiteLLM (chat models). Devfile wire-continue consumes it:
