The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Talos MCP Server listing page.
A Model Context Protocol server for Talos Linux cluster operations — one thin tool, typed actions, zero runtime dependencies.
Companion to virtualbox-mcp-server: that server provisions the nodes, this one turns them into a Kubernetes cluster.
One tool (talos) with typed actions for the cluster hot path — no CLI syntax needed:
| Action | Does |
|---|---|
gen_config | Generate cluster config + talosconfig (cluster, endpoint, optional output_dir) |
apply_config | Apply machine config to a node (node, file, insecure for maintenance mode) |
bootstrap | Bootstrap etcd on the control plane (once per cluster) |
kubeconfig | Retrieve the cluster kubeconfig |
health | Cluster health validation |
config_merge | Merge a talosconfig context (never overwrites ~/.talos/config) |
version | Client or node version |
run | Raw talosctl argv for the long tail (etcd, logs, reboot, upgrade…) |
resolve | Report platform/install state without downloading or running |
Backend: talosctl — the official gRPC client of the Talos machine API. An existing PATH install is always preferred; otherwise the correct binary for the host's OS/architecture is auto-installed from the official Sidero release, verified against GitHub's asset digest.
The full cluster recipe ships to clients in the MCP initialize handshake, so a fresh session can bring up a cluster without external knowledge.
None beyond a hypervisor for the nodes. The server is a single Go binary; talosctl is auto-installed if absent.
Published on the official MCP Registry
as io.github.bryanjbelanger/talos-mcp-server — that name is what
registry-aware clients install by
(current entry).
For hosts that support MCP Bundles, download the .mcpb from the
latest release
and open it. One bundle covers every platform; it carries a binary per
(os, arch) and picks one at startup. The server needs no configuration —
guest credentials and endpoints are per-call parameters, and talosctl is
auto-installed on first use if the host has none.
Otherwise take the bare binary for your platform from the same release, or build it:
Verify with claude mcp list (✔ Connected), then restart the session.
skills/talos-cluster — the end-to-end procedure: provision nodes via the virtualbox MCP server, configure and bootstrap via this one. Install by copying (or symlinking) into ~/.claude/skills/.
MIT