The Xero MCP that connects Claude to every 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.

A standard single-org connector cannot. It connects to one organisation at a time. ELab connects to every organisation you have authorised, so you can search and work across them in one session without reconnecting each time.

A standard connector links your AI tool to one Xero organisation. ELab adds access to every organisation you have authorised in a single session, stronger invoice and credit note search (filter by reference, status and date range, with larger result pages), Xero Projects support, a hosted connection layer with automatic token refresh, approved-user access controls and an audit trail on write actions.

Yes. The MCP supports both read and write operations. Claude can create invoices, draft bills, post manual journals and manage contacts across the organisations you have authorised. 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.

Sometimes. When a new capability needs a Xero permission you have not already granted, you will be asked to re-approve access for the organisations you already use. We tell you before it happens, and it takes about a minute per organisation.

ELab provides the Xero integration layer. We are not responsible for the AI model providers or the AI client software that call it. You remain responsible for reviewing outputs and any actions taken in your Xero organisations.