Picture this. It's the end of the month, and someone on your team has been using an AI assistant to pull aged receivables, draft invoices and check who owes money. It works well for them. Now a colleague wants the same thing, and then a client does too. Someone asks you the question that matters: can we trust an agent with accounting data, and who has to run it?
That is the situation Xero's latest announcement speaks to, and the APIs.io catalog has a story on it. Xero has moved its MCP server from a developer's laptop to its own infrastructure. In its post, The Xero Remote MCP is now generally available, the company explains the catch with the local server developers have been using: "You had to run it yourself." That is fine for one developer experimenting. It is, in Xero's words, "awkward the moment you wanted a colleague, a client or a second organisation to use the same thing."
The remote server is "the same Xero MCP server, hosted and maintained by Xero. Add the URL and sign in. That's the setup." For you, that means no one has to keep a process running on a personal machine. The one figure in the post is the size of the catalog: 39 tools at launch, covering invoicing, full accounting, and reports for profit and loss, balance sheet, trial balance and aged receivables and payables.
The design details are what make it believable for accounting data. It uses Xero's standard OAuth 2.0 with PKCE, "so users consent to which organisation an AI tool can see." Calls "go through the same permissions and rate limits as the rest of the Xero API." And because it signs in through a standard Xero app rather than a Custom Connection, which exists only in the US, UK, Australia and New Zealand, "it's available everywhere."
The money side is just as plain. Pricing follows the API. The server is included on paid developer plans, tool calls count as API calls "under your existing usage," and you can use it against the demo organisation on the free plan. So you can try it before anyone signs off on anything.
Here is where the catalog turns to its own record. Vendor posts say what a vendor wants you to know, so the question is whether the catalog's file on Xero agrees. It does. The Xero provider page lists API pages including the Xero Accounting API, which most of the 39 tools wrap, and the Xero Identity API and Xero Connections API behind the organisation-choosing sign-in. On the Agent Readiness score, the MCP server, agent skills, idempotency, error semantics, the event surface, delegated identity and dynamic client registration are all lit.
The Kin Score is 77.4, in the exemplar band, with contract governance at 84.5, the highest governance facet this series has recorded, and developer ergonomics at 86.2. The Agent Readiness score is 65.1, which lands in agent-native. The catalog holds Xero as one of its best-governed records.
The catalog also files something against Xero. The unlit dimensions include reversibility and dry-run mode. Those matter a great deal for an agent that can post journals and draft invoices. If your team is thinking about letting an assistant near the ledger, that gap is the one to weigh. An agent that cannot preview or undo what it does is a risk you would need to cover some other way.
The detail the catalog says is worth copying is commercial. MCP tool calls are metered as API calls, so the agent surface and the API share one usage model, one rate limit and one invoice. For you, that means no separate bill to explain to finance and no second set of limits to track.
What you take away is simple. Xero has made the MCP server a hosted, consented, metered part of the API rather than a side project, and the catalog's record agrees with that claim. You can say yes to the colleague and the client without asking anyone to run a server. You should still hold the line on writes until the next step arrives: letting an agent check a journal before it posts.
Read the original: https://apis.io/2026/10/23/xero-hosts-its-mcp-server-and-scores-agent-native/