Talos Mcp Server

io.github.bryanjbelangerPublished by GitHub account bryanjbelangerv1.1.2Updated Oct 24, 2026

Talos Linux cluster operations as one thin MCP tool over the official machine API.

VerifiedSTDIODesktop onlyCloud & InfrastructureDeveloper Tools

Overview

AI-generated overview

A local MCP server that lets an assistant generate configs, apply them, bootstrap etcd and check health on Talos Linux clusters via talosctl.

What you can do
Generate cluster config and talosconfig, and merge talosconfig contexts without overwriting the default config file. Apply machine config to a node, including maintenance mode, and bootstrap etcd on the control plane. Retrieve the cluster kubeconfig and validate cluster health. Report client or node versions and platform/install state without downloading or running anything. Run raw talosctl arguments for the long tail, such as etcd, logs, reboot and upgrade.
When to use it
Useful when bringing up or operating a Talos Linux Kubernetes cluster from an assistant session, especially alongside a hypervisor server that provisions the nodes. It suits users who want typed cluster actions instead of remembering talosctl syntax.
Requirements
Runs as a local process on the desktop; a single Go binary or MCP bundle, with no declared environment variables or authentication. talosctl is used as the backend: an existing PATH install is preferred, otherwise the matching binary is auto-installed from the official release. Guest credentials and endpoints are passed per call. A hypervisor is needed for the nodes.
Before you install
Actions change real infrastructure: applying machine config, bootstrapping etcd and raw talosctl commands such as reboot or upgrade can alter or disrupt a cluster. The server may download and install talosctl from the internet on first use. Cluster credentials and endpoints are supplied per call, so handle them carefully.

Installation

In SourceWeft

  1. Open Talos Mcp Server in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

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:

ActionDoes
gen_configGenerate cluster config + talosconfig (cluster, endpoint, optional output_dir)
apply_configApply machine config to a node (node, file, insecure for maintenance mode)
bootstrapBootstrap etcd on the control plane (once per cluster)
kubeconfigRetrieve the cluster kubeconfig
healthCluster health validation
config_mergeMerge a talosconfig context (never overwrites ~/.talos/config)
versionClient or node version
runRaw talosctl argv for the long tail (etcd, logs, reboot, upgrade…)
resolveReport 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:

bash
go build -o talos-mcp-server .

Registration with Claude Code

bash
claude mcp add --scope user talos -- /path/to/talos-mcp-server

Verify 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

Source: README.md at commit 5fb6e38

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.1.2LatestSep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.