Xero has moved its MCP server from a developer’s laptop to its own infrastructure. In The Xero Remote MCP is now generally available, the post explains the catch with the local server developers have been using to pull aged receivables, draft invoices and check who owes money: “You had to run it yourself.” That works for one developer experimenting, and is “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.”
The one figure is the catalog size: 39 tools at launch, covering invoicing, full accounting, and profit and loss, balance sheet, trial balance and aged receivables and payables reports. The design details are what make it trustworthy for accounting data. It uses Xero’s standard OAuth 2.0 with PKCE, “so users consent to which organisation an AI tool can see,” and calls “go through the same permissions and rate limits as the rest of the Xero API.” 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.” Pricing follows the API: included on paid developer plans, with tool calls counting as API calls “under your existing usage,” and usable against the demo organisation on the free plan.
The catalog holds Xero as one of its best-governed records. The Xero provider page lists API pages including the Xero Accounting API that 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 lit.
The Kin Score is 77.4, 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, agent-native. The detail 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. The unlit dimensions include reversibility and dry-run mode, which matter for an agent that can post journals and draft invoices. Xero has made the MCP server a hosted, consented, metered part of the API rather than a side project. The record agrees, and the next step is letting an agent check a journal before it posts.