Xero data, answered where teams work.

What a conversational layer over Xero can and cannot reach

Xero's API is one of the more approachable in accounting software, which is why it has attracted so many integrations. Contacts, invoices, payments, bills, purchase orders, credit notes, and supplier credits are all readable, and those records cover the overwhelming majority of what non-finance staff actually ask about: who owes us money, what does this contact still owe, has this bill been paid.

There is one boundary worth stating plainly, because it surprises people. Kipper does not read Xero bank data. No bank transactions, no bank balances, no reconciliation status. That also rules out anything derived from them, including cash position and runway. Bank feeds are central to Xero itself, so the assumption that a Xero integration must see them is understandable, but for Kipper it is not the case.

The posts below cover connecting Xero to AI assistants over MCP, OAuth scopes and what each one grants, custom connections versus OAuth apps, multi-entity setups, SQL access approaches, and troubleshooting. Read the scopes post before granting anything: it is the one that determines what an integration can reach.