Copy the server address.
In TidyPayouts, open Settings → Security & workspace → Connect AI assistants. Your server address is shown there with a copy button, next to the apps and tokens you have already approved.
TidyPayouts ships its own MCP server, so ChatGPT, Claude, Cursor and other assistants can look up payouts, reports, VAT checks and store health in your workspace. Read-only by default, with every lookup on the record.
Real workspace data —
not the model’s imagination.
| Ask your assistant | Where the answer comes from |
|---|---|
| “What did each store pay out this month?” | Your payout list, newest first, in each payout’s own currency. |
| “What’s inside this payout before it’s posted?” | The posting preview: totals, mapped lines, costs and open issues. |
| “Where did the money in this payout go?” | A breakdown of the payout by category. |
| “How did each channel perform last quarter?” | Profit-and-loss style analytics for a date range, by channel or store. |
| “Any VAT evidence problems this period?” | The VAT summary and its list of exceptions that need attention. |
| “Is every store still reporting on time?” | Connection status and report freshness per store. |
| “Is QuickBooks still connected?” | Connection state and when authorization expires. |
| “What happened with this order?” | An exact order or SKU lookup in your workspace. |
Lists are capped to reasonable sizes, results contain your records and never credentials, and the assistant only sees the workspaces you approved when it connected.
Set it up once.
Approve it deliberately.
In TidyPayouts, open Settings → Security & workspace → Connect AI assistants. Your server address is shown there with a copy button, next to the apps and tokens you have already approved.
Claude: Settings → Connectors → Add custom connector. ChatGPT: turn on Developer mode, then create a connector (available on some plans). Claude Code: claude mcp add, then run /mcp and choose Authenticate.
A TidyPayouts page opens. Sign in, tick the workspaces the assistant may read and allow read-only access. The connection uses OAuth with PKCE, so there is no token to copy into the assistant.
In a chat with your assistant, ask about payouts, VAT exceptions or store health. Each lookup runs inside your workspace’s permissions and writes a record to its activity.
What an assistant may do
is enforced by TidyPayouts, not the chat.
Each tool call writes an activity entry naming the tool and client — never your arguments or results — so a review of who-saw-what stays answerable.
Results are capped and come back as explicit fields. Amounts arrive in the payout’s own currency, ready to compare with the source report.
The Model Context Protocol is an open standard that lets AI assistants call approved tools on another system. TidyPayouts speaks it at its own MCP endpoint, with read-only lookups by default.
Claude on web and desktop through custom connectors, ChatGPT through developer-mode connectors (available on some plans only), Claude Code, Cursor and other clients that speak MCP over HTTP. For clients that cannot sign in with OAuth, you can create a personal access token in Settings instead.
Not by default. A connection is read-only unless you tick Allow limited changes, and even then each change is previewed first and applied only with a fresh confirmation token and a written reason. Posting payouts and sending to QuickBooks are never available to assistants.
No. Connections use an OAuth sign-in that you approve, tokens are stored only as hashes, and tool results contain your records — never credentials. You can revoke an app or token in Settings at any time and it stops working immediately.
Connect an assistant, approve the workspaces, keep the guardrails on.
Join the free beta →Free during beta. No credit card.