> ## Documentation Index
> Fetch the complete documentation index at: https://docs.siderolabs.com/llms.txt
> Use this file to discover all available pages before exploring further.

# AI Agent Integration

> Integrate Talos and Omni documentation with AI agents using llms.txt, skill.md, or MCP.

export const VersionWarningBanner = () => {
  const latestVersion = "v1.13";
  const [latestUrl, setLatestUrl] = useState(null);
  const [currentVersion, setCurrentVersion] = useState(null);
  const [isBeta, setIsBeta] = useState(false);
  const parseVersion = v => v.replace("v", "").split(".").map(Number);
  const isGreaterVersion = (a, b) => {
    const [aMajor, aMinor] = parseVersion(a);
    const [bMajor, bMinor] = parseVersion(b);
    if (aMajor > bMajor) return true;
    if (aMajor === bMajor && aMinor > bMinor) return true;
    return false;
  };
  useEffect(() => {
    if (typeof window === "undefined") return;
    const {pathname, hash, search} = window.location;
    const match = pathname.match(/\/talos\/(v\d+\.\d+)\//);
    if (!match) return;
    const detectedVersion = match[1];
    if (detectedVersion === latestVersion) return;
    setCurrentVersion(detectedVersion);
    if (isGreaterVersion(detectedVersion, latestVersion)) {
      setIsBeta(true);
    }
    const newPath = pathname.replace(`/talos/${detectedVersion}/`, `/talos/${latestVersion}/`);
    setLatestUrl(`${newPath}${search}${hash}`);
  }, []);
  if (!latestUrl || !currentVersion) return null;
  return <div className="not-prose sticky top-6 z-50 my-6">
      <div className="border border-yellow-500/30 bg-yellow-500/10 px-4 py-3 rounded-xl">
        <div className="text-sm">
          {isBeta ? <>
              ⚠️ You are viewing a <strong>beta version</strong> of Talos ({currentVersion}).
              This version may be unstable.
              <a href={latestUrl} className="ml-2 underline text-yellow-400 hover:text-yellow-300 font-medium">
                View latest stable version {latestVersion} →
              </a>
            </> : <>
              ⚠️ You are viewing an older version of Talos ({currentVersion}).
              <a href={latestUrl} className="ml-2 underline text-yellow-400 hover:text-yellow-300 font-medium">
                View the latest version {latestVersion} →
              </a>
            </>}
        </div>
      </div>
    </div>;
};

<VersionWarningBanner />

SideroLabs publishes machine-readable documentation metadata that allows AI agents and developer tools to understand Talos Linux and Omni capabilities programmatically.

These integration points can be used by agent frameworks, MCP-compatible tools, IDE extensions, or custom automation.

## Available integration endpoints

Depending on your tooling and integration model, you can use one or more of the following endpoints.

### The `llms.txt` file

The `llms.txt` file is a structured documentation index.

It lists all the available documentation pages so agents can discover relevant content before answering questions.

You can see the `llms.txt` file at:

```url theme={null}
https://docs.siderolabs.com/llms.txt
```

### The `skill.md` file

The `skill.md` file is a capability definition that describes supported operations, workflows, architectural constraints, and expected inputs and outputs.

Agents can use this file to understand:

* Supported actions
* Required configuration inputs
* Workflow sequencing
* Operational constraints

You can download the `skill.md` file in your personal Claude skills directory:

```bash theme={null}
mkdir -p ~/.claude/skills/siderolabs
curl -L https://docs.siderolabs.com/skill.md \
  -o ~/.claude/skills/siderolabs/SKILL.md
```

Restart Claude Code after downloading the file.

**Alternatively**, if your agent supports the [Skills CLI](https://www.npmjs.com/package/skills), you can install the skill using:

```bash theme={null}
npx skills add https://docs.siderolabs.com
```

This command loads the SideroLabs capability definition into the agent’s context.

### MCP endpoint

SideroLabs exposes its documentation through a remote Model Context Protocol (MCP) server.

This enables MCP-compatible clients to query the documentation dynamically using the standard MCP interface.

To connect, register the following URL as a remote MCP server in your client configuration:

```url theme={null}
https://docs.siderolabs.com/mcp
```

**For example:**

To register the SideroLabs documentation as an MCP server in OpenCode or Claude Code:

<Tabs>
  <Tab title="OpenCode">
    Add the MCP server configuration to your OpenCode config file located at `~/.opencode/opencode.json`:

    ```json theme={null}
    {
      "mcp": {
        "siderolabs-docs": {
          "type": "remote",
          "url": "https://docs.siderolabs.com/mcp",
          "enabled": true
        }
      }
    }
    ```
  </Tab>

  <Tab title="Claude code (user-level configuration)">
    Add the MCP server to your [personal Claude configuration](https://code.claude.com/docs/en/settings#configuration-scopes) file located at `~/.claude.json`:

    ```json theme={null}
    {
      "mcpServers": {
        "siderolabs-docs": {
          "type": "remote",
          "url": "https://docs.siderolabs.com/mcp"
        }
      }
    }
    ```
  </Tab>

  <Tab title="Claude code (project-level)">
    To share the MCP configuration with your team, create or update the `.mcp.json` file in the root of your repository:

    ```json theme={null}
    {
      "mcpServers": {
        "siderolabs-docs": {
          "type": "remote",
          "url": "https://docs.siderolabs.com/mcp"
        }
      }
    }

    ```
  </Tab>
</Tabs>

For other MCP-compatible clients, refer to your client’s documentation for instructions on adding a remote server.