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.

Previous
Previous

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

Next
Next

Jetpack Workflow MCP server: what exists in September 2026