Skip to main content
Welcome — this lesson walks through the KAgent web UI and the default configuration that exposes agents, models, tools, and MCP servers. You’ll learn how KAgent maps user queries to tools, where to manage LLM providers and models, and where to add integrations (MCP servers) and tools for richer automation on Kubernetes.

Home screen and agents (what you’ll see first)

The home screen lists the agents available in your KAgent installation. In this demo, all built-in agents are enabled (Argo Rollouts, Istio, Helm, Kubernetes/k8s, observability, etc.). Note that the exact set of agents depends on the KAgent version and any custom components you installed. For this lesson we’ll use the Kubernetes (k8s) agent as the primary example to interact with a cluster. From the Agents list you can open an agent, type natural-language queries (for example, “list pods in the kagent namespace”), and let the agent evaluate the request. The agent determines the appropriate tool to call, runs it, and returns the result.
A dark-themed screenshot of an AI agent interface where the user asks for the list of pods in the "kagent" Kubernetes namespace and a k8s_get_resources tool call is shown as completed. The right sidebar lists various Kubernetes actions and tools available to the agent.

How agents choose tools and show results

The right-hand tools panel displays the Kubernetes actions available to that agent. When you ask a question, the agent matches the intent to one or more tools (for example k8s_get_resources) and executes them. The result is presented in the chat or a console-style output. Example output for listing pods:
• istio-agent-7b54a0bda-r-m8m1w (Running)
• k8s-agent-dcc57cd87-7vzsg (Running)
• kagent-controller-6f546c65bd-ckk6s (Running)
• kagent-grafana-mcp-597df4c7f4-gvjvf (Running)
• kagent-kmcp-controller-manager-86b48b656d-qz4hl (Running)
• kagent-querydoc-7dc78dc9d7-bcjcz (Running)
• kagent-tools-6d6695c5-7txp7 (Running)
• kagent-ui-5757fccb58-bsbbc (Running)
• kgateway-agent-6fbb9c8d87-dxmd4 (Running)
• observability-agent-749d568fb6-dnxpp (Running)
• promql-agent-5d6c7c76cb-kpqxc (Running)

LLM Providers and Models (configure from the UI)

Each agent can be wired to one or more LLM providers and models. In this demo the configured provider is OpenAI, but you can add additional providers and models via the UI or by using configuration code if you prefer.
  • Use the Models page to add providers, set model names, and provide authentication (API keys, tokens).
  • The Create workflow in the UI lets you create new agents and assign models/providers to them.
A dark-themed web UI titled "Create New Model" on a site branded "kagent," showing form fields for name, namespace, provider & model. The page also includes an Authentication section with an API key input.

Tools Library (what agents call to act)

Tools are the execution primitives agents call to interact with external systems (Kubernetes API, Helm, Argo, observability backends, etc.). KAgent ships with a default set of tools organized into categories. The Tools Library shows available categories and individual tool actions; these entries are what agents select when handling a query.
  • Tools are extendable — you can add custom tools or MCP-based tool servers.
  • Typical categories: Kubernetes (k8s), Helm, Argo, Datetime, Networking, Observability, and provider-specific integrations.
A dark-themed web UI showing a "Tools Library" for "kagent" with a search bar and expandable tool categories (Argo, Cilium, Datetime, Helm, etc.). Individual tool entries like "datetime_get_current_time" and "helm_get_release" are listed with brief descriptions.

MCP Servers (integrations and server endpoints)

MCP Servers are service integrations that provide additional functionality and tool endpoints for agents. The default deployment includes several MCP servers; you can add more (for example, cloud service integrations or custom tool servers) from the MCP Servers page.
  • MCP Servers expose new tool capabilities and can host specialized tooling that agents call.
  • You can register, configure, and remove MCP server entries in the UI.
A dark-themed kagent dashboard showing an "MCP Servers" list. It displays three server entries (kagent-grafana-mcp, kagent-querydoc, kagent-tool-server) and a purple "Add MCP Server" button.

Quick reference: UI pages and their purposes

PagePurposeTypical actions
AgentsManage and interact with agentsOpen an agent, send queries, view tool calls
ModelsConfigure LLM providers and modelsAdd provider, set model name, add API keys
Tools LibraryInspect available tools and categoriesSearch tools, view descriptions, add custom tools
MCP ServersRegister integrations and tool backendsAdd MCP server, configure endpoints and auth

Next steps

  • Create a new agent and attach a model via the Create workflow.
  • Add or configure LLM providers on the Models page.
  • Explore the Tools Library and enable or add tools your agents need.
  • Register additional MCP servers to extend capabilities (e.g., cloud services, observability).
Note: The exact agents, tools, and MCP servers available in your KAgent installation depend on the version and the components you installed. The UI lets you extend and customize these elements.
That completes the high-level UI and default configuration overview. In the next lesson we’ll create and configure an agent end-to-end, wire it to a model, and add a custom tool to extend behavior.

Watch Video