What prerequisites are needed to set up this demo lab?
You need a Kubernetes cluster (K3s is used in the guide), credentials for the SUSE Application Collection (username and token), and Helm installed to deploy cert-manager and Rancher Fleet.
@alessandro-festa
Basic information
A set of bundles to demonstrate SUSE AI capabilities
No standard config provided
This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.
RepositoryTool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
GreenDoc - SUSEAI Demo Lab is a document that describes how to implement a local lab to demonstrate capabilities of SUSE AI in the context of a specific use case. It provides step-by-step instructions to set up a minimal SUSE AI stack on a K3s cluster using Rancher Fleet and the SUSE Application Collection, including an MCP server and Open WebUI.
Follow the cluster setup: create namespaces and secrets for the SUSE Application Collection, deploy cert-manager and Rancher Fleet via Helm. Then apply a GitRepo configuration (suseai.yaml) to deploy the SUSE AI stack with a Kubernetes MCP server. Finally, configure Open WebUI’s “Tools Servers” (e.g., http://mcp-service.suseai.svc.cluster.local:8000/kubernetes) and enable the tool for a model.
You need a Kubernetes cluster (K3s is used in the guide), credentials for the SUSE Application Collection (username and token), and Helm installed to deploy cert-manager and Rancher Fleet.
Open a browser and go to `http://localhost:8000`. Click on the `kubernetes` link. Authorize using the token `top-secret` and then use the "try out" option to test queries.
In Open WebUI admin settings, under Tools, add a new tool server with the URL `http://mcp-service.suseai.svc.cluster.local:8000/kubernetes`. Then enable "Function Calling" to "native" and select the tool for the model you want to use.
All components are deployed inside the local K3s cluster. Secrets are created from the SUSE Application Collection token. No external data is pulled beyond the Helm charts and container images from the Application Collection.
The MCP server uses HTTP (port 8000). Authentication is token-based; the example token is `top-secret` (configured via the authorize button in the web UI).
Painless E2E Automation for Mobile and Web

See and control a real Windows PC you own — from any MCP client, locally or remotely. Observe (UIA + screenshots), click/type/drag/scroll, launch apps, owner Live View. BYOH: your machine, your key.
YC (S26) | Open Computer History | Continuously record your company computer work, map your workflows, help you find work worth automating, and power your agents' context
AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents
🚀 The fast, Pythonic way to build MCP servers and clients.
Comments