How Claude reaches Xero
Claude does not have built-in access to your Xero organisation. It needs a connector: software that authenticates to Xero and exposes Xero data and actions to Claude. The most common way to do this today is an MCP server — a small service that speaks the Model Context Protocol.
Three questions to ask before you connect
- Who holds the Xero credentials? If each person’s Claude holds a Xero token, every connected AI is another set of keys to your books.
- What can Claude do? Reading an aged receivables report is very different from approving an invoice or changing bank details.
- Who is Claude acting for? In a firm, different people should see different clients. A single shared connection cannot tell them apart.
Direct connection versus a gateway
A direct connection is quick to set up for one person working on their own books. For a team — and especially a practice handling client data — a gateway such as Kroy holds the connection centrally, applies per-person permissions, requires approval for financial actions and records every request.
What to keep out of scope
Most organisations exclude payroll, bank-detail changes and invoice approval from AI access, at least initially.