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

# Operation commands

> Every command the Snow Doughnut MCP exposes: what it runs, an example prompt, what it reads, and what comes back. Ask in your own words and your AI picks the command.

Each command runs one of this knowledge base's processes against your filled workbooks. You don't have to name a command; ask in your own words and your AI matches the request, the same way [skills](https://docs.snowdoughnut.com/skills-overview.md#how-a-skill-gets-picked-up) get picked up. Name one directly when you want to be certain.

Every command follows the same four rules:

* It reads your filled copies, from the locations recorded at [setup](https://docs.snowdoughnut.com/mcp-setup.md), never the blank workbooks on this site.
* A missing value is a question back to you, recorded in your dictionary once you answer. No command invents one.
* It decides and records; execution runs through your own connected tools. See [what this framework covers](https://docs.snowdoughnut.com/what-this-framework-covers.md#the-split).
* It talks in short turns: quick picks in a multiple-choice dialog, up to four at a time, with options from your own lists; anything only you can answer in chat; a one-line confirmation, then the work. The contract is [how the MCP talks](https://docs.snowdoughnut.com/mcp-conversation.md).

## Setup and context

| Command | Example prompt | What it does |
| :- | :- | :- |
| `setup_snowdoughnut` | "Set up Snow Doughnut" | Walks the [setup path](https://docs.snowdoughnut.com/overview.md): locations, dictionaries, the [schedule register](https://docs.snowdoughnut.com/reporting-cadence.md), [standing rules](https://docs.snowdoughnut.com/glossary.md#standing-rule), and creator defaults. Resumable |
| `get_context` | Runs before any task | Returns your tools, locations, setup, and framework version, so every other command works against your own copies |
| `whats_new` | "Any framework updates?" | Compares your recorded framework version against the current one and lists what changed |

## Naming and tracking

| Command | Example prompt | Runs |
| :- | :- | :- |
| `name_this` | "Name my new Meta prospecting campaign for Glacier Boots" | [Name something](https://docs.snowdoughnut.com/name-something.md) and the three [naming conventions](https://docs.snowdoughnut.com/naming-conventions-overview.md), assembled from your dictionaries |
| `build_utms` | "Tag this URL for that campaign" | [UTM standards](https://docs.snowdoughnut.com/utm-standards.md), one tagged URL per ad set, joined to the names above |

## Briefs and checks

| Command | Example prompt | Runs |
| :- | :- | :- |
| `create_brief` | "Start a campaign brief for the spring push" | The [campaign](https://docs.snowdoughnut.com/campaign-brief-process.md), platform, [copy](https://docs.snowdoughnut.com/copywriting-process.md), [creative](https://docs.snowdoughnut.com/creative-brief-process.md), [article](https://docs.snowdoughnut.com/article-process.md), or [landing page](https://docs.snowdoughnut.com/landing-page-process.md) brief process, drafted from your libraries for the [owner](https://docs.snowdoughnut.com/glossary.md#owner) to approve |
| `run_checklist` | "Pre-launch check this campaign" | The matching [checklist](https://docs.snowdoughnut.com/campaign-launch-checklist.md): the rule checks run and reported, the [human-eyes rows](https://docs.snowdoughnut.com/meta-pre-launch-checklist.md) listed for a person to clear |
| `log_experiment` | "Register this test" | [Creating an experiment](https://docs.snowdoughnut.com/creating-an-experiment.md): the ID, the log row, the names, and the scheduled guardrail watch |

## Reporting

| Command | Example prompt | Runs |
| :- | :- | :- |
| `fill_flat_file` | "Log yesterday's numbers" | The [daily fill](https://docs.snowdoughnut.com/flat-file-template.md#daily-fill-and-restatement): one dated row per metric, per channel, per grain you store, estimates flagged and restated, the file's checks run |
| `build_report` | "Make this week's report" | The [reporting process](https://docs.snowdoughnut.com/report-on-results.md) for any cadence, from the [daily brief](https://docs.snowdoughnut.com/daily-brief.md) to the [annual review](https://docs.snowdoughnut.com/yearly-reporting-process.md), drafted for the approver the register names |

## Maintenance

| Command | Example prompt | Runs |
| :- | :- | :- |
| `run_maintenance` | "Run the article sweep" | The [article maintenance](https://docs.snowdoughnut.com/article-maintenance-process.md) and [content calendar](https://docs.snowdoughnut.com/content-calendar-process.md) passes: what's due, the checks, and a triage or exceptions list for the owner to rule on |

## Commands on a schedule

Every [scheduled pass](https://docs.snowdoughnut.com/glossary.md#scheduled-pass) in this knowledge base is one of these commands on a timer: `fill_flat_file` each morning, `build_report` on the register's days, `run_checklist` at +1 hour, +48 hours, and weekly on a live campaign, `run_maintenance` monthly, and the guardrail watch from `log_experiment` until a test's end date. Set the schedules once during [setup](https://docs.snowdoughnut.com/mcp-setup.md) and the commands run without being asked, with results going to the owner the register names.

## Related resources

* [**Set up the MCP**](https://docs.snowdoughnut.com/mcp-setup.md) Connect the server and run onboarding.
* [**Snow Doughnut MCP**](https://docs.snowdoughnut.com/mcp-overview.md) What the MCP does and never does.
* [**Reporting cadence**](https://docs.snowdoughnut.com/reporting-cadence.md) Where the schedules live.
* [**Glossary**](https://docs.snowdoughnut.com/glossary.md) Owner, builder, creator, standing rule, scheduled pass.

> [accordion] MCP wiring
>
> **Type:** mcp\
> **Domains:** mcp\
> **Provides:** `mcp-commands`\
> **Uses:** `article-brief`, `campaign-brief`, `checklist-prelaunch`, `copy-brief`, `creative-brief`, `experiment-log`, `flat-file`, `landing-page-brief`, `naming-convention`, `process:article-maintenance`, `report-template`, `reporting-cadence`, `utm-rules`


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.