Does Xero have an official MCP server?

Xero does not publish an official MCP server at this time. Community servers use the Xero API documented at developer.xero.com. You need a Xero developer app with a client ID and client secret to authenticate the connection.

What Xero API scopes should I authorize for an AI assistant?

For read-only review and analysis, authorize accounting.transactions.read, accounting.accounts.read, and accounting.reports.read. Only add write scopes if the assistant is expected to record transactions or reconcile entries, and document each permitted write operation explicitly.

Can the AI reconcile transactions in Xero?

The Xero API supports reconciliation operations. Reconciliation changes the accounting records, so it should be reviewed by a qualified person before the AI proceeds. Set a rule that write operations require human confirmation, and record it in your project context.

What happens to the follow-up tasks from a Xero review session?

Add them to a shared task board in a tool like fenbs, with the Xero transaction reference, the issue, and who should handle it. The next session reads the task list and picks up where the previous one left off rather than re-reviewing transactions already checked.

Where should bookkeeping process rules be stored?

In a shared project context tool such as fenbs, as Decisions and rules. Record expense categories, reconciliation standards, and any standing rules about what the AI can and cannot change. These rules are read by every assistant session that works on the bookkeeping, not just the first.

Xero MCP Server: Connect AI to Bookkeeping Workflows

A Xero MCP server lets an AI assistant query invoices, reconcile transactions, check account balances, and pull financial reports through a standard tool call. Here is how to connect it, set the right access boundaries, and keep bookkeeping process rules and follow-up tasks outside the accounting system.

August 5, 2026Updated October 21, 20264 min read

A Xero MCP server connects an AI assistant to Xero accounting data through a standard tool call, letting it query invoices, check bank account balances, review unreconciled transactions, and pull profit and loss summaries without exporting a spreadsheet. The connection uses the Xero API (opens in a new tab), which requires a Xero organization with an API-connected app. Tools like fenbs keep the bookkeeping process rules and follow-up tasks that come out of each session, so the next session starts with the right context and the accounting records stay in Xero where they belong.

Xero MCP servers are community-built. Check the MCP server directory for available packages. You will need a Xero account with sufficient subscription level to enable the API connection.

Connect an AI assistant to Xero

In the Xero developer portal (opens in a new tab), create a new app. Set the redirect URI to match the MCP server's OAuth callback and note the client ID and client secret.
Install and configure the Xero MCP server package with the client ID and client secret as environment variables.
Add the server to your AI client's MCP config. See MCP server configuration for the config format.
On first connection, the server opens a browser for you to sign in to Xero and authorize access. After authorization, the server stores the tokens for future sessions.
Test with a read-only call: ask the AI to list open invoices or pull the current bank balance. Compare the result to what you see in Xero before using the connection for any write operations.

What the AI can do with Xero

Through the Xero API, an AI assistant can read invoices, bills, bank transactions, contacts, account balances, and reports. This is enough for most review and analysis tasks: checking whether invoices are overdue, summarizing unreconciled transactions for a given period, or pulling a profit and loss for a specific month.

Write operations include creating and updating invoices, recording payments, and adding journal entries. These require write scope in the Xero app authorization. Only enable write access for assistants working in supervised workflows where each action is reviewed. A wrong journal entry in accounting can require significant effort to reverse.

Set access boundaries for financial work

The Xero API uses OAuth scopes to separate read and write access by data type. When authorizing the MCP server app, select only the scopes the assistant actually needs. Read-only access covers the majority of review and analysis tasks; write access should be added deliberately and documented as a specific permitted operation.

For bookkeeping work, establish a rule that any change to the accounting records — a new journal entry, a recorded payment, a reconciliation mark — must be reviewed and confirmed by a qualified person before the AI proceeds. Document this as a standing rule in the project context. See MCP server architecture for how access decisions flow through an MCP connection.

Keep process rules and follow-up tasks outside Xero

Xero holds the accounting records. It does not hold the process rules your bookkeeper applies — which transactions to categorize as which expense type, how to handle intercompany invoices, which bank feeds require manual review — or the follow-up tasks that come out of a review session.

fenbs keeps those rules as Decisions and rules in the project, and the follow-up tasks on the board. When the assistant reviews the current month and surfaces three invoices that need attention, those become tasks in fenbs with the right owner and context. The next session reads where things stand without re-querying Xero to reconstruct what was already reviewed.

Some Xero accounts have access to multiple organizations, which is common for bookkeeping firms managing clients or for businesses with subsidiaries. The Xero API includes the organization in the authentication flow: the MCP server typically connects to the organization that was active at authorization time. If you need to work across organizations in one session, check whether the MCP server package supports multi-tenant access or whether you need separate configurations for each organization. The Xero developer documentation (opens in a new tab) covers the multi-tenant authentication flow, including how to list connected tenants and select the right one per API call. Record which organization each credential set maps to as a context note so future sessions know which config to use for which client.

How fenbs helps

Keep bookkeeping rules and follow-up tasks where every session can find them

Record your expense categorization rules, reconciliation standards, and the requirement that a person reviews any write operation as Decisions and rules in fenbs. Add follow-up tasks when the AI surfaces transactions that need attention. The next session starts from the current task list rather than re-reviewing what was already checked.

Create a free account

Free for one person · No credit card · Works with Claude, ChatGPT, Cursor and more

How to do this with fenbs

Create a free account and add a project for the Xero bookkeeping work.
Record the bookkeeping process rules as Decisions and rules: expense categories, reconciliation conventions, and which operations require human review.
Add follow-up tasks to the board when the AI surfaces transactions, invoices, or discrepancies that need attention. Include the Xero reference, the issue, and who should handle it.
Connect your AI app to fenbs at Integrations. It reads the rules before reviewing any Xero data.
Before each session ends, save progress: which period was reviewed, what was found, what tasks were added, and what the next session should check.

fenbs does not connect to Xero directly. It holds the process rules and task list; the Xero MCP server handles the live accounting queries.