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

# stackkit agent

> Agent-native helpers for StackKits automation

Agent-native helpers for StackKits automation.

Agent-native helpers emit install plans, self-checks, prompts, and MCP configuration without mutating a rollout.

```bash theme={null}
stackkit agent [flags]
```

Subcommands: [`stackkit agent install-plan`](#stackkit-agent-install-plan), [`stackkit agent mcp-config`](#stackkit-agent-mcp-config), [`stackkit agent prompt`](#stackkit-agent-prompt), [`stackkit agent self-check`](#stackkit-agent-self-check)

## stackkit agent install-plan

Print a non-interactive StackKits install plan.

```bash theme={null}
stackkit agent install-plan [flags]
```

| Flag       | Type   | Default        | Description                        |
| ---------- | ------ | -------------- | ---------------------------------- |
| `--dir`    | string | `my-homelab`   | Workspace directory                |
| `--json`   | bool   | —              | Emit JSON                          |
| `--kit`    | string | `basement-kit` | StackKit to plan for               |
| `--target` | string | `local`        | Target kind: local, ssh, vm, or ci |

**Examples**

```bash theme={null}
# Print the install steps for a Basement Kit workspace named my-homelab
stackkit agent install-plan

# A Cloud Kit plan for an agent working over SSH, as JSON
stackkit agent install-plan --kit cloud-kit --target ssh --dir my-cloud --json
```

## stackkit agent mcp-config

Print one StackKits MCP client connection config.

Print a ready-to-paste MCP client configuration named "stackkit".

For users this is one StackKits MCP connection. Locally it starts the stackkit-mcp adapter; after install the same connector can also be reached as stackkit-server /mcp when a protected endpoint is explicitly enabled.

```bash theme={null}
stackkit agent mcp-config [flags]
```

| Flag           | Type   | Default                 | Description                              |
| -------------- | ------ | ----------------------- | ---------------------------------------- |
| `--client`     | string | `generic`               | Client format: generic, codex, or claude |
| `--mode`       | string | `docs,local,server`     | MCP modes                                |
| `--server-url` | string | `http://localhost:8082` | stackkit-server URL                      |

**Examples**

```bash theme={null}
# Print the connection as Claude mcpServers JSON
stackkit agent mcp-config --client claude

# Print the Codex config.toml block
stackkit agent mcp-config --client codex
```

## stackkit agent prompt

Print a copy-ready StackKits agent prompt.

```bash theme={null}
stackkit agent prompt [scenario] [flags]
```

| Flag     | Type | Default | Description                     |
| -------- | ---- | ------- | ------------------------------- |
| `--json` | bool | —       | Emit JSON                       |
| `--list` | bool | —       | List available prompt scenarios |

**Examples**

```bash theme={null}
# List the available prompt scenarios
stackkit agent prompt --list

# Print the prompt for diagnosing a failed rollout
stackkit agent prompt diagnose-failed-rollout
```

## stackkit agent self-check

Check local agent-facing StackKits prerequisites.

```bash theme={null}
stackkit agent self-check [flags]
```

| Flag           | Type   | Default                 | Description         |
| -------------- | ------ | ----------------------- | ------------------- |
| `--json`       | bool   | —                       | Emit JSON           |
| `--server-url` | string | `http://localhost:8082` | stackkit-server URL |

**Examples**

```bash theme={null}
# Check that stackkit, stackkit-server, and stackkit-mcp are on PATH
stackkit agent self-check

# The same checks as JSON
stackkit agent self-check --json
```