# StackKits Agent Snippets

## Autonomous Basement Kit

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

## Inspect

```bash
stackkit status --json
stackkit verify --http --json
stackkit logs list --json
stackkit compat
```

## MCP Config

```bash
stackkit agent mcp-config --client codex --mode docs,local,server
```

Website discovery:

```text
GET https://stackkit.cc/openmcp.json
OPEN https://stackkit.cc/planner
GET https://stackkit.cc/getting-started/installation-processes.md
```

The Planner's optional v2alpha1 `stackkits_*` WebMCP tools are browser-local and read-only: `stackkits_list_catalog`, `stackkits_get_module_profiles`, `stackkits_assess_capacity`, and `stackkits_prepare_handoff`. They expose CUE facts, compare declared capacity, and prepare, but never execute, the CLI handoff.

Native local connector:

```text
[mcp_servers.stackkit]
command = "stackkit-mcp"
args = ["--mode", "docs,local,server"]
```

Local endpoint exposed by stackkit-server after install:

```text
POST http://localhost:8082/mcp
GET  http://localhost:8082/openmcp.json
```

Protected remote MCP target:

```text
POST https://<protected-target>/mcp
GET  https://<protected-target>/openmcp.json
```

Agents should configure one MCP connection named `stackkit`. Remote MCP is the same connector for installed StackKit day-2 operations through Streamable HTTP. WebSocket would be a custom gateway, not the default StackKits surface.

## Published Prompts

- /getting-started/agents/basekit-autonomous-rollout.md
- /getting-started/agents/inspect-existing-rollout.md
- /getting-started/agents/diagnose-failed-rollout.md
- /getting-started/agents/ssh-rollout.md