[See what's new in the\
\
Kick Changelog](/content/changelog/index.html)

For the complete documentation index, see [llms.txt](https://docs.kick.co/llms.txt). This page is also available as [Markdown](https://docs.kick.co/ai/mcp/mcp-use-case-library/mcp-example-workflows.md).

**Tip:** Default to read-only. When a workflow writes data, ask for a preview first and confirm before applying. The prompts in this article are phrased that way; keep that pattern when adapting them.

## How to read this page

Every workflow is tagged in its title so you know what it touches before you open it:

- _Read-only_: looks things up, never changes Kick.
- _Read first, then writes_: starts as a lookup; writes only after you approve a preview.
- _Writes to Kick_: uses a write tool. Always preview and confirm before applying.

A label that says "multi-step" spans several prompts or turns, or builds a reusable artifact.

Hover a prompt and click the copy icon to paste it into your assistant. Use **Ask → Open in Claude** or **Open in ChatGPT** (top right) to load the full page as context.

You can ask the assistant to do more than run one prompt. It can chain steps, build a reusable artifact (a checklist, a Q&A sheet), save a sequence as a routine, or draft a skill. See [Routines & artifacts](https://docs.kick.co/ai/mcp/mcp-use-case-library/mcp-example-workflows#routines--artifacts) below.

## Start here

New to Kick MCP? Begin with these read-only single prompts, then explore the sections below.

- **Find the right client context:** confirm which workspace you are in (see [Daily ops](https://docs.kick.co/ai/mcp/mcp-use-case-library/mcp-example-workflows#daily-ops)).
- **Pull reports for review:** get a P&L or balance sheet (see [Close](https://docs.kick.co/ai/mcp/mcp-use-case-library/mcp-example-workflows#close)).
- **Review transactions that need attention:** triage a period (see [Daily ops](https://docs.kick.co/ai/mcp/mcp-use-case-library/mcp-example-workflows#daily-ops)).

## Daily ops

**Workspace context snapshot** _(read-only)_ 
```
Give me a one-screen snapshot of the Acme LLC workspace: entities, connected accounts, uncategorized count, unmatched transfers, open tasks, and most recent activity. Confirm this is the right workspace before we proceed.
```

A faster orientation than listing workspaces by name. Use it at the start of a session.

**Find the right client context** _(read-only)_ 
```
List the Kick workspaces I can access, then help me find the one for Acme LLC and confirm we are in the right place before using any other tools.
```

Use this when you are switching between clients or checking whether the assistant is using the right workspace.

**Daily triage across clients** _(read-only)_ 
```
Across all my workspaces, which clients are at risk of missing close this month? Show the workspace, the uncategorized count, the unmatched-transfer count, and the date of the most recent meaningful change.
```

**Review transactions that need attention** _(read-only)_ 
```
In the active workspace, find January 2026 transactions that need bookkeeping review. Limit the first result to 25 rows. Group your summary by likely follow-up: missing category, unclear counterparty, possible transfer, or needs client context.
```

Ask for source data before acting:
```
For each item, include the transaction id, date, amount, counterparty, and bank description.
```

**Account health check (across workspaces)** _(read-only)_ 
```
Across every workspace I can access, list connected financial accounts and flag any with no transactions in the last 14 days or a sharp volume drop vs. the prior month. Return one table: workspace, account, last-activity signal, this-month vs. last-month count, sorted most stale first.
```

**Document backlog** _(read first, then writes)_ 
```
In the Acme LLC workspace, list documents uploaded in the last 30 days that aren't yet matched to a transaction. Group by document category, entity, and account, and flag any that aren't reconciled. Include the file name, upload date, and period for each.
```
Then match the oldest, and stop before linking:
```
For the five oldest unmatched documents, use each document's period and account to search transactions in that account within the period (±5% on any extracted amount), rank candidate matches, and stop before linking.
```
Note: filename search does not read document contents. Match on period, account, and amount, not vendor text.

**Task follow-up queue** _(read first, then writes)_ 
```
List open tasks in the Acme LLC workspace due this week. For each bookkeeping-related task, summarize the underlying issue and whether the related transactions are still unresolved.
```
Then stage a new task and stop before confirming:
```
Prepare a task preview: "Follow up with client on Stripe: $1,240 on Jan 15" linked to transaction T-4821. Stop before confirming.
```

## Close

**Pull reports for review** _(read-only)_ 
```
Pull the January 2026 P&L for entity 123 on a cash basis. Summarize the largest expense categories and list three questions I should ask the client.
```
For a deeper review:
```
Compare the January 2026 P&L, balance sheet, and trial balance for entity 123. Point out accounts that changed materially from the previous month and include the report source for each observation.
```

**Run a period-end sweep** _(read-only)_ 
```
For the Acme LLC workspace and the period Jan 1 through Jan 31, 2026, list: every uncategorized transaction, every unmatched transfer, every transaction over $5,000 without a memo, and any vendor that first appeared this period. Group the results and include source IDs.
```
To reconcile against an external source:
```
Compare the opening balances in the Acme LLC workspace against the attached trial balance. List every account where the balances diverge, with both values shown side by side. Do not change any data.
```

**Cash flow vs. P&L sanity check** _(read-only)_ 
```
For entity 123 and Q1 2026, compare net income (P&L) to operating cash flow. List the biggest reconciling items (AR/AP, transfers, owner draws, loan principal).
```

## Investigation

**Inspect activity before changing anything** _(read-only)_ 
```
Show recent activity related to transaction category changes. Summarize who made the changes, when they happened, and whether any batch looks worth reviewing before close.
```

**Unwind a change after review** _(writes to Kick, multi-step)_ 
```
Pull the activity log for the bulk update on Jan 12 that touched 84 transactions. Show what changed for each: the before and after state. Then prepare to revert that batch and stop before applying. I will confirm.
```
For a single transaction:
```
Show the full edit history for transaction T-4821. List every change with the user, timestamp, and the previous and new values for each field.
```

**Why did Kick categorize this?** _(read-only)_ 
```
For transaction T-4821, explain how it got its current category, class, and counterparty. Check applied rules, similar transactions, and recent edits. List what would change if I recategorized it to Office Supplies.
```

**Account drill-down after a report surprise** _(read-only)_ 
```
P&L shows Software Subscriptions up 60% month over month. Pull account transactions for January 2026, group by counterparty, identify the three largest drivers, and for each tell me whether it came from a bank import, a rule, or a manual JE.
```

## Cleanup & scale

**Audit and tune the Chart of Accounts** _(read first, then writes)_ 
```
In the active workspace, list each account and category with the number of transactions posted to it in the last ninety days. Flag entries with zero recent usage and note whether each looks safe to disable.
```
For a structural change, request a preview before any write:
```
Prepare to create a new Long-Term Liability account named SBA Loan and reclassify the historical loan transactions for First National Bank into it. Show the count of affected transactions, the date range, and the proposed account hierarchy. Stop before writing.
```

**Clean up counterparties and classes** _(read first, then writes)_ 
```
List counterparties in the active workspace that look like duplicates of Amazon. Show the variants, the transaction count for each, and the merge target you would pick. Do not merge yet.
```
```
Which classes have fewer than five transactions this year? List each with its transaction count and propose which ones to retire.
```
Once you have reviewed the proposal, authorize the merge:
```
Prepare to merge the counterparty variants you listed above into a single counterparty named Amazon. Show the final transaction count and stop before confirming.
```

**Build and tune rules** _(read first, then writes)_ 
```
I want a rule that categorizes Gusto payouts as Payroll and assigns class = Operations. Show me which existing transactions would have matched if this rule had been in place. Stop before creating the rule.
```

## Routines & artifacts

These chain multiple steps, run across turns, or produce a reusable artifact, routine, or skill.

**Monthly close checklist artifact** _(read-only, multi-step)_ 
```
For the Acme LLC workspace and January 2026, run a full close-readiness pass: uncategorized, unmatched transfers, transactions over $5,000 without a memo, accounts with material month-over-month swings, and open tasks. Then build an interactive close checklist artifact I can re-run: each row is a check, its current count, the drill-down query behind it, and a status I can tick off.
```

Make it durable:
```
Save the exact sequence of MCP calls you just used as a named routine "Monthly Close: Acme LLC" so I can re-run it next period.
```

**Client Q&A loop** _(read first, then writes)_ 
```
Find this month's transactions needing client input. For each, gather id, date, amount, account, and current best-guess category. Build a client-ready Q&A artifact: one plain-English question per item, grouped by client, with a blank "client answer" column. Don't change any Kick data. I'll paste answers back next turn.
```

Next turn, close the loop:
```
Here are the client's answers. Map each to the right category/class, show me one combined bulk-update preview, and stop before applying.
```

**Report-surprise investigation artifact** _(read-only, multi-step)_ 
```
Pull the January 2026 P&L for entity 123. Take the three accounts with the biggest month-over-month change, drill into each account's transactions, identify the top drivers, and attribute each to a bank import, a rule, or a manual JE. Build a one-page "what moved and why" artifact with a sources column.
```

## Final Notes

This content is a structured overview of workflows in Kick's system designed for financial reporting and bookkeeping processes.