MCP server for Talos Linux API integration - manage clusters with AI
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"talos-mcp-server-2","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# Talos MCP Server Talos MCP Server runs as a Python stdio server. It calls a pinned talosctl binary. The server does not connect to Talos through a separate Python gRPC client. Version 0.4.1 includes diagnostic warning fixes and dependency maintenance after the 0.4.0 breaking repair release. Its default profile is readonly. A separate write profile enables standalone operations when the operator supplies suitable Talos credentials. An exact tool allowlist can restrict either profile. ## Install a reviewed build Use Python 3.10 or newer. Install a talosctl release that matches the Talos minor version on the node. This repository pins the default CLI release in .talosctl-version and records official release checksums in talosctl-checksums.txt. Install a reviewed wheel into a dedicated environment: ~~~sh uv build --wheel python3 -m venv /opt/talos-mcp/venv /opt/talos-mcp/venv/bin/python -m pip install dist/talos_mcp_server-0.4.1-py3-none-any.whl /opt/talos-mcp/venv/bin/talos-mcp-server --version ~~~ The package version is static metadata. A source checkout needs an editable install or a rebuilt wheel after code changes. A wheel install includes Python dependencies. Install talosctl separately and supply its absolute path with --talosctl. The server can start without a Talos configuration file. In that state, talos_config_info, offline validation, and talos_version with client_only=true work. Authenticated node tools return CONFIG_REQUIRED. Set --talosconfig and, if needed, --context for cluster calls. The CLI uses that context for the server lifetime and passes it to each authenticated child. ## Dependency maintenance in 0.4.1 The repository lock includes security updates for the 41 advisories in the [initial triage](https://github.com/CBEPX/talos-mcp-server/blob/v0.4.1/docs/security/dependency-triage-20261024.md) and two additional advisories in the [dependency graph follow-up](https://github.com/CBEPX/talos-mcp-server/blob/v0.4.1/docs/security/dependency-f…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.