Xero MCP for Claude

Xero MCP connectorfor Claude

Xero's own Claude connector covers one organisation and only reads. Invio adds every organisation you run, with every write held in a queue until you approve it.

Using ChatGPT or Microsoft Copilot instead? See the ChatGPT guide or the Copilot guide.

Checked 9 September 2026

Xero already has a Claude connector. Here's the difference.

Xero's own Claude connector

Official, and free with any Xero subscription

One organisation at a time - reconnecting is needed to switch

Read-only - it can answer questions, not draft anything

Invio's Xero MCP connector

Independent, paid connector on top of Xero's official API

Every organisation your plan allows, in one session

Reads live, and drafts writes held for your approval

If you run one Xero organisation and only need to ask questions, Xero's own connector already covers that - we say so plainly rather than pretend otherwise.

Setup

Connect Xero to Claude in 4 steps

Covers claude.ai and Claude Code. The same connector URL works for ChatGPT too - see the full 7-step guide for every client at once.

1

Connect Xero and generate a connector URL

In Invio, go to Settings > MCP > Xero, connect the Xero organisations you want to share, then click Generate connector URL. Copy it straight away - it is shown exactly once.

2

Click Open in Claude

Right after generating the URL, click Open in Claude - it pre-fills the "add custom connector" screen for you in claude.ai. Or add it yourself: Settings > Connectors > Add custom connector, and paste the URL.

3

Using Claude Code, not just claude.ai?

A connector added in claude.ai also shows up in Claude Code, but it does not work there automatically. Run /mcp in a Claude Code session, pick the Xero connector, and approve it there too.

4

Ask a question first

Try something read-only, like what's outstanding on one of your organisations. Reads run straight through - no approval needed. Then ask it to draft an invoice or change a contact, so you see the approval step happen for real.

A second, dead entry in Claude's desktop app (Cowork)

If you added this connector before it was live, that attempt is left behind as a stale entry that never connects, sitting next to the working one you add now. Open Claude's connector settings and remove the older, non-working Xero entry.

How writes reach Xero

Reads are live. Writes wait for you.

Claude drafts

It reads your live Xero data directly. When it wants to create or change an invoice, a contact, a credit note or a journal, that becomes a draft - not a change to your books.

Invio holds it

The draft sits in your approval queue, showing the exact organisation and the exact payload Invio would send. Left untouched, it expires after 24 hours and nothing happens.

You approve

Approve or reject inside Invio. Nothing reaches Xero until you do, and every approval records who made it.

Every client, in one guide

The full setup guide covers Claude, ChatGPT and any other MCP client - what Xero's consent screen asks for, where the connector URL comes from, and exactly how approval works.

FAQ

Questions about Claude and Xero

How is this different from Xero's own Claude connector?
Xero's own connector is free with any Xero subscription. It connects one organisation at a time - moving to a different client's file means disconnecting and reconnecting - and it only reads, so it can answer questions but cannot draft anything. Invio connects every organisation your plan allows in one session, and drafts writes - an invoice, a contact change, a credit note, a manual journal - held for you to approve before anything reaches Xero.
Does this replace Xero's own Claude connector?
Not necessarily - you can use either, or both. If you only run one Xero organisation and only need to ask questions, Xero's own connector already covers that. Invio answers a different question: several organisations in one session, and writes that need a person to approve them.
Does Claude Code work the same way as claude.ai?
Not automatically. A connector you add in claude.ai also appears in Claude Code, but Claude Code authorises each connector separately - run /mcp in a session, pick the connector, and approve it there before any tool call works.
What happens when Claude tries to change something in Xero?
It can't post the change directly. Claude hands the draft to Invio, which shows you exactly what it wants to write and to which organisation, and holds it. Nothing reaches Xero until you approve it inside Invio, and an unapproved draft expires after 24 hours.
Can I point the same connector at ChatGPT as well?
Yes. One connector URL works with Claude, ChatGPT, or any other MCP-capable client on the same subscription - you do not need a second plan to use more than one assistant. See the ChatGPT-specific guide if you use both.
Is this an official Claude or Anthropic product?
No. Invio is an independent connector built on Xero's official API. We are not affiliated with, endorsed by, or certified by Xero, Anthropic, or Claude, and we say so on every page.
Get started

Ask Claude about the Xero organisations you already can't see across

Choose a plan on the main connector page, generate a connector URL in Settings, and click Open in Claude.

Using ChatGPT or Microsoft Copilot too? See the ChatGPT guide or the Copilot guide. For questions this page doesn't cover, the main connector FAQ has more.

Invio is an independent connector built on Xero's official API. Invio is not affiliated with, endorsed by, or certified by Xero. Xero is a trademark of Xero Limited. Claude is a trademark of Anthropic, and we are not affiliated with, endorsed by, or certified by Anthropic either. You remain responsible for reviewing and approving any changes made to your Xero organisations.

Xero MCP Connector for Claude | Invio