Connect Claude to every Xero organisation. At once.

MCP (Model Context Protocol) is an open standard that lets AI assistants like Claude connect directly to external tools and data sources. A Xero MCP connects Claude to your Xero accounting data, so you can query financials, create invoices, post journals and run reports using natural language instead of navigating the Xero UI manually.

With ELab's Xero MCP, you subscribe, authenticate with your Xero credentials through a secure OAuth flow, select the organisations you want to connect and start using Claude with full financial context. The whole setup takes under 10 minutes. We handle the hosting, token refresh and infrastructure.

With the official Xero MCP, no. It connects to one organisation at a time. ELab's Xero MCP connects to all your organisations from a single Claude session. You can query across entities, reconcile intercompany transactions and run consolidated reports without switching connections.

The official Xero MCP is free and connects Claude to a single Xero organisation. ELab's Xero MCP adds multi-entity management (connect all your orgs at once), pre-built finance workflows (reconciliation, cost apportionment, AP automation), hosted infrastructure with auto token refresh, and an audit trail that logs every write operation with user identity.

Yes. The MCP supports both read and write operations. Claude can create invoices, draft bills, post manual journals, manage contacts and handle bank transactions. Every write action is logged in the audit trail with a timestamp and the identity of the user who initiated it.

The MCP authenticates via Xero's OAuth flow using your existing Xero credentials. For multi-entity access, the authenticating user needs advisor-level or admin-level access across the organisations you want to connect. Standard access works for single-entity setups.

Financial data is read and written directly to Xero via the official API. ELab does not store transaction, account or report data beyond what is needed to execute the active operation. Xero credentials are stored as encrypted environment variables, never in code, logs or session context.

Every write operation (invoices, journals, payments, contacts) is logged with a timestamp, the user who initiated the action and what was changed. This gives you the same accountability you'd have if someone made the change directly in the Xero UI, even though the action was executed through Claude.