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.
