io.github.bryanjbelanger/talos-mcp-server
Talos Linux cluster operations as one thin MCP tool over the official machine API.
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
https://github.com/bryanjbelanger/talos-mcp-server/releases/download/v1.1.2/talos-mcp-server-1.1.2.mcpbDocumentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
Contents
Talos MCP Server
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.
Design
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.
Prerequisites
None beyond a hypervisor for the nodes. The server is a single Go binary; talosctl is auto-installed if absent.
Installing
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:
go build -o talos-mcp-server .Registration with Claude Code
claude mcp add --scope user talos -- /path/to/talos-mcp-serverVerify with claude mcp list (✔ Connected), then restart the session.
Bundled skill
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/.
License
MIT
Frequently asked questions
What is io.github.bryanjbelanger/talos-mcp-server?
Talos Linux cluster operations as one thin MCP tool over the official machine API.
How do I install io.github.bryanjbelanger/talos-mcp-server?
Follow the installation steps in its documentation, shown on this page and in its repository.
Does io.github.bryanjbelanger/talos-mcp-server need an API key?
Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.
Is io.github.bryanjbelanger/talos-mcp-server open source?
Its code is public on GitHub, but the repository does not declare a standard license.
Who maintains io.github.bryanjbelanger/talos-mcp-server?
It is published by bryanjbelanger. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.