Xero MCP server for AI agents.

Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 191 Xero actions across invoicing, payments, settings and ledger, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by Xero.

Xero publishes an MCP server that you run on your own machine (the @xeroapi/xero-mcp-server package), signed in with a Xero custom connection or a bearer token. (Xero's documentation, checked 22 October 2026.) Use Xero's server when one person wants to work in Xero through a server they run on their own machine. Use actionlake when you also want Xero behind the same endpoint as your other systems: a key per agent with allowed actions and a spending cap, a named person's approval before destructive actions, a sealed record of every call, and one ask across Xero and another system.

Your own Xero OAuth app, registered with Xero (its client id and client secret), and the access and refresh tokens from one admin sign-in. actionlake has no Xero app of its own, so this is not a one-step consent. actionlake renews the access token as it expires. actionlake finds the organisations, sites or workspaces the credential can reach for you when you connect. Each one is its own connection, so an agent can work across several by name. The free call account { op: "connections.requirements", service: "xero" } lists exactly what to paste.

Only if its key allows it, and only with an explicit confirmation. 15 Xero actions are destructive, including create a batch payment, delete a draft invoice and delete a batch payment. Each runs only with confirm: true. Under the human confirm policy, or an approval rule on the key, the run waits until a named person approves it.

actionlake paces every call to the limits in the Xero service file: 60 calls a minute and 5,000 a day, at most 5 at a time per connection. Repeated reads are answered from cache (116 Xero actions can be), which never reaches Xero.

One upstream call, the only unit actionlake bills. A list that pages bills one call per page (11 Xero actions page). Cache hits, searches, dry runs and calls Xero refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

The Xero Accounting API 2.0 at api.xero.com/api.xro/2.0. It is built from Xero's documentation as read on 14 September 2026. 191 actions in 13 areas, each one in the signed service file (version 4.0.0).

Yes. ask joins Xero to ConnectWise PSA or HubSpot CRM on the same customer and returns the answer rather than every row. Xero maps crm.company, which 227 other connectors also map.

actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to an hour, and a write clears the reads it affects. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your Xero credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models.

Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names.