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.
