# StackKits Agent Guide

StackKits is agent-ready through static public docs, deterministic CLI commands, a node-local API surface, one user-facing MCP connection named `stackkit`, and four optional page-side WebMCP planner tools.

Open [the Module Profile Planner](/planner) to choose a StackKit, explicit use-case alternatives, module-local profiles, and user-declared CPU, RAM, and free storage. In a browser with WebMCP, the page registers `stackkits_list_catalog`, `stackkits_get_module_profiles`, `stackkits_assess_capacity`, and `stackkits_prepare_handoff`. They share the visible planner state and are strictly read-only: they expose CUE facts and feasibility, do not recommend a configuration, inspect a host, call a provider, run a command, or apply a plan. A browser without WebMCP uses the same planner normally.

Basement Kit is the supported one-command path, Cloud Kit is preview, and Modern Homelab is an alpha definition archive, not an install target. Standalone Docker Compose is the primary application runtime; Komodo and Coolify are explicit integrations. User-installed apps outside that path are state-unmanaged.

Use `stackkit agent prompt <scenario>` for copy-ready prompts and `stackkit agent mcp-config` for one ready-to-paste `stackkit` MCP connection.

Use [Installation processes](/getting-started/installation-processes.md) to choose between website discovery and planning, full installer, direct CLI, on-server agent, SSH agent, native MCP, and local MCP fallback by configuration/individualization, access options, and automation degree. Website discovery and WebMCP planning are read-only; SSH is the external bootstrap authority; `stackkit-mcp` is the local adapter for the single `stackkit` connection; protected remote `/mcp` is a target day-2 capability after install.

Core autonomous flow:

```bash
stackkit init basement-kit --owner-source=local --non-interactive
stackkit validate
stackkit generate
stackkit plan
stackkit apply
stackkit verify --http --json
```

Do not hand-edit generated rollout artifacts. Change StackSpec, CUE, or Go source, then regenerate.

Published prompts:

- [Autonomous BaseKit rollout](/getting-started/agents/basekit-autonomous-rollout.md)
- [Inspect existing rollout](/getting-started/agents/inspect-existing-rollout.md)
- [Diagnose failed rollout](/getting-started/agents/diagnose-failed-rollout.md)
- [Generate and apply through SSH](/getting-started/agents/ssh-rollout.md)