QuickBooks and Xero MCP Servers: What Exists and How to Connect Safely
Yes, both exist. Intuit publishes a QuickBooks Online MCP server in its own GitHub organisation, and Xero publishes one in its XeroAPI organisation. Both run on your own computer, both need developer credentials, and both can change your books unless you restrict them. The safe route is the same for each: test on sample data, connect read-only first, and keep a person in the loop for anything that creates, edits or deletes a record.
This is general information, not accounting, security or legal advice. Details below come from the two repositories’ own README files and GitHub pages, checked on 1 November 2026. Both projects are active and change often, so confirm against the current README before you set anything up.
Key Takeaways
- Intuit’s
quickbooks-online-mcp-serverand Xero’sxero-mcp-serverare both published by the vendors’ own GitHub organisations and both run locally on your machine.- QuickBooks has built-in switches to hide create, update and delete tools. Xero controls access mainly through the scopes you grant the connection.
- QuickBooks production setup is the harder of the two, because Intuit rejects a plain localhost callback in production mode.
- Test with Xero’s Demo Company or a QuickBooks sandbox before touching real books.
- Treat the config or
.envfile holding your keys like a password.
Do QuickBooks and Xero Have Official MCP Servers?
Yes. Each is published in the software maker’s own GitHub organisation, which is a stronger signal than a directory listing or a third-party wrapper. It still does not mean a polished, supported product. Read each README for what it claims.
| QuickBooks Online | Xero | |
|---|---|---|
| Repository | intuit/quickbooks-online-mcp-server | XeroAPI/xero-mcp-server |
| Where it runs | Local, as a stdio subprocess on your machine | Local, launched by your AI app with npx |
| Needs | Intuit developer app, OAuth handshake, refresh token | Xero developer account, custom connection with client ID and secret |
| Read, create, update, delete | Yes, across 29 entity types and 11 reports (145 tools, per its README) | List, create and update tools, plus payroll timesheet tools; the only delete tool listed is for payroll timesheets |
| Built-in way to hide write tools | Yes, three environment switches | No switch; narrow the scopes instead |
| Suggested first test | Intuit sandbox company | Xero Demo Company |
If you are new to the idea, our guide to MCP servers for small business explains what a server, a client and a tool are before you touch any of this. Our list of official MCP servers shows which other vendors publish their own. If you run a WordPress site, see our WordPress MCP server guide.
What Can Each Server Do?
Think of each server as a menu of actions your AI assistant may order. What matters is which actions are on the menu.
QuickBooks Online. Intuit’s README describes full create, read, update, delete and search operations for entities such as customers, invoices, bills, vendors, payments, journal entries, deposits and transfers. It also lists 11 reports, including profit and loss, balance sheet, cash flow, aged receivables and aged payables. That is a lot of reach. An assistant with every tool enabled could delete a bill or record a payment, not just summarise one.
Xero. Xero’s README lists a tool set covering contacts, the chart of accounts, invoices, quotes, credit notes, payments, bank transactions, manual journals and reports such as profit and loss, balance sheet and trial balance. Most are list- tools that only read. There are also create- and update- tools, including create-payment and create-bank-transaction. Payroll tools exist too, and the README notes that payroll queries need a region of NZ or UK.
How to Connect QuickBooks Online Safely
Intuit does not offer a personal API key. Even to read your own company, the README says you must register an app on the Intuit Developer Portal and complete a one-time browser-based OAuth handshake.
- Start in the sandbox. Create an app, add
http://localhost:8000/callbackas a redirect URI, copy the client ID and secret, create a sandbox company, setQUICKBOOKS_ENVIRONMENT=sandbox, and run the auth step the README describes. Sandbox accepts localhost redirects. - Disable write tools before the first chat. The README lists three optional settings:
QUICKBOOKS_DISABLE_WRITE=truehidescreate_tools,QUICKBOOKS_DISABLE_UPDATE=truehidesupdate_tools, andQUICKBOOKS_DISABLE_DELETE=truehidesdelete_tools. It also says read tools, meaningget_andsearch_, are always available. Setting all three gives you a read-only assistant. - Know why production is harder. The README says Intuit rejects
http://localhostredirect URIs in production mode and requires a public HTTPS callback for the first authorisation. It describes two workarounds: an ngrok tunnel, or a small public callback handler you deploy yourself. Both are developer tasks, and a tunnel exposes a web address to the internet while you use it, so this is a good point to ask for technical help. - Expect token upkeep. After the handshake the server runs without the browser, “until the 100-day refresh window lapses”, per the README. It rotates the refresh token and writes the new one back to your
.envfile. - Guard the file. That
.envholds your client secret and refresh token. Do not email it, sync it to a shared folder, or commit it to a code repository.
How to Connect Xero Safely
Xero’s README offers two authentication modes. For desktop AI apps it recommends custom connections, which let you set a client ID and secret for one specific organisation.
- Use the Demo Company first. Xero recommends it because it comes with sample data, and it can be reset at any time from the My Xero page.
- Create a custom connection in your Xero developer account, following the guide the README links to.
- Match the scopes to your connection date. The README says connections created before 29 April 2026 use the older bundled scopes, while connections created from that date use granular ones. The server tries the older set first and falls back to the newer one.
- Narrow access with
XERO_SCOPES. The README shows an optionalXERO_SCOPESsetting that takes a space-separated list. Its own example uses invoice, contact and settings scopes. The README does not document a ready-made read-only set for custom connections, so if you want read-only, check Xero’s scope documentation for the.readvariants and test in the Demo Company that write tools fail before you point it at live books. - Keep payroll out. Leave payroll scopes off unless you have a specific, reviewed need. The bearer-token mode lists payroll employees and timesheets among its scopes, which is more than most owners need on day one.
The config goes in your AI app’s settings file with the client ID and secret in plain text, so the same warning applies: that file is as sensitive as a password.
Which Tasks Make Sense and Which Do Not
This is our judgement from the documented tools, not a vendor ruling.
| Task | Stance | Why |
|---|---|---|
| “Summarise this month’s profit and loss” | Reasonable, read-only | Low impact if misread; verify numbers against the report |
| “List overdue invoices and who owes most” | Reasonable, read-only | Uses aged receivables or invoice search |
| “Draft a quote or invoice” | Think twice | Writes to real records; review every draft before sending |
| “Categorise these bank transactions” | Think twice | Edits your books; mistakes spread into reports and tax |
| “Record or approve payments” | Avoid | Keep payments and reconciliation with a person |
| “Delete or void anything” | Avoid | Hard to undo at scale |
| “Payroll and employee records” | Avoid | Sensitive and often regulated |
Your accountant or bookkeeper should know before an AI assistant touches the ledger. They are the person who finds the damage at year end.
What Goes Wrong
The MCP specification says tools “represent arbitrary code execution and must be treated with appropriate caution”. For accounting, three failures stand out:
- Over-broad access. All tools on means a single bad instruction can edit or delete records.
- Steered requests. If the assistant also reads emails or web pages, hidden text in them can try to redirect it. Do not combine your accounting connection with tools that read untrusted content.
- Leaked credentials. A key in a config file is only as safe as your computer and your backups.
Our post on whether OpenClaw is safe for business covers the same pattern for another agent tool.
What If This Is Too Technical?
Setup involves developer portals, Node.js, tokens and config files. If that is not your world, you have sensible options: ask your accountant or an IT contractor to set up a read-only connection, or skip MCP and use your accounting software’s built-in reports and exports. Our comparison of MCP against plain APIs and automation tools explains the trade-offs. For customer records rather than accounting, see our guide to CRM MCP servers for small business. If you use QuickBooks Online in the US, Intuit also describes a packaged QuickBooks connector for Claude, and our Claude Cowork guide for small business covers what it can change.
Frequently Asked Questions
Is there an official QuickBooks MCP server?
Intuit publishes quickbooks-online-mcp-server in its own GitHub organisation, and its README describes a local server for QuickBooks Online. There are also community forks, so check the organisation name before you install.
Is there an official Xero MCP server?
Xero publishes xero-mcp-server in its XeroAPI GitHub organisation, with a README covering setup for desktop AI apps.
Can I make either server read-only?
QuickBooks: yes, by setting the three disable switches to true. Xero: limit the scopes and verify in the Demo Company, since the README documents no single read-only switch.
Does it work with QuickBooks Desktop?
Intuit’s server is for QuickBooks Online. This guide does not cover QuickBooks Desktop.
Can I use it without a developer account?
No for both, per their READMEs. Intuit says there is no shortcut around creating an app, and Xero’s setup uses a developer account with API credentials.
Sources
- Intuit, quickbooks-online-mcp-server README (github.com/intuit/quickbooks-online-mcp-server)
- Xero, xero-mcp-server README (github.com/XeroAPI/xero-mcp-server)
- Model Context Protocol, Specification, version 2026-07-28 (modelcontextprotocol.io)
All retrieved 1 November 2026.