November 20, 2026

MCP for Accountants: Which Accounting Software Has an MCP Server in 2026 (and What to Let AI Agents Do)

MCP for Accountants: Which Accounting Software Has an MCP Server in 2026 (and What to Let AI Agents Do)
Which accounting, payroll and close tools publish a first-party MCP server, which ones let an AI agent write to your books, and the controls I would set before connecting one.

I checked 13 finance systems that publish an official MCP server, and exactly one of them, Sage Intacct, is read-only by design. Two more, Puzzle and Microsoft Dynamics 365 Business Central, start read-only and make you opt in to writes. Everything else on the list will let an AI agent create or change records if the person who signs in has the rights to do it.

That's the part most MCP coverage skips. Vendor pages pitch the agent, developer tutorials show you how to wire it up, and almost nobody asks the controller question: what happens to segregation of duties when Claude or ChatGPT logs in as you? COSO put out Achieving Effective Internal Control Over Generative AI in February 2026, and the AICPA followed in October with a practice aid on AI for financial statement auditors (AICPA announcement). Your auditors are going to ask how AI touches the close. I'd rather you have the answer before they do.

What is an MCP server, in accounting terms?

An MCP server is a standard adapter the software vendor publishes so an AI assistant can call a fixed set of actions (called tools) against your books, using your login. Before MCP, getting an AI to look at your general ledger meant exporting CSVs or paying someone to script the API.

Three things matter more than the protocol itself:

  • It inherits your role. Most of these servers sign in through OAuth as the person connecting. Connect with an admin role and the agent gets every write, edit and delete that role carries.
  • It's usually session-bound. A connector in Claude acts when someone prompts it in a chat. It doesn't watch your books overnight unless you wire it into a separate workflow tool.
  • Who hosts it changes your risk. A vendor-hosted server or the vendor's own open-source repo keeps the vendor accountable. A third-party middleware server is another data processor holding your ERP tokens, and that's a vendor review you'd have to do.

I wrote more about judging software this way in Stop Comparing Software Features. Ask If an Agent Can Actually Run It.

Which accounting software has an official MCP server?

As of November 2026, QuickBooks Online, Oracle NetSuite, Sage Intacct, Xero, Business Central, Zoho Books, Puzzle, Light, Rillet and Numeric all publish first-party servers, and so do Stripe, Gusto and Remote on the money-movement side. Capabilities change fast, so treat this table as a starting point and confirm against the vendor docs I've linked before you connect anything.

SystemRead / writeWhat I could verify
QuickBooks OnlineRead and writeIntuit's open-source server exposes 144 tools across 29 entities, with DISABLE_WRITE, DISABLE_UPDATE and DISABLE_DELETE flags and no payroll tools (our breakdown). A hosted version is reported to be in an invite-only pilot.
Oracle NetSuiteRead and write, by roleOAuth 2.0 with PKCE, SuiteQL and saved searches, and the Administrator role can't connect (Oracle docs).
Sage IntacctRead-onlySage describes the server as read-only access.
XeroRead and writeThe official open-source server has write tools, and Xero recommends starting on the Demo Company.
Business CentralRead-only by defaultWrites and posting need a custom configuration with edit tools unblocked (Microsoft Learn).
Zoho BooksRead and writeTools can be added or removed through a custom Zoho MCP configuration, with admin approval.
PuzzleRead-only by defaultWrite access is an opt-in beta, and every change asks for confirmation (Puzzle).
LightRead and writeHosted; can edit draft transactions and draft expenses.
RilletMirrors the public APIHosted, OAuth2 or API key, limited to the connected user's permissions.
NumericRead GL, write to the closeWrites to close tasks and flux explanations, inherits the user's Numeric role, and a Claude admin can set the connector read-only (Numeric help).
GustoRead and writeThe tool list now includes run_payroll, which calculates and submits an unprocessed payroll (Gusto docs).
RemoteMostly readCan't move money or start payouts or payroll runs.
StripeRead and writeRefunds require human confirmation, and Stripe stops accepting full secret keys and untagged restricted keys in December 2026 (Stripe docs).

The Gusto row is the one I'd flag. Earlier in 2026 a lot of guides, ours included, called Gusto's server read-only. That's out of date. An agent with the right Gusto role can now submit payroll, so scope that connection carefully.

What can AI agents safely do with ledger access today?

With read-only access, agents are good at the export, pivot and summarize work that eats the first days of close, and they should stay in a drafting role. The jobs I'd hand over first:

  • Flux commentary drafts. Pull comparative trial balances, drill into the GL lines behind the big variances, and draft the explanation for a human to edit.
  • AR aging triage. List invoices over 60 days past a dollar threshold, summarize payment history, and draft collection emails nobody sends until a person reads them.
  • Missing-bill checks. Compare recurring vendors against what's arrived, propose an accrual, and lay out a draft entry in a table. I walk through this one in how to hand accruals and prepaids to an AI agent.
  • Close checklist updates. In Numeric, an agent can see which reconciliations are blocked and update task status or flux notes without touching GL balances.

I'll complicate my own list a bit: read-only still isn't risk-free. An agent that misreads a sign or invents a vendor name in a flux note gives you a wrong explanation that looks finished, and a tired reviewer can wave it through. The tie-out step below exists for that reason.

Which permission should controllers leave off?

Unapproved write and post access on a live production ledger. Leave that off.

Two reasons. First, the model can be wrong in ways that look right, and Oracle's own MCP FAQ warns about hallucination. Second, an agent that reads documents can be steered by text hidden in them. A vendor PDF with buried instructions is the obvious case, and Stripe's docs warn about prompt injection directly.

There's also a quieter control problem. Because the server signs in as you, every entry the agent posts lands in the audit log under your name. If you let the same agent prepare and post using your credentials, you've undercut the preparer and reviewer separation that SOX 404 control environments usually rely on. My rule is short: AI drafts, and a named person approves anything that posts.

What controls should be in place before you connect an AI client?

Six, and you can set all of them up in an afternoon:

  • A dedicated, least-privilege role. View-only on the modules the agent needs. NetSuite already blocks Administrator; do the same everywhere else.
  • Sandbox first. Point the first connection at a sandbox or demo company. Xero says this in its own docs.
  • First-party servers only. Vendor-hosted or the vendor's own repo, so there's no extra processor holding tokens.
  • Standard reports over raw queries. Built-in financial reports apply consolidation and currency rules that an ad-hoc query can miss.
  • Logs you keep. The prompt, the tool calls, the report timestamp, and when tokens get revoked.
  • Human sign-off. Anything the agent drafts is a preparer draft until a reviewer ties it to the locked trial balance.

Frequently asked questions

Which accounting MCP servers are read-only?

Sage Intacct is read-only by design. Puzzle and Business Central default to read-only and need an explicit opt-in for writes. Numeric reads GL data and only writes to close tasks and flux explanations.

Can an AI agent run payroll through an MCP server?

In Gusto, yes: its current tool list includes submitting a payroll. Remote's server can't start payroll runs or move money, and Intuit's open-source QuickBooks server has no payroll tools at all.

Does connecting an MCP server affect SOX 404?

It can. The agent acts under a real user's identity, so keep prompts, tool configurations and reviewer sign-offs as audit evidence, and never let one identity both prepare and post.

Should I use a third-party MCP server for my ERP?

Only if the vendor doesn't publish one and you've reviewed the middleware like any other processor. It holds your ERP tokens outside the vendor's own security boundary.

If you want to try this, pick one read-only connection this week, run a single flux-commentary prompt against last month, and tie every number back to the trial balance by hand. You'll learn more about where it breaks than any directory can tell you. If you're building toward a role where this is part of the job, the live listings on Audit Friendly Jobs show which teams already ask for it, and our software reviews score each vendor on agent readiness.