MCP servers for Canadian tax and accounting software: what exists in September 2026

An MCP server is the standard way to let an AI agent use a piece of software: a published list of things the agent can read and do, with the vendor's permissions in front of it. Claude, ChatGPT and Microsoft Copilot all speak it. Over the past year most vendors that serve Canadian accounting firms have said something about MCP, a few have shipped, and it has become hard to tell an announcement from a product. This page is the scoreboard. Each entry links to a page with the sources, what an agent can actually do with that product today, and what to watch. We verify every status quarterly and date each one.

The short version, as of September 2026: the accounting platforms and the file systems have shipped; the practice management platforms have announced; the Canadian tax packages and the CRA have neither.

Accounting platforms

QuickBooks Online. Shipped. Intuit publishes an official local MCP server with 144 tools, labelled early preview, and hosted connectors for Claude and ChatGPT. The Claude connector is US-only, so Canadian firms use the local server or the API. QuickBooks Online MCP server.

Xero. Shipped. Official local MCP server for any MCP client, plus a hosted Claude connector that is read-only and available in Canada, and a ChatGPT app launched in September 2026. Nothing reaches TaxCycle, which Xero owns. Xero MCP server.

Practice management platforms

Karbon. Announced, not shipped. A public MCP server was announced with Kai on June 3, 2026; Kai is in limited early access and no MCP appears in the product or API release notes. Karbon's REST API is documented and complete enough that we have already run T1 intake against it. Karbon MCP server.

TaxDome. Announced, in beta. MCP support promised for general availability by the end of Q3 2026, on top of an API that is itself in private beta. No public documentation yet. TaxDome MCP server.

Jetpack Workflow. None, and no API. Zapier exposes client and job creation and wraps them in its own MCP catalogue. We have run T1 intake on Jetpack Workflow through a browser session and Google Drive. Jetpack Workflow MCP server.

Canadian tax software

TaxCycle. None. A developer API exists under a partner licence with no public documentation. Widest set of documented import paths: Auto-fill my return, Excel import for slips and forms, XML slips, DoxCycle. TaxCycle MCP server.

ProFile and Pro Tax. None. Intuit's MCP server covers QuickBooks Online only. ProFile has a partner API by application. Auto-fill my return, GIFI import from QuickBooks Online, Hub & Link portal. ProFile and Pro Tax MCP server.

DT Max. None, and no API or SDK. Auto-fill my return and competitor conversion are the only documented paths in. DT Max MCP server.

Taxprep, Cantax and CCH iFirm. No MCP, but CCH iFirm Taxprep has the only public web API among Canadian tax packages: cell-level read and write on T1, T2 and T3 returns, on the Pro tier. Desktop Taxprep and Cantax have no API. Taxprep, Cantax and CCH iFirm MCP server.

The CRA

Canada Revenue Agency. None, and the terms of use for CRA sign-in services prohibit automated access. Auto-fill my return, EFILE, ReFILE, Express NOA and Client Data Enquiry run only inside CRA-certified software with a person signed in. Anything sold as a CRA MCP server has no CRA access. CRA MCP server.

File and email systems

Google Drive. Shipped. Google's Workspace MCP server is in developer preview since May 2026; the Drive connector in Claude is generally available on all plans with read and write. Google Drive MCP server.

Microsoft 365. Shipped, with conditions. Microsoft's SharePoint, OneDrive, Outlook and Teams MCP servers are in preview and require a Copilot licence; the Microsoft 365 connector in Claude is generally available on all plans, read for everyone and write when an administrator allows it. Microsoft 365 MCP server.

What the scoreboard means for a firm

Three things follow from the pattern.

The input side of tax intake is solved. Client documents in Google Drive, SharePoint, OneDrive or an email inbox are readable by an agent today, on any plan, with nothing to build. A firm that keeps a folder per client already has an agent-ready document layer. How to set that up, plan by plan and level by level, is in Claude for Canadian tax preparers.

The middle is missing. None of the systems above knows that a file is a 2025 T4 from a specific employer with box 24 blank, or that a client's return is waiting on a T3 that has not been issued yet, or that the rental-sale question was answered on February 10. Practice management platforms will get closer when their MCP servers ship, and they track work rather than tax facts. That middle layer is what Armada T1 is: the system of record for T1 intake, with its own MCP server, where an agent records slip and receipt data as validated section records with the source stored alongside, tracks what is still outstanding, and routes each open question as a task to the preparer or to the client. Armada T1 does not calculate or EFILE returns; the completed file is handed off to whichever CRA-certified tax software the firm already runs.

The output side will stay closed for a while. The Canadian tax packages have no MCP servers and, with the exception of CCH iFirm, no public APIs; the CRA has neither, and its terms of use rule out the browser as a substitute. The handoff from a verified intake file into the return is a preparer keying or importing from something known to be complete, and the value of an agent upstream is measured in how little the preparer has to check.

How we keep this current

Every page in this set carries a "status verified" month and links to the vendor pages we read. We re-check all twelve quarterly, sooner when a vendor has given a date, and we change the status only when something is generally available or publicly documented, not when it is announced. If you see a change before we do, tell us and we will verify it. All thirteen pages are listed at /integrations, newest first.

For the practical side, the T1 intake checklist, the T1 client questionnaire and the T1 Client Intake Kit cover what an agent needs to collect; the Karbon and Jetpack Workflow and Google Drive builds show the loop running end to end.

This page describes third-party products as documented by their vendors in September 2026. All product names are trademarks of their respective owners, and no partnership or endorsement is implied. Product availability changes; verify with the vendor before relying on it.