Enter your idea

Adding a comment to push for this to be prioritised - I find it infuriating I have to switch between different accounts by disconnected and reconnecting the MCP every time. This could be multiple times a day, and I'm only running two businesses. I work with numerous accountants and the same issue drives them crazy as well.

Disclosure: I'm Invio's AU distributor, so I have a commercial interest here.

For anyone stuck disconnecting and reconnecting while this idea gains support: Invio built a connector that holds several Xero organisations in one Claude or ChatGPT session. You connect each organisation by logging in to Xero and approving access. No developer app or client secret.

It answers one question across the group, which is what Glenn and Charlotte describe below. It can also draft invoices, bills and payments, but nothing reaches Xero until a person approves it.
It can also put P&L or balance sheet for several organisations side by side with a total

If Xero's own multi-organisation support arrives as mentioned above, that will be the simplest route for many. This is for groups that need it now, or want every write to wait for a person's approval.

Invio built one, and anything it drafts waits for your approval before it reaches Xero.

If you need proper consolidated statements, Joiin, Fathom or Syft are the better fit.

I have two companies and having to continually disconnect and reconnect is driving me insane!!! 😆

Pedro, good point on the resourcing gap, not every practice has the people to build and maintain a custom setup. Worth flagging for everyone on this thread: Xero ran their Developer Quarterly Webinar last night and announced a remote MCP server going to general availability in October, built for multi-org access. Should ease a lot of the pain described here once it lands. Worth watching next month.

Hi Philippe, I agree with your position on an infrastructure that connects with Xero via API. Also, share the sentiment that it could be a very straightforward process, with Claude helping.

However, what you get from AI is based on how much you know and understand about technology, and it could be very challenging for many practitioners (e.g. Bookkeepers and Accountants) to start a build, go through the process and come up with a repeatable solution. Big 4 and second-tier firms have the advantage of human resource infrastructure; small practices have only themselves and little free time.

We started building dashboards that run on the server and can be accessed and refreshed by any person in the organisation.

Also, building something local, without the ability to share it with other people in the team, may not be as useful, meaning you will need a server (either local or on the Cloud).

To be honest, I am not fond of building into an AI product (Claude, GPT, etc.), but for the vast majority, that is the best option (being left behind as the alternative).

Mr. Fraser's idea seem worthwhile for his situation, but I suspect many of Xero's Advisors would rather the Claude connector support multiple clients/tenants.

Developing with Claude to come up with personalized MCPs, or other means, seems like over kill for something that is implied can already work (Xero's own MCP repo suggests compatibility).

I, too, vote for multiple organizations in the Claude Connector.

Hey - so this blew my mind - I got Claude to write 3 x custom MCP connectors, (one for each Xero organisation), and it works! Downside, took about 20 minutes to get it all working, and costs £5/month for a custom connector per Xero organisation, so £15/month for me. But it works!

get claude to talk you through it, but here are instructions for you, and below are instructions for Claude;
How we did it - three organisations, one Claude, using Xero Custom
Connections plus the open-source Xero MCP server. You repeat the whole
thing once per organisation.

IN THE XERO DEVELOPER CENTRE (once per organisation)

1. developer.xero.com > My Apps > New app > Custom connection. Name it so
you can tell them apart later, e.g. "Claude MCP - [org name]".

2. Scopes. Tick the scopes you will need. If the scope ends with “.read” it means it is read only. That was fine for me- up to you how you use it. For my read-only variant I used:
well: accounting.attachments, accounting.banktransactions,
accounting.contacts, accounting.invoices, accounting.manualjournals,
accounting.payments, accounting.reports.aged,
accounting.reports.balancesheet, accounting.reports.profitandloss,
accounting.reports.trialbalance, accounting.settings

3. Authorising user - you. I use read-only, so I used my own username However, if you are going to let Claude create or edit anything, create a separate Xero user for it first and authorise as that user. Xero records who createdan invoice, and you will want that to say "Claude", not you.

4. Save, then Connect. You get an email with two steps that both matter:

a) Buy a Custom Connection subscription. One PER ORGANISATION - they
are not shared. You can buy them one at a time as you go; I did.
UK is GBP 5/month ex VAT (AU $10 inc GST, NZ $10 ex GST, US $5 ex
tax). Worth knowing: Xero moved developer pricing to tiers on
2 March 2026 with a free starter tier of 5 connections, but Custom
Connections were explicitly excluded and "remain on the same
commercial terms" - so the free tier does not cover this.

b) The consent screen. This is the step that matters. It lists every
Xero organisation your user can see. Pick one. You cannot change it
afterwards - you would have to create a new custom connection.

5. Copy the Client ID from the app page, then generate a Client Secret.
It is shown once and it is 48 characters. Count them before pasting it
anywhere - a 49-character paste, one stray character picked up on
copy, cost me an hour debugging a connection that looked perfectly
configured.

ON THE CLAUDE SIDE

6. Run Xero's own open-source MCP server, @xeroapi/xero-mcp-server, once
per connection: a separate server entry for each, each given that
connection's own client ID, secret and scopes in its environment, and
each under a distinct name (xero-companyA, xero-companyB, ...).

7. Claude then sees each organisation's tools namespaced by server name,
so a question about company B is answered from company B's books.
Group questions work by asking each in turn and summing. You can leave
the built-in hosted Xero connector attached to a further organisation
alongside these - they coexist fine.

TWO THINGS THAT CAUGHT US OUT

- The tool list does NOT reflect your granted scopes in step 2 above. Even on a read-only connection, create-invoice, create-payment, the update-* tools and the payroll tools all still appear and are callable. However, Xero only allows what is defined in step 2.

- A server's NAME is not evidence of which organisation it is bound to.
You picked the organisation by hand on the consent screen, so one
mis-click gives you a perfectly working connection to the wrong
company's books: real numbers, right currency, internally consistent,
wrong entity. Nothing downstream ever looks wrong. So make the first
call of every session a parameterless "organisation details" call on
each server and check the name that comes back before trusting a single
figure.

IF YOU WANT CLAUDE TO DO THE SETUP, paste it everything above, plus:
"Please set up multiple MCP server entries pointing at Xero custom
connections, one per organisation, so I can ask for reports across all of
them. Ask me first how many organisations I need and what each server
should be called. I have the client IDs and secrets ready - write the
config with placeholders so I can paste the credentials in myself."

THE OBVIOUS CAVEAT: this is one app registration, one paid subscription
and one local server process per entity. For three organisations it is
fine. For a practice with 30+ clients it plainly a lot of work - which is why
native multi-org support in the connector is the thing actually being
asked for here.

We are a multi entity group with 4 entities using Xero - we need to be able to query through claude across all organisations to get anything useful as outputs.

I've started using Atso.ai to manage multiple Xero accounts with my claude without having to login and logout!

This is a must - for any multi entity group, this is a must. It's unusable otherwise

This would be so usefil

I'm very interested in the "..can this be improved to ...permit data requests at a more granular level?" part of the request.

I have a Claude skill to perform a monthly financial close and it works fantastically with Ramp but the Xero connectivity is a major impediment. Lots of abilities that Claude wants to have access to but that are not supported in the connector. Also, stale data is very frustrating - I want Claude to have realtime access to my Xero data.

I selected Xero partially on the basis of your announced partnership with Anthropic. There was a press release March 27th, 2026 and I'm disappointed there doesn't seem to have been much development since then.

This would be really useful as we have 2 companies in Xero and I need to be able to produce consolidated dashboards and reports. If this can be prioritized it would be very helpful.

One reason we need this is we are at a disadvantage to our own clients who can quickly access their data via their AI tool while we are not able to do the same.

This is absolutely needed - most business and family groups do not operate in isolation and analysing a single entity at a time is inefficient

We need this badly. I run a unlisted property trust fund called Natgen. We have over 30 entities. We need this asap!

I concur with Duyen.

We operate 6 trading entities. We can analyse data at a single entity level no problem. What would bring real value would be the ability to aggregate and analyse data across the Group without a lot of manual data extraction.

I'm thinking analysing payables, receivables, trends, cash-flow forecasting, and aggregation of expenditure line items (eg: software subs, travel, training).

Honestly, getting Claude to analyse one org is maybe cute, but really doesn't add a lot of additional functionality. I'm not here for cute.

Luke has described the two real gaps precisely. Worth adding for anyone hitting them today: both are solvable outside the official connector. Xero's public API does expose transaction-level detail (bank transactions, invoices, journals), and the open source Xero MCP server can be adapted to hold connections to several organisations at once. Our practice runs exactly this setup for scheduled multi-entity work, including reconciliation-grade transaction pulls, on both Mac and Windows. These limits sit in the official connector's design rather than the platform, so native support for both would make the integration what it should be. Happy to compare notes on the setup, I am easy to find on LinkedIn (same name as this comment).

Duyen, well said. Holding companies, family groups and related trading entities under one login is exactly the scenario where the single-org connector falls short, and intercompany journals and consolidated views are where multi-org access pays off most. As mentioned in my earlier comment, we adapted the open source MCP setup to handle this for our own practice, so it is workable today. Happy to compare notes if useful, feel free to reach out to me on LinkedIn (same name as this comment). Fully agree native support is the right long-term answer.

Strong support for this idea. Worth noting for others hitting the same wall: this is solvable today. Xero's API supports custom connections, and the open source Xero MCP server can be adapted so Claude holds connections to multiple organisations in one session. We run this daily in our practice across several client orgs, on both Mac and Windows, so the single-org limit is a connector design choice rather than a platform constraint. Native support in the official connector would still be the right outcome for most users. Happy to share what we learned building ours if useful.