Xero MCP connectorfor Microsoft Copilot
Microsoft's remote-connector path for Xero runs through Copilot Studio, not the Copilot chat box you already have open. Build an agent, add this connector on its Tools page, and publish it to the people who should use it. Reads run straight through. Every write is drafted and held until you approve it inside Invio.
Using Claude or ChatGPT instead? See the Claude guide or the ChatGPT guide.
This runs through Copilot Studio, not the Copilot chat box
Microsoft's own remote-MCP path for Xero lives in Copilot Studio - the platform used to build agents for Microsoft 365 Copilot and Teams, reached from an agent's own Tools page, not a setting inside the ordinary Copilot chat window. You add this connector there as a Model Context Protocol tool, choose no authentication (the connector URL already carries your access), and then publish that agent - to specific people, a group, or your organisation's agent catalog for an admin to approve - before it is reachable at all. We have not run this specific connector through Copilot Studio ourselves; what we can say with certainty is that it serves the Streamable HTTP transport Copilot Studio's own wizard requires, the same endpoint Claude and ChatGPT already connect to.
Connect Xero to Copilot Studio in 5 steps
The same connector URL works for Claude and ChatGPT too - see the full setup guide for every client at once.
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.
Open, or create, a Copilot Studio agent
This is Copilot Studio, the separate platform Microsoft agents are built in - not the Microsoft 365 Copilot chat window you already have open. Open an existing agent there, or create a new one, to attach the connector to.
Add the connector as an MCP tool
On the agent's Tools page, choose Add a tool, then New tool, then Model Context Protocol. Paste the URL you copied from Invio into Server URL, and set the authentication type to None - the URL already carries your access, the same way it does for Claude and ChatGPT.
Publish the agent to the people who should use it
An agent is not reachable by anyone until you publish it. Share it directly with specific people or a group, or submit it to your organisation's agent catalog for an admin to approve - either way, it then appears in Microsoft 365 Copilot or Teams for the users you chose.
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.
Reads are live. Writes wait for you.
Copilot 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.
What an agent gains that it doesn't have on its own
A documented way to connect
Copilot Studio's MCP tool wizard accepts a hosted, remote connector like this one directly - paste the URL, choose no authentication, and it is available to add to an agent's Tools page.
More than one Xero organisation
Connect every organisation you run, up to your plan's limit, and let the agent ask across them in one session without reconnecting.
Writes that wait for a human
Nothing created or changed reaches Xero until you approve it inside Invio - a ledger stays a human decision, not an agent response.
Questions about Microsoft Copilot and Xero
Does this work inside the Microsoft Copilot chat box I already have?
Have you tested this connector with Copilot Studio?
What authentication type should I choose in Copilot Studio?
What happens when Copilot tries to change something in Xero?
Can I point the same connector at Claude or ChatGPT as well?
Is this an official Microsoft or Copilot product?
Give an agent the Xero organisations you already can't see across
Choose a plan on the main connector page, generate a connector URL in Settings, and add it to a Copilot Studio agent's Tools page.
Using Claude or ChatGPT too? See the Claude guide or the ChatGPT 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. Microsoft Copilot is a trademark of Microsoft, and we are not affiliated with, endorsed by, or certified by Microsoft either. You remain responsible for reviewing and approving any changes made to your Xero organisations.