{
  "markdown": "# Talos MCP Server\n\nA Model Context Protocol server for [Talos Linux](https://www.talos.dev) cluster operations — one thin tool, typed actions, zero runtime dependencies.\n\nCompanion to [virtualbox-mcp-server](https://github.com/bryanjbelanger/virtualbox-mcp-server): that server provisions the nodes, this one turns them into a Kubernetes cluster.\n\n## Design\n\nOne tool (`talos`) with typed actions for the cluster hot path — no CLI syntax needed:\n\n| Action | Does |\n|---|---|\n| `gen_config` | Generate cluster config + talosconfig (`cluster`, `endpoint`, optional `output_dir`) |\n| `apply_config` | Apply machine config to a node (`node`, `file`, `insecure` for maintenance mode) |\n| `bootstrap` | Bootstrap etcd on the control plane (once per cluster) |\n| `kubeconfig` | Retrieve the cluster kubeconfig |\n| `health` | Cluster health validation |\n| `config_merge` | Merge a talosconfig context (never overwrites `~/.talos/config`) |\n| `version` | Client or node version |\n| `run` | Raw `talosctl` argv for the long tail (etcd, logs, reboot, upgrade…) |\n| `resolve` | Report platform/install state without downloading or running |\n\n**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.\n\nThe full cluster recipe ships to clients in the MCP initialize handshake, so a fresh session can bring up a cluster without external knowledge.\n\n## Prerequisites\n\nNone beyond a hypervisor for the nodes. The server is a single Go binary; `talosctl` is auto-installed if absent.\n\n## Installing\n\nPublished on the [official MCP Registry](https://registry.modelcontextprotocol.io)\nas `io.github.bryanjbelanger/talos-mcp-server` — that name is what\nregistry-aware clients install by\n([current entry](https://registry.modelcontextprotocol.io/v0/servers?search=io.github.bryanjbelanger/talos-mcp-server&version=latest)).\n\nFor hosts that support MCP Bundles, download the `.mcpb` from the\n[latest release](https://github.com/bryanjbelanger/talos-mcp-server/releases/latest)\nand open it. One bundle covers every platform; it carries a binary per\n(os, arch) and picks one at startup. The server needs no configuration —\nguest credentials and endpoints are per-call parameters, and `talosctl` is\nauto-installed on first use if the host has none.\n\nOtherwise take the bare binary for your platform from the same release, or\nbuild it:\n\n```bash\ngo build -o talos-mcp-server .\n```\n\n## Registration with Claude Code\n\n```bash\nclaude mcp add --scope user talos -- /path/to/talos-mcp-server\n```\n\nVerify with `claude mcp list` (`✔ Connected`), then restart the session.\n\n## Bundled skill\n\n[`skills/talos-cluster`](skills/talos-cluster/SKILL.md) — 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/`.\n\n## License\n\nMIT\n",
  "bytes": 3021,
  "sha": "31ee1adc613d18a852eb91c97e5fa3cc7961c27d1e5e2dc13c99489b49aa8d14",
  "repo_slug": "bryanjbelanger/talos-mcp-server",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_bryanjbelanger_talos_mcp_serve_94caa269/readme"
}