Connect Collects to Claude
Server URL: https://mcp.collects.io/mcp ·
Sign-in: OAuth, at the first Collects request.
Claude (claude.ai, Desktop, mobile)
- Add Collects from the Claude connectors directory — or, before the listing is live, go to Customize › Connectors › Add custom connector and enter the server URL. No client ID or secret is needed.
- Ask Claude about your overdue invoices. The first time Claude calls Collects it shows a Connect card: sign in to Collects.
- Optional: install the Collects plugin for the resolve unpaid invoices skill.
Claude Code
claude mcp add --transport http collects https://mcp.collects.io/mcp
The 34 tools
Claude sees only the tools your role and the permissions you gave it allow. The Tools page lists each one with the permissions, roles and plan it needs.
Reading
| Tool | What it does |
|---|---|
collects_account |
Who you are connected as, your role, your organisation and plan, its mailbox and Xero health, and what you can do now |
list_overdue_invoices |
Overdue invoices from your Xero organisation, most overdue first |
get_invoice_status |
The status of one overdue invoice, including disputes and promises to pay |
get_resolution_outcome |
The outcome of a resolution |
collects_search |
Search your invoices, debtors, disputes and Workbench tasks by text and the filters the Collects pages have |
collects_fetch |
One invoice, debtor, Workbench task or attachment by id, invoice number or debtor name, with its timeline, dispute, payments and emails when you ask |
collects_activity |
What Collects has done, as the Activity page shows it: work done, time and cost handed back, work by activity, everything it handled (by activity, rule, who did it or day, for one customer or invoice too), the problems it caught, and the Value page's verdict and what you are owed by age (read-only) |
collects_value |
What Collects is worth to you, as the Value page shows it: value delivered, opportunity on your ledger and estimated value, expected collections, the latest collections actions and how the figures are worked out; and, to owners and admins before you move to Collect, the Billing page's value panel (read-only) |
collects_briefing |
Your briefing: what needs attention and what came in since you last opened it. Reading it does not mark it seen |
collects_ar_overview |
Your dashboard: what you are owed and what is overdue, what needs attention, Xero sync alerts and the most overdue invoices |
Reminders on an invoice or a customer
| Tool | What it does |
|---|---|
start_resolution |
Collects starts resolving the invoice on your normal schedule and settings. Claude asks you to confirm first |
collects_pause_reminders |
Pause reminders on one invoice, with a reason |
collects_resume_reminders |
Resume reminders on one invoice, or lift the AI's financial-difficulty pause |
collects_record_promise |
Record a promise to pay, or mark one missed |
collects_log_note |
Log a note or a call on an invoice |
collects_set_debtor_do_not_contact |
Pause or resume every reminder to one customer. Pausing shows you what stops first |
Emailing a debtor
| Tool | What it does |
|---|---|
collects_preview_debtor_email |
Shows the email exactly as it would go, to the address Collects holds for the debtor. Sends nothing |
collects_send_debtor_email |
Sends the email you saw in the preview, once you confirm |
collects_message_dispute_debtor |
Emails the debtor about an open dispute, after showing you the message and who it goes to |
Disputes
| Tool | What it does |
|---|---|
collects_open_dispute |
Log a dispute on an invoice; reminders pause |
collects_update_dispute |
Comment on, assign, resolve, approve or reject a dispute |
collects_add_dispute_evidence |
Attach a PDF or image to a dispute, in two steps |
The Workbench
| Tool | What it does |
|---|---|
collects_act_on_task |
Act on a Workbench task as its card does: review, hold, release, approve, reject, resolve, or accept or dismiss an AI suggestion. Approving or accepting anything that emails the debtor shows you the email first |
collects_resolve_blocker |
Ignore a failing data check on an invoice, mark it fixed, or re-check it |
Organisation, team and integrations (owner or admin)
| Tool | What it does |
|---|---|
collects_set_org_chasing |
Turn the organisation's collection emails on or off |
collects_update_company_identity |
The Company identity card on Settings, Organisation |
collects_update_locale |
The date format, on the Locale & Configuration card |
collects_update_operating_model |
The Operating model card: the figures Collects' value estimates use |
collects_update_debtor_contact |
Who debtors can contact, shown in every email's footer |
collects_set_ai_thresholds |
The AI thresholds |
collects_manage_team |
Invite, resend, cancel, deactivate or reactivate a team member, after showing you what changes |
collects_connect_integration |
The link to connect Xero or your mailbox in Collects. You sign in to Xero or your mailbox there, never in Claude |
collects_retry_import |
Retry the Xero or email import, or refresh credit terms from Xero |
collects_disconnect_integration |
Disconnect Xero, your mailbox or a connected app, after showing you what stops |
Resources and prompts
Claude can also read an invoice or a debtor as a resource,
collects://invoices/{id} and
collects://debtors/{id}: read only, with the same data and rules
as collects_fetch. Three prompts give you a starting point:
review my overdue book, prepare an invoice reminder (for an
invoice you name) and while I was away. A prompt only fills in a
request; it never sends anything.
When Collects needs you in the browser
If your plan does not include an action, or Xero is not connected, Collects answers with a link: the billing page (only the owner changes the plan) or Settings › Integrations. Hosts on the newer MCP protocol revision may offer to open it for you. Card details and Xero sign-in never happen in Claude.
Text your customers wrote
A debtor's email or reply, a dispute note and text Collects' AI wrote from
them reach Claude marked as untrusted_text. Claude treats them as
information to report, never as instructions to follow.
Who can do what
Collects acts as the person who signed in, with their role in Collects, checked on every request: Claude can do what you can do in the Collects app, and nothing more. Anyone in your organisation can read. Changing reminders, disputes and Workbench tasks needs the role the Collects app asks for, and the organisation, team and integration tools are for owners and admins. Anything that emails a debtor, adds a person or stops collection shows you what will happen first, and happens only once you confirm.
What Claude does shows in Collects under your name, marked "via Claude", and Settings › Integrations › Connected apps lists each app's recent actions.
Two-step verification
If you have two-step verification on in Collects, signing in to connect asks for your code, whether you sign in with your email and password or with Xero. Turning two-step on, changing your password or being deactivated ends your existing connections; connect again to carry on.
Try it on a sandbox organisation
A sandbox is a Collects demo organisation: a book of made-up customers and invoices, with a history the product itself wrote (reminders sent, replies, promises to pay, disputes, Workbench items). Use it to try every tool and the REST API before you connect your own organisation.
How to get one: ask Collects at hello@collects.io. There is no sign-up for a sandbox; someone at Collects creates it for you and you are its owner. Then:
- Open the invitation email, set your password and accept the terms.
- Connect Claude or Claude Code as above, and sign in with email and password. A sandbox has no Xero organisation of its own, so "Continue with Xero" does not reach it.
- You can invite colleagues from the Team page, as in any organisation.
What is different from your own organisation:
- It is on the Collect plan, so the plan allows starting resolutions and sending emails.
- Emails to its customers, sent by Collects or by you, go only to Collects' own demo mailbox or to reserved test addresses. Collects refuses any other recipient, so no customer email reaches a real person. Team invitations are ordinary emails to the address you enter.
- It is not a customer account: it stays out of Collects' reports.
-
It is suspended 30 days after it was created. After that you can still read
it, and every change is refused with
account_suspended.