MCP servers for accounting and taxes

The short version, as of August 2026: the accounting platforms have moved faster than the tax side. Two of the big ledger vendors ship official MCP servers, tax compliance is covered mostly by vendor APIs wrapped in MCP, and general tax-code research is served by commercial third parties rather than anything authoritative. This is the honest map, including what does not exist and where an agent should not be the last word.

Accounting platform connectors

This is the most mature category. Two of the major ledger systems maintain their own open-source servers:

• Xero maintains an official server at XeroAPI/xero-mcp-server, which runs locally through your MCP client and speaks to Xero's accounting and payroll API: invoices, contacts, the chart of accounts.
• Intuit maintains intuit/quickbooks-online-mcp-server for QuickBooks Online, which runs as a local process and authenticates to a QuickBooks Online company through an app you register on the Intuit developer portal.

Both are self-hosted rather than remote hosted endpoints, which is the right default for financial data anyway. Expect an OAuth setup step; that is the part that takes the time, not the MCP wiring. If you have not connected a server before, adding an MCP server to Claude Code walks the mechanics.

Beyond those two, most coverage is community servers or accounting-tooling vendors exposing their own platform through MCP. Check who publishes a server before you connect it to a ledger.

Tax compliance and filing versus tax research

These are two different categories with very different risk profiles, and conflating them is the main mistake in this space.

Compliance and filing is vendor territory. Tax-automation providers have started publishing MCP interfaces onto their existing APIs: Avalara for indirect-tax compliance and TaxBandits for information returns are two published examples. These are the same operations their APIs already supported, reachable in natural language. The correctness guarantee comes from the vendor, not from the model.

Tax-code research is a different job: grounding an answer in the Internal Revenue Code, Treasury regulations, IRS publications, and rulings, with citations you can follow. There are commercial MCP services doing this, and no authoritative free equivalent. Treat the citation, not the summary, as the output you rely on.

The free and reliable corner: public filings

If your work touches organizations rather than your own books, the public-data servers are the strongest picks in this whole space, because the underlying data is authoritative, free, and does not require you to hand an agent write access to anything.

Community MCP servers wrap the ProPublica Nonprofit Explorer API, which exposes IRS Form 990 filings: tax-exempt status, an EIN, and filed financials. That is the bedrock of any diligence workflow on a tax-exempt organization. The fuller list for that job is MCP servers for nonprofits, which is the right page if your finance work is nonprofit finance.

What most people actually use: files and spreadsheets

Worth saying plainly, because the listicle format tends to hide it: a large share of real accounting work with an agent runs through the Filesystem server and a spreadsheet, not through a platform connector. Exports, reconciliations, and schedule preparation are file problems. An agent that can read a directory of statements and write a working paper covers more ground than a ledger integration for a lot of workflows, and it exposes far less.

Keep the active server count low either way. Clients get unwieldy past a handful, and every enabled server spends context. Useful Claude Code MCP servers and free MCP servers cover the general-purpose set.

Who offers MCP solutions, and how to tell them apart

Servers come from three places, and the distinction matters more in finance than anywhere else:

• First-party vendor servers, published by the company whose data they expose (Xero and Intuit above). Highest trust, usually self-hosted, usually the slowest to add features.
• Community servers, published by individuals or small teams. Fine for public data, and a real supply-chain question for anything with credentials. Read the source.
• Remote hosted endpoints, run as a service. Convenient, and they mean your financial data transits someone else's infrastructure. Read the terms before, not after.

Compliance caveats, stated bluntly

• An agent must not be the last check on a filing. A human with the professional obligation signs the return. Use the agent to draft, reconcile, and flag, then review.
• Model output is not tax advice. A cited answer from a research server is a starting point for a professional to verify, not a conclusion.
• Connecting a ledger means granting write access to financial records. Scope credentials as tightly as the platform allows and prefer read-only until you have a specific reason not to.
• Public data is safe where client data is not. A 990 lookup carries no confidentiality exposure. A client's books do, including under your engagement terms and your jurisdiction's privacy rules.
• Log what the agent did. If it touched the ledger, you need to be able to say what it changed and when.

If you have spare capacity, point it somewhere useful

One more server worth knowing about, from the other direction. Tokens for Good does not read your books; it lets your agent contribute research. It claims a queued nonprofit, researches its real-world impact against a fixed methodology with citations, and submits a structured report. Every organization is researched twice by independent contributors, validated, consolidated, scored deterministically, and human-reviewed before it reaches the public directory.

It runs on the AI subscription you already pay for, with no separate API cost, and it uses capacity that resets unused otherwise. "Tokens" means AI model tokens, not crypto. See how it works or the docs.

Frequently asked questions