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.

Microsoft 365 MCP server: what exists in September 2026

Microsoft ships several MCP servers, and the ones a Canadian accounting firm would want, covering SharePoint, OneDrive, Outlook and Teams, are in preview and tied to Microsoft 365 Copilot licensing. The faster route for most firms is the Microsoft 365 connector in Claude, which is generally available on every plan and reads SharePoint, OneDrive, Outlook mail and calendar, and Teams, with write access when an administrator turns it on. For a firm whose client documents sit in SharePoint or OneDrive, an agent can be reading them today.

Status, verified September 2026

Microsoft's MCP Server for Enterprise, documented June 26, 2026, is in public preview and covers Entra directory data only, read-only; it does not reach files or mail. The Agent 365 MCP servers for SharePoint and OneDrive, Outlook mail and calendar, Teams, Word and Dataverse are in preview through Copilot Studio, and end users need a full Microsoft 365 Copilot licence to use them. The GA Microsoft servers, Microsoft Learn and Azure, are for developers rather than for documents. MCP support inside Copilot Studio has been generally available since May 2025, which lets a firm connect Armada T1 or any other MCP server to a Copilot agent.

The Microsoft 365 connector for Claude is generally available on Free, Pro, Max, Team and Enterprise plans, including the mobile apps. It reads SharePoint, OneDrive, Outlook mail and calendar, and Teams through delegated Microsoft Graph permissions; sending mail, creating calendar events, creating or updating files and posting Teams messages are available only when an administrator enables write access, and the write tools do not handle attachments. ChatGPT offers separate SharePoint, OneDrive and Outlook apps.

Underneath everything is Microsoft Graph on Entra ID OAuth 2.0, with delegated and application permission models. Canada is a local region geography under Microsoft's data residency commitments for Exchange, SharePoint, OneDrive and Teams. One caveat matters for firms that care about that: when Anthropic models are used inside Microsoft 365 Copilot, Microsoft states that the processing is outside its in-country commitments. Claude has been generally available in Microsoft Foundry since June 2026.

Status verified September 2026. We re-check this page quarterly.

What an agent can do with Microsoft 365 today

Through the Claude connector, an agent can search a SharePoint document library or a OneDrive folder for a client's uploads, read the slips and receipts, read the email thread where the client explained the rental sale, and check the calendar for the review meeting. With write access enabled by the firm's administrator, it can save a reconciliation summary back to the client folder and draft the follow-up email for a preparer to send. A firm that already runs a client-per-folder convention in SharePoint has, in effect, the same document layer that Google Drive gives a Google Workspace firm, and our Jetpack Workflow and Google Drive build translates directly.

Two cautions. Text extraction from a connector is fine for a letter and not fine for a T4; for anything with box numbers on it, have the agent read the file itself. And an inbox is not an intake system: a T5 attached to an email the agent has read is still not recorded, tracked, or reconciled against what the file expected.

Where Armada T1 fits

Armada T1 is the system of record for Canadian T1 intake, with its own MCP server. SharePoint, OneDrive and Outlook hold the documents and the conversations; Armada T1 holds what they say. An agent connected to both reads each document as it arrives, records slip and receipt data as validated section records with the source stored alongside, reconciles against the file's expected list, and routes each open question as a task to the preparer or to the client. A firm on Copilot Studio can connect Armada T1 to a Copilot agent through its GA MCP support; a firm on Claude connects it the same way it connects Microsoft 365. Armada T1 does not calculate or EFILE returns; the completed file is handed off to the CRA-certified tax software your firm already runs.

How to check for changes

Watch the Agent 365 MCP server posts for the SharePoint and Outlook servers to reach general availability and to loosen the Copilot licence requirement, and the Claude connector help page for attachment support in the write tools. For the rest of the Canadian stack, see MCP servers for Canadian tax and accounting software.

This page describes third-party products as documented by their vendors in September 2026 and is not affiliated with or endorsed by Microsoft. Microsoft 365, SharePoint, OneDrive, Outlook, Teams, Copilot and Azure are trademarks of Microsoft Corporation. Claude is a trademark of Anthropic, PBC. ChatGPT is a trademark of OpenAI. Product availability changes; verify with the vendor before relying on it.

Google Drive MCP server: what exists in September 2026

Yes, on two fronts. Google now runs its own Google Workspace MCP server, covering Drive alongside Gmail, Calendar, Chat and People, in developer preview since May 2026. And the Google Drive connector built into Claude has been generally available for over a year, on every plan, with read and write access. For a Canadian accounting firm whose client documents already live in Drive, this is the most mature agent access on the whole list, and the reason our no-API intake build used Drive as the document layer.

Status, verified September 2026

Google's Workspace MCP server entered public developer preview with a gradual rollout from May 1, 2026. It is a hosted, remote MCP server that any compliant client can connect to, and it sits within Google's wider catalogue of managed MCP servers, some of which are generally available and some, including Workspace, still in preview.

The Google Drive connector for Claude, help page updated August 17, 2026, is generally available on all Claude plans in the web app and Claude Desktop, with Team and Enterprise organizations enabling it at the owner level. It searches and retrieves files, reads Docs, Sheets, Slides, PDFs, images and Office files, uploads files, creates folders, and can share, move and trash files. Claude Code can save files to Drive when file creation is enabled. ChatGPT has a Google Drive app with sync on paid plans, read-only.

Underneath is the Drive API v3 on OAuth 2.0. The scope worth knowing about is drive.file, which limits an app to files it created or the user picked; the broader drive and drive.readonly scopes are restricted and require Google's verification. Google Workspace data regions offer the United States, Europe, or no preference; there is no Canada option.

Status verified September 2026. We re-check this page quarterly.

What an agent can do with Google Drive today

Read every document a client has uploaded, in the folder structure the firm already uses. That is the whole of intake's input side, and it needs no new software. In our published build, Jetpack Workflow and Google Drive: T1 intake run by an AI agent, no API required, the agent listed a client's 2025 T1 Inbox folder, read each file, identified a T4 and a donation list, and recorded the figures with the source document attached. One lesson from that build carries over to any Drive setup: for slips and anything else with numbers on it, have the agent pull the file itself rather than rely on a connector's text extraction, because a misread box number is a wrong return.

The agent can also write back: a reconciliation summary in the client folder, a renamed and sorted set of slips, a folder for next year. What Drive does not give you is structure. A folder knows it holds a file; it does not know the file is a 2025 T4 from a specific employer with box 24 blank. That knowledge has to live somewhere else.

Where Armada T1 fits

Armada T1 is the system of record for Canadian T1 intake, with its own MCP server, and it is the somewhere else. Drive holds the documents; Armada T1 holds what they say. An agent connected to both reads each file as it lands in the client's folder, records slip and receipt data as validated section records with the source stored alongside, reconciles against the list of what the file expected, and routes each open question as a task to the preparer or to the client. The firm keeps its Drive folders exactly as they are. Armada T1 does not calculate or EFILE returns; the completed file is handed off to the CRA-certified tax software your firm already runs.

How to check for changes

Watch the Workspace updates blog for the Workspace MCP server to reach general availability and the Claude connector help page for capability changes. Firms with residency requirements should watch the data regions page for a Canada option. For the rest of the Canadian stack, see MCP servers for Canadian tax and accounting software.

This page describes third-party products as documented by their vendors in September 2026 and is not affiliated with or endorsed by Google. Google Drive and Google Workspace are trademarks of Google LLC. Claude is a trademark of Anthropic, PBC. ChatGPT is a trademark of OpenAI. Product availability changes; verify with the vendor before relying on it.

CRA MCP server: what exists in September 2026

There is no CRA MCP server, no CRA API for tax preparers or taxpayers, and no official way for an AI agent to sign in to a CRA account or to Represent a Client. Anything described as a "CRA MCP server" is a private product that has no access to CRA systems. The CRA's terms of use for its sign-in services prohibit automated access outright, so an agent driving a CRA session through a browser is not a workaround; it is a breach of the terms the firm's representative accepted. The CRA's data reaches a firm through exactly one machine channel, and that channel runs through CRA-certified tax software.

Status, verified September 2026

The CRA's digital services for tax preparers page lists no developer program, API, or agent access. The terms and conditions for CRA sign-in services, modified February 9, 2026, prohibit the use of any "script, robot, spider, web crawler, screen scraper" or other automated device, prohibit sharing credentials, and state that My Account is for individuals and that representatives must use Represent a Client. The CRA can suspend access without notice.

The CRA's own use of AI is internal. As reported in April 2026, it runs a public chatbot for general questions and states that AI is not used to decide personal tax matters. Nothing is exposed to outside agents.

Status verified September 2026. We re-check this page quarterly.

What the machine channels actually are

Every one of them requires CRA-certified software and a registered EFILE number, and none of them is an API a firm or an agent can call directly.

Auto-fill my return delivers slips, carryforwards, RRSP and home buyers' plan data, disability tax credit eligibility, and account balances into the return, for clients who have authorized the firm through Represent a Client. It runs inside the certified software under the representative's own CRA sign-in and, from 2026, its backup multi-factor authentication. The CRA's 2026 getting ready for tax season tax tip confirms that since July 15, 2025 individual authorizations are requested only through Represent a Client, no longer through EFILE.

EFILE transmits the return itself; the 2026 program accepts 2018 to 2025 returns, with ReFILE for 2022 to 2025. Express NOA returns the notice of assessment into the software. Client Data Enquiry shows account information for authorized clients. Each is a feature of the certified product, exercised by a person who is signed in.

The consequence for agent design is simple. An agent can prepare everything that goes into a return and can read everything that comes out of the CRA once a preparer has downloaded it, and it should never hold CRA credentials, complete a CRA sign-in, or navigate a CRA session. The CRA account sign-in with backup MFA is built around a human being present; the terms make the same assumption.

Where Armada T1 fits

Armada T1 is the system of record for Canadian T1 intake, with its own MCP server. It does not connect to the CRA. It holds what the CRA cannot supply: the receipts, the questions, the life events, the documents that arrive after the mid-March Auto-fill window, each recorded as a validated section record with its source stored alongside. An agent connected to it reads each document as it arrives, identifies what is still open, and routes each item as a task to the preparer or to the client. When the preparer runs Auto-fill in the certified software, the two sets of data meet in the return. Armada T1 does not calculate or EFILE returns, and it never asks a firm for a CRA credential.

The 2020 CRA account breaches, settled in 2026 for $8.7 million with claims open until February 2027, are a reminder of why credential handling is the line to draw. A tax intake system that never touches a CRA sign-in cannot leak one.

How to check for changes

Watch the digital services for tax preparers page and the terms of use modification date. If the CRA ever opens a developer channel, it will be announced through the EFILE program first. For the rest of the Canadian stack, see MCP servers for Canadian tax and accounting software.

This page summarises publicly available CRA guidance as published in September 2026 and is not tax, legal, or filing advice. Blackspark is not affiliated with the Canada Revenue Agency. Program rules change; verify with canada.ca before relying on them.

Taxprep, Cantax and CCH iFirm MCP server: what exists in September 2026

Wolters Kluwer has no MCP server and no AI-agent connector for any of its Canadian tax products. It does have something no other Canadian T1 vendor offers publicly: a documented web API for CCH iFirm Taxprep that reads and writes individual cells in a T1, T2, or T3 return. That makes CCH iFirm the one Canadian tax package an agent can, with the right subscription tier, write into directly. Desktop Taxprep and Cantax have no such interface.

Status, verified September 2026

The CCH iFirm Taxprep Web API, documented at version 2026.20, exposes get and set operations on return cells for T1, T2, and T3, authenticated with an API key or OAuth 2.0, with rate limits in the range of 30 to 100 requests per minute depending on the call. The Common, CRM and Jobs APIs cover contacts and work, with Swagger documentation. Wolters Kluwer's product page ties API access to the Pro package, and the CCH iFirm API overview is the commercial entry point.

There is no MCP server over any of it. The CCH iFirm Taxprep release notes for May and July 2026 contain nothing on MCP or agents. Wolters Kluwer's generative AI in Canada is CCH AnswerConnect, a research assistant inside CCH iFirm since January 2025, not an interface for outside agents. Desktop Personal Taxprep and Cantax have no public API; Wolters Kluwer positions CCH iFirm as the path forward for Cantax firms. All three are CRA-certified for the 2025 tax year.

Status verified September 2026. We re-check this page quarterly.

What an agent can do with Taxprep, Cantax and CCH iFirm today

On CCH iFirm Taxprep with API access, an agent can read the cells of a return and write into them, create and update contacts and jobs, and do it with an audit trail on the API side. Any MCP client can be pointed at a REST API through a thin wrapper, so a firm on the Pro package does not need to wait for Wolters Kluwer to ship an MCP server to have an agent populate slip fields from verified intake data, or to read a return back and compare it with the source documents. The rate limits are low enough that this is a per-file workflow, not a bulk one.

Without API access, the documented paths are the same as for other products: Auto-fill my return in CCH iFirm, TaxprepConnect for AFR in desktop Taxprep, and Cantax's own AFR, plus CSV import into any input cell in CCH iFirm, which will take a file an agent has produced. CCH iFirm Portal handles client document exchange; documents uploaded there are reachable to an agent through the CRM API on the Pro tier or otherwise after a person downloads them.

Where Armada T1 fits

Armada T1 is the system of record for Canadian T1 intake, with its own MCP server. It sits in front of Taxprep, Cantax, or CCH iFirm the same way: an agent reads each slip and receipt as it arrives, records the figures as validated section records with the source stored alongside, reconciles against what the file expected, and routes each open question as a task to the preparer or to the client. The preparer opens the return with a file that is known to be complete rather than one that is assumed to be. Armada T1 does not calculate or EFILE returns; the completed file is handed off to the CRA-certified tax software your firm already runs.

How to check for changes

Watch the CCH iFirm Taxprep release notes and the Web API documentation version number. Wolters Kluwer already has the API an MCP server would wrap, so if one arrives it will likely be a short announcement rather than a long beta. For the rest of the Canadian stack, see MCP servers for Canadian tax and accounting software.

This page describes third-party products as documented by their vendors in September 2026 and is not affiliated with or endorsed by Wolters Kluwer. Taxprep, Cantax, CCH iFirm, TaxprepConnect and CCH AnswerConnect are trademarks of Wolters Kluwer N.V. or its affiliates. Product availability changes; verify with the vendor before relying on it.

DT Max MCP server: what exists in September 2026

There is no DT Max MCP server, no DT Max API or SDK, and no announced AI-agent access for any product in Thomson Reuters' DT Professional Suite. Of the Canadian T1 packages, DT Max is the most closed to automation from outside: the only documented machine paths into a return are the CRA's Auto-fill my return and the program's own conversion and import utilities. That makes the intake layer in front of DT Max more important, not less.

Status, verified September 2026

The DT Max T1 product page and the DT Professional Suite products index describe no API, SDK, or developer program. The knowledge base has no integration or API topics. The program updates page, current to version 29.30 of June 17, 2026, lists tax-content and form changes and nothing on AI or agent access. Thomson Reuters markets AI research and workflow tools elsewhere in its portfolio; none of it is exposed through DT Max. DT Max is CRA-certified for the 2025 tax year.

Status verified September 2026. We re-check this page quarterly.

What an agent can do with DT Max today

An agent cannot open, read, or write a DT Max return. The documented paths into one are narrow. Auto-fill my return downloads slips and carryforwards from the CRA for authorized clients. DT Max converts prior-year files from competing products at setup. Everything else that is not on a CRA slip is keyed by the preparer from whatever the client sent.

The DT Max user guide documents keyword-based data entry, which is the interface a preparer works in and the reason DT Max firms tend to have fast keyers. An agent's contribution in that environment is to make sure that what gets keyed is complete and verified before anyone opens the file: every slip present, every figure read from the source document, every question the return depends on answered and recorded with a date. Keying from a reconciled intake file is quicker than keying from an inbox.

On the client side, DT Max integrates with Thomson Reuters' Onvio client portal for document exchange. Onvio has no public API for Canadian firms that we could find, so an agent reaches uploaded documents only after a person downloads them or through a browser session.

Where Armada T1 fits

Armada T1 is the system of record for Canadian T1 intake, with its own MCP server. For a DT Max firm it is the structured layer that DT Max itself does not offer to outside tools: an agent reads each slip and receipt as it arrives, records the figures as validated section records with the source stored alongside, reconciles against what the file expected, and routes each open question as a task to the preparer or to the client. The preparer opens DT Max with a file that is known to be complete, and keys or imports from it. Armada T1 does not calculate or EFILE returns; the completed file is handed off to the CRA-certified tax software your firm already runs.

How to check for changes

Watch the program updates page and the knowledge base for any new integration topic. Thomson Reuters' broader AI announcements are worth reading with the question of whether DT Max is named; so far it has not been. For the rest of the Canadian stack, see MCP servers for Canadian tax and accounting software.

This page describes third-party products as documented by their vendors in September 2026 and is not affiliated with or endorsed by Thomson Reuters. DT Max, DT Professional Suite and Onvio are trademarks of Thomson Reuters or its affiliates. Product availability changes; verify with the vendor before relying on it.

ProFile and Pro Tax MCP server: what exists in September 2026

There is no MCP server for ProFile or for Pro Tax, Intuit's two Canadian tax preparation products. Intuit does ship an official MCP server, and it is a good one, but it covers QuickBooks Online accounting objects only; none of its tools open a return. ProFile has a partner API that is granted by application rather than published. For an agent working a Canadian T1 file today, ProFile and Pro Tax are destinations reached through their own import features, not systems the agent can call.

Status, verified September 2026

The ProFile Partner Program page describes APIs available to partners through a request form; there is no public reference and no self-serve access. Intuit's quickbooks-online-mcp-server is documented on the QuickBooks Online MCP server page; its 144 tools cover QuickBooks Online entities and none of them touch ProFile or Pro Tax. The Pro Tax feature page and ProFile's What's New mention no AI-agent access.

The nearest Intuit has come is the Intuit Accountant Suite, launched in Canada on February 17, 2026, which brings Intuit's AI assistant to the firm's QuickBooks Online Accountant workspace and syncs with Pro Tax. That is Intuit's own agent inside Intuit's own product, not an interface an outside agent can use. Both products are CRA-certified for the 2025 tax year.

Status verified September 2026. We re-check this page quarterly.

What an agent can do with ProFile and Pro Tax today

An agent cannot open, read, or write a ProFile or Pro Tax return. It can feed the import paths and drive the client-facing side.

ProFile pulls slips and carryforwards from the CRA through Auto-fill my return, singly or in batch, and imports GIFI data from QuickBooks Online for business returns. Both products carry forward prior-year files from other suppliers, including TaxCycle. For clients whose books are in QuickBooks Online, the QuickBooks Online MCP server lets an agent pull the calendar-year figures and reconcile them before a preparer keys or imports anything, which is the one place Intuit's MCP work already helps a Canadian T1 practice.

On the client side, Hub & Link is ProFile's portal for document collection and e-signature, and Pro Tax uses the client request features of QuickBooks Online Accountant. Neither has a public API, so an agent reaches uploaded documents only after a person downloads them or through a browser session.

Where Armada T1 fits

Armada T1 is the system of record for Canadian T1 intake, with its own MCP server. It is the layer between the client's documents and ProFile or Pro Tax: an agent reads each slip and receipt as it arrives, records the figures as validated section records with the source stored alongside, reconciles against what the file expected, and routes each open question as a task to the preparer or to the client. The preparer opens the return with a file that is known to be complete. Armada T1 does not calculate or EFILE returns; the completed file is handed off to the CRA-certified tax software your firm already runs.

How to check for changes

Watch ProFile's What's New and the Intuit developer blog. If Intuit adds tax-product tools to its MCP server, the GitHub repository is where they would appear first. For the rest of the Canadian stack, see MCP servers for Canadian tax and accounting software.

This page describes third-party products as documented by their vendors in September 2026 and is not affiliated with or endorsed by Intuit. ProFile, Pro Tax, QuickBooks, QuickBooks Online and Hub & Link are trademarks of Intuit Inc. Product availability changes; verify with the vendor before relying on it.

TaxCycle MCP server: what exists in September 2026

There is no TaxCycle MCP server. TaxCycle has a developer API, but it is licensed to selected partners under a written agreement rather than published, and TaxCycle has announced no AI-agent access of any kind. Its parent company, Xero, ships an official MCP server for Xero accounting; none of that reaches TaxCycle. What TaxCycle does have is the widest set of documented data import paths of any Canadian T1 package, and those are the doors an agent's output goes through today.

Status, verified September 2026

The TaxCycle Software Developer API licence, last updated January 7, 2025, is the only public trace of the API: a legal agreement, with no portal, no reference documentation, and no self-serve sign-up. The integrations help topic covers DoxCycle, TaxFolder, and CRA services and does not mention an API or MCP. The only AI TaxCycle has announced is KYRA, a website support assistant launched February 24, 2026. Release 16.0.63710.0 of July 16, 2026 contains nothing on either subject.

Xero's xero-mcp-server is documented on the Xero MCP server page. It exposes Xero accounting objects only. TaxCycle is CRA-certified for the 2025 tax year under Xero Software (Canada) Limited.

Status verified September 2026. We re-check this page quarterly.

What an agent can do with TaxCycle today

An agent cannot open, read, or write a TaxCycle return. What it can do is prepare the structured data that TaxCycle's data import features accept, and drive the client-facing side.

The import paths are specific. Auto-fill my return pulls slips and carryforwards from the CRA for authorized clients, in batches of up to ten. Excel import for slips and Excel import for forms load structured rows into slip and form fields from a spreadsheet in TaxCycle's template layout. XML slip import takes CRA-format slip XML. DoxCycle recognizes scanned slips and posts amounts into the return. Any of these will take a spreadsheet or file an agent has produced, and a preparer stays in control of the import.

On the client side, TaxFolder is TaxCycle's portal, and a preparer can ask a client to upload documents from inside the return. TaxFolder has no API either, so an agent reaches the uploaded documents only after a person downloads them or through a browser session.

Where Armada T1 fits

Armada T1 is the system of record for Canadian T1 intake, with its own MCP server. It is the layer between the client's documents and TaxCycle: an agent reads each slip and receipt as it arrives, records the figures as validated section records with the source stored alongside, reconciles against what the file expected, and routes each open question as a task to the preparer or to the client. The preparer opens TaxCycle with a file that is known to be complete rather than one that is assumed to be. Armada T1 does not calculate or EFILE returns; the completed file is handed off to TaxCycle, and TaxCycle's own import features are the documented route for structured data into a return.

How to check for changes

Watch the TaxCycle news page and the integrations topic. If Xero extends its MCP program to TaxCycle, it will most likely appear first in Xero's AI Toolkit FAQ. For the rest of the Canadian stack, see MCP servers for Canadian tax and accounting software.

This page describes third-party products as documented by their vendors in September 2026 and is not affiliated with or endorsed by Xero or TaxCycle. TaxCycle, DoxCycle, TaxFolder and Xero are trademarks of Xero Limited or its affiliates. Product availability changes; verify with the vendor before relying on it.

Jetpack Workflow MCP server: what exists in September 2026

There is no Jetpack Workflow MCP server, and there is no public Jetpack Workflow API for one to be built on. The only programmatic door is Zapier, which exposes client and job creation, and Zapier in turn wraps those actions in its own MCP catalogue. That is thinner than any other practice management platform on this list. It is also the platform where we have already shown that an agent can run T1 intake end to end without an API, so the absence is a constraint rather than a stop.

Status, verified September 2026

Jetpack Workflow's current knowledge base answers the integrations question directly: not currently. There is no developer documentation and no API reference anywhere on jetpackworkflow.com. The company has not announced MCP support or any AI features.

The Zapier app is documented in the Classic knowledge base, and Zapier's listing shows two triggers (new client, updated client) and a handful of actions: create job from a template, create client, update client, find client, find or create client. Zapier's MCP catalogue exposes the same actions as a Jetpack Workflow server. Because the documentation lives in the Classic help centre and the current FAQ says there are no integrations, we treat the Zapier path as confirmed for Classic accounts and unconfirmed for the current app; check with Jetpack Workflow support before building on it. The QuickBooks Online integration for client import and time sync is documented the same way.

Status verified September 2026. We re-check this page quarterly.

What an agent can do with Jetpack Workflow today

Two things, and the second matters more than the first.

Through Zapier, an agent can create a client, create a job from one of the firm's templates, and look a client up. That is enough to open a 2025 T1 job for every client on a list, and nothing more: no reading of tasks or comments, no status changes, no documents, because Jetpack Workflow stores none.

Through a browser, inside the preparer's own logged-in session, an agent can do everything a person can. We built and published this: Jetpack Workflow and Google Drive: T1 intake run by an AI agent, no API required. The agent reads the client's slips and receipts from a Google Drive folder, records the figures in the tax file, opens the T1 project in Jetpack Workflow from the firm's template, links the two systems in the project description, and leaves the follow-ups as tasks a preparer will see. Screen-driving is slower per action and more brittle than an API, and it still closed the loop.

Where Armada T1 fits

Armada T1 is the system of record for Canadian T1 intake, with its own MCP server. In a Jetpack Workflow firm it does the job the practice management system cannot: it holds the documents, records slip and receipt data as validated section records with the source stored alongside, tracks what is still outstanding, and runs the completeness check before a file moves. The agent routes each open question as a task to the preparer or to the client, with Jetpack Workflow carrying the job and its tasks as it always has. Armada T1 does not calculate or EFILE returns; the completed file is handed off to the CRA-certified tax software your firm already runs.

How to check for changes

Watch the knowledge base FAQ for the integrations answer to change and the Zapier listing for new triggers, particularly anything task-level. For the rest of the Canadian stack, see MCP servers for Canadian tax and accounting software.

This page describes third-party products as documented by their vendors in September 2026 and is not affiliated with or endorsed by Jetpack Workflow. Jetpack Workflow is a trademark of Jetpack Workflow, Inc. Zapier is a trademark of Zapier, Inc. Product availability changes; verify with the vendor before relying on it.

TaxDome MCP server: what exists in September 2026

TaxDome has promised an MCP server, put it into beta over the summer of 2026, and committed to general availability by the end of the third quarter. As of mid-September it is not generally available, and TaxDome's API, which the MCP server will sit on, is still in private beta. For a Canadian firm on TaxDome, the practical position is that agent access is weeks or months away rather than years, but nothing you can sign up for today.

Status, verified September 2026

TaxDome's Spring 2026 quarterly update, published June 19, 2026, says the API is in private beta and that MCP support is on the way, along with TaxDome Agents. The Summer Update 2026 webinar recap of June 30 describes the MCP server as a way to connect TaxDome to Claude, ChatGPT, or Copilot, puts it in beta over the summer, and gives end of Q3 2026 as the target for general availability. The product updates page shows no MCP or public API release as of September 17, 2026, and the integrations overview lists no public API. There is no TaxDome connector in Claude's directory and no ChatGPT app.

Zapier lists a TaxDome server in its MCP catalogue. It is a third-party wrapper over Zapier's TaxDome actions, not a TaxDome product, and its coverage follows what TaxDome exposes to Zapier.

Status verified September 2026. We re-check this page quarterly, and given the stated Q3 target we will re-check this one in October.

What an agent can do with TaxDome today

Without an API or MCP server, an agent cannot read or write TaxDome directly. What it can do is work at the edges. TaxDome's organizers collect answers with conditional logic and roll last year's answers forward, and the completed organizer and the uploaded documents can be exported as files; an agent can read those files. TaxDome's Canadian edition prints returns from Canadian tax programs into the client's account, which is a one-way path from tax software into TaxDome rather than the reverse. Zapier's actions cover contacts and a limited set of triggers, which is enough to notify an agent that something happened but not to run intake from inside TaxDome.

That is the gap the MCP server is meant to close. The questions that will matter when it ships are whether it exposes organizer answers as structured data rather than PDFs, whether it can create and update client tasks and document requests, and whether it can read the document library with enough metadata to tell a 2025 T4 from a 2024 one.

Where Armada T1 fits

Armada T1 is the system of record for Canadian T1 intake, with its own MCP server. It is where the answers and the figures go once an agent has read them: slip and receipt data recorded as validated section records with the source stored alongside, an expected-document list seeded from last year, and a completeness check that names every open item. The agent routes each open question as a task to the preparer or to the client, and when TaxDome's MCP server ships, the client-facing half of that can run through TaxDome's own tasks and requests. Armada T1 does not calculate or EFILE returns; the completed file is handed off to the CRA-certified tax software your firm already runs.

How to check for changes

Watch the product updates page and the TaxDome updates blog. When the API leaves private beta, TaxDome will need to publish developer documentation somewhere; that page appearing is the signal. For the rest of the Canadian stack, see MCP servers for Canadian tax and accounting software.

This page describes third-party products as documented by their vendors in September 2026 and is not affiliated with or endorsed by TaxDome. TaxDome is a trademark of TaxDome, Inc. Claude is a trademark of Anthropic, PBC. ChatGPT is a trademark of OpenAI. Copilot is a trademark of Microsoft Corporation. Product availability changes; verify with the vendor before relying on it.

Karbon MCP server: what exists in September 2026

Karbon announced a public MCP server on June 3, 2026, alongside Kai, its AI coworker. As of mid-September 2026 it has not shipped: Kai is in limited early access, and neither the product release notes nor the API release notes mention an MCP server. What Karbon does have, and has had for years, is a well-documented REST API, which is why it is already the easiest Canadian practice management platform to put an agent in front of.

Status, verified September 2026

The announcement is in Karbon's June 3, 2026 press release and on Karbon's own site, which describe a public MCP server that connects Karbon to external AI tools over an open standard. The Kai feature page shows Kai in early access and says nothing about MCP. Karbon's product release notes through August 31, 2026 and its API release notes through September 8, 2026 contain no MCP release. There is no Karbon connector in Claude's directory and no ChatGPT app.

The API is documented at developers.karbonhq.com. It is a REST API authenticated with a bearer token plus a per-firm AccessKey header rather than OAuth, and it covers contacts, organizations, work items, notes, timelines, and client requests. A community-built karbon-mcp-server wraps parts of that API; it is unofficial and unsupported by Karbon. Zapier's MCP catalogue includes Karbon with contact actions only.

Status verified September 2026. We re-check this page quarterly, and we expect this one to change first.

What an agent can do with Karbon today

Quite a lot, through the API. An agent can find a client's contact and work item, read the notes and timeline on a tax job, post a note, move a work item through its workflow statuses, and create client requests, which are the tracked to-do items the client sees in the Karbon for Clients portal. That last one is the piece that matters for intake: a missing-document follow-up becomes a specific request assigned to the client, with Karbon's own reminders behind it, instead of an email a preparer has to remember to send.

We built and published exactly this. Karbon T1 intake with an AI agent walks through an agent that watches for documents arriving on a Karbon work item, records the figures in the tax file, and turns each gap into a Karbon client request. When Karbon's MCP server ships, the API calls in that build become MCP tool calls; the workflow does not change.

Where Armada T1 fits

Armada T1 is the system of record for Canadian T1 intake, with its own MCP server. Karbon holds the client relationship and the work item; Armada T1 holds the tax file. An agent connected to both reads each document as it arrives, records slip and receipt data as validated section records with the source stored alongside, identifies the questions and documents still open, and routes each one as a task to the preparer or, through a Karbon client request, to the client. Armada T1 does not calculate or EFILE returns; the completed file is handed off to the CRA-certified tax software your firm already runs.

How to check for changes

Watch the API release notes and the Kai page. When the MCP server ships, the things to look for are whether it is hosted or local, whether it covers client requests and work item statuses or only contacts, and whether it is priced with Kai or included with the API. For the rest of the Canadian stack, see MCP servers for Canadian tax and accounting software.

This page describes third-party products as documented by their vendors in September 2026 and is not affiliated with or endorsed by Karbon. Karbon, Kai and Karbon for Clients are trademarks of Karbon, Inc. Claude is a trademark of Anthropic, PBC. Product availability changes; verify with the vendor before relying on it.

Xero MCP server: what exists in September 2026

Yes. Xero publishes an official MCP server, it works with any MCP client that supports local servers, and Xero's hosted Claude connector is available to Canadian subscribers. Of the accounting and practice platforms a Canadian firm might run, Xero is the one where an agent can be connected this afternoon with nothing more than a Xero login. The limits are real, though: the hosted connector is read-only, and none of it reaches TaxCycle, the Canadian tax software Xero owns.

Status, verified September 2026

The official server is at github.com/XeroAPI/xero-mcp-server. It is a local server that runs over stdio, authenticates with a Xero developer app through OAuth 2.0 (client credentials or the standard authorization flow), and exposes tools over contacts, invoices, bills, payments, bank transactions, accounts, journals, and reports including the trial balance and profit and loss. Xero's AI Toolkit FAQ says it works with any MCP client that supports local servers, and it confirms there is no hosted MCP endpoint yet.

The hosted Claude connector is generally available and Xero's Canadian page for it is at xero.com/ca/ai-in-accounting/claude. It is read-only: an agent in Claude can look up and summarise, and cannot post transactions. Xero's ChatGPT app went live on September 15, 2026, powered by JAX, Xero's own assistant. Underneath all of it is the Xero API on OAuth 2.0.

Xero has owned TaxCycle since December 2021. The MCP server and the connectors cover Xero accounting only. TaxCycle has no MCP server and no public API; see the TaxCycle MCP server page.

Status verified September 2026. We re-check this page quarterly.

What an agent can do with Xero today

For a firm's own practice or for a client's business, an agent connected to the local server can pull the year's profit and loss and balance sheet, list unreconciled bank lines, find the invoices and bills behind a figure, and, with the local server, create contacts and draft invoices. Through the hosted Claude connector the same questions can be asked in plain language inside Claude with no setup beyond signing in, read-only.

On a T1 file, Xero matters for self-employed clients and rental owners whose books live there. An agent can pull the calendar-year figures for the T2125 or T776, reconcile them against what the client reported on the intake questionnaire, and flag the categories that need a preparer's attention before anything is keyed into the return. For practice-level client questions, Xero's Ask in Xero HQ covers the firm's client list, but it is a Xero feature rather than a tool an outside agent can call.

Where Armada T1 fits

Armada T1 is the system of record for Canadian T1 intake, with its own MCP server. The same agent that reads a client's Xero books can record the business or rental summary, the vehicle and home-office figures, and the supporting statements as validated section records in the client's Armada T1 file, with the source stored alongside each figure. The file tracks what is still outstanding, and the agent 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 the CRA-certified tax software your firm already runs, TaxCycle included.

How to check for changes

Watch the AI Toolkit FAQ for a hosted MCP endpoint and for write access in the Claude connector, and the TaxCycle news page for any sign that Xero's MCP work is reaching its tax product. For the rest of the Canadian stack, see MCP servers for Canadian tax and accounting software.

This page describes third-party products as documented by their vendors in September 2026 and is not affiliated with or endorsed by Xero. Xero, Xero HQ, JAX and TaxCycle are trademarks of Xero Limited or its affiliates. Claude is a trademark of Anthropic, PBC. ChatGPT is a trademark of OpenAI. Product availability changes; verify with the vendor before relying on it.

QuickBooks Online MCP server: what exists in September 2026

Yes, there is an official QuickBooks Online MCP server, and it is the most complete one any vendor on this list has shipped. Intuit publishes it as an open-source local server, and QuickBooks is also available inside Claude and ChatGPT as a hosted connector. The catch for a Canadian firm is that the hosted Claude connector is restricted to US customers, so the local server and the API are the routes that work from Canada today.

Status, verified September 2026

Intuit's local MCP server is at github.com/intuit/quickbooks-online-mcp-server. It runs on your machine over stdio, authenticates with your own Intuit developer app and OAuth 2.0 tokens, and exposes 144 tools that read and write QuickBooks Online accounting objects (customers, invoices, bills, payments, accounts, reports). Intuit still labels it an early preview, as it did when it announced the server in October 2025. It works with any MCP client that supports local servers, including Claude Desktop and Claude Code.

The hosted QuickBooks connector for Claude went live on April 23, 2026 and gained write actions such as invoicing and payroll on July 28, 2026, alongside a ChatGPT app. Intuit's help article for the Claude connector, updated August 5, 2026, states that it is currently available to US customers only. Canadian QuickBooks Online Accountant subscribers cannot enable it yet.

Underneath both is the QuickBooks Online REST API v3, OAuth 2.0, with Canadian companies supported through the same developer program. Zapier also lists a QuickBooks Online server in its MCP catalogue, which is a third-party wrapper over Zapier actions rather than an Intuit product.

Status verified September 2026. We re-check this page quarterly; if you find the Claude connector available in Canada before we do, tell us.

What an agent can do with QuickBooks Online today

For a Canadian firm, an agent connected through the local MCP server or the API can read a client's books, pull trial balances and general ledger detail, list customers and vendors, and create or update transactions. On the T1 side, that matters for self-employed clients whose T2125 comes from a QuickBooks Online file: an agent can pull the profit and loss for the calendar year, reconcile it against what the client reported on the intake questionnaire, and flag the categories a preparer should look at before anything is keyed into the return.

What the QuickBooks Online server does not touch is tax preparation. Intuit's Canadian T1 products, ProFile and the Pro Tax module inside QuickBooks Online Accountant, have no MCP server and no public API for returns; we cover them on the ProFile and Pro Tax MCP server page. Pro Tax can import GIFI from QuickBooks Online and carry forward from other suppliers, but those are features of the desktop and web products, not tools an agent can call.

Where Armada T1 fits

Armada T1 is the system of record for Canadian T1 intake, with its own MCP server. The same agent that reads a client's QuickBooks Online books can record the business income summary, the vehicle and home-office figures, and the supporting statements as validated section records in the client's Armada T1 file, with the source stored alongside each figure. The file tracks what is still outstanding, and the agent 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 the CRA-certified tax software your firm already runs, ProFile and Pro Tax included.

How to check for changes

Watch the GitHub repository for the preview label to come off, and the Claude connector help article for the US-only line to change. Intuit's Canada developer topic is where Canadian API differences are posted. For the rest of the Canadian stack, see MCP servers for Canadian tax and accounting software.

This page describes third-party products as documented by their vendors in September 2026 and is not affiliated with or endorsed by Intuit. QuickBooks, QuickBooks Online, ProFile and Pro Tax are trademarks of Intuit Inc. Claude is a trademark of Anthropic, PBC. ChatGPT is a trademark of OpenAI. Product availability changes; verify with the vendor before relying on it.