Connect Xero to Claude Code

Have Claude draft invoices and code bills in Xero. From the terminal, inside the sessions where you already work.

How do you connect Xero to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Xero, you add a Xero MCP server: a small hosted service that exposes Xero's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Xero account. No API keys pasted into config files.

claude mcp add --transport http xero https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Xero once connected?

Full read-write Xero access lets Claude draft and send invoices, create and categorize bills, add contacts, and post manual journals once you approve. The month-end work that used to mean clicking through screens happens where your ledger already lives, with you confirming each change.

Draft a sales invoice for a contact and submit it for your approval
Create and code a bill to the right account and tax rate
Send a drafted sales invoice to the contact once you approve it
Add or update a contact record with billing details
Post a draft manual journal for an adjustment you describe
Pull a profit and loss or aged receivables report and flag what stands out

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Xero access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Xero API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Xero changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Xero connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Xero connector work in claude.ai and Claude Code?

Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Xero account, so access always matches what that person can already see and do.

Do I need to host or maintain anything myself?

No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Xero's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.

Is it safe to give a coding agent write access to Xero?

Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Xero account it signs in with. Revoking access is one click in Xero.

More on the Xero connector

Xero connector for claude.ai QuickBooks Online + Claude Code FreshBooks + Claude Code Stripe + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connector Talk to us