TaxDome Launches Client MCP Server for Accounting Firms

TaxDome released a client-facing Model Context Protocol server on November 4, 2026, letting a firm’s clients query their accountant from inside Claude, ChatGPT or any MCP-compatible assistant, at no charge under existing TaxDome pricing plans.

For firm owners the practical point is cost and exposure. The connection is included with the platform, independent of the firm’s AI add-on, so the budget question is settled. The harder questions are confidentiality and liability once client data passes through a third-party assistant.

The release follows TaxDome’s October 28 launch of a public API and MCP server aimed at firms, developers and AI agents. That product serves the firm’s side of the relationship. The new one serves the client’s.

What the TaxDome client MCP lets clients do

Clients connect their TaxDome account to their assistant and ask in plain language. TaxDome’s examples are “What’s outstanding?” and “Is my return ready?”

The assistant can answer questions about documents, requests and invoices, in the same chat the client already uses for other tasks. One connection covers all of a client’s entities, so an owner with several companies does not need a separate link for each.

When something needs a signature or a payment, the assistant hands over the exact link. One tap opens it in the TaxDome app, where the action is completed.

That design matters. The assistant surfaces status and routes the client to the firm’s own signing and payment screens, rather than taking the action itself.

TaxDome did not list messaging the accountant directly through the assistant among the launch features. Firms should treat the release as a status and retrieval tool, not a replacement for the client portal.

TaxDome pricing plans: no extra charge

The AI client experience is included with the TaxDome platform and carries no cost to firms or clients, the company said. TaxDome pricing plans therefore do not change for the client MCP.

It is also separate from the firm’s AI add-on. A firm that has not bought the add-on can still offer the client connection under its current plan.

Firms comparing TaxDome pricing plans against rivals can treat the client MCP as a feature rather than a line item. Current per-seat rates are on TaxDome’s pricing page, and the company’s plans are sold per user. Rival platforms are listed in Accountio’s guide to the best practice management software for accounting firms.

The cost to firms is not zero in practice. Someone has to tell clients the connection exists, explain what it shows and handle the questions that follow. That time is the real price of any pricing plan that bundles in a new channel.

Which AI assistants work with TaxDome

TaxDome named Claude and ChatGPT, plus any assistant that supports the open Model Context Protocol. The protocol lets an assistant call outside tools through a standard connection, so support is not tied to one vendor.

The wider accounting software market is moving the same way. Dext launched an AI connector for Claude, ChatGPT and Copilot, and PEX released PEX AI to link spend data to ChatGPT and Claude.

Karbon has taken a different route with Kai, an AI coworker that works inside the practice management system for staff. TaxDome’s client MCP puts the assistant on the client’s side of the table instead.

“Today this is for early adopters.”

Ilya Radzinsky, co-founder, TaxDome

Radzinsky said AI assistants and agents will become a bigger part of the consumer experience, and that accountants using TaxDome will be there to provide it. He framed the release as part of a wider push on the client experience across the mobile app, the web and the assistant.

How access is scoped and what is not yet clear

TaxDome said a connection sees only what the client already sees, through their own accounts and sign-in. It sees nothing of the firm’s data beyond that.

That is the central security claim, and it is a sound design choice. The assistant inherits the client’s permissions rather than the firm’s, so a connected assistant cannot reach other clients’ records or internal notes.

The announcement does not describe the authentication method, the consent screen a client sees when linking an assistant, or whether a firm can switch the feature off or limit which data types are exposed. Firms should put those questions to TaxDome before enabling the feature for a client book.

Those answers decide how a firm documents the rollout. A firm that can restrict exposure by client or data type has a different risk file from one that cannot.

Confidentiality and liability for the firm

In the United States, two regimes bear on the release. Section 7216 of the Internal Revenue Code restricts how tax return preparers use and disclose return information, and carries criminal penalties for knowing or reckless breaches. The statute is published at the Legal Information Institute.

The Federal Trade Commission’s Safeguards Rule, 16 CFR Part 314, implements the Gramm-Leach-Bliley Act and covers tax preparers as financial institutions. It requires a written information security programme, a risk assessment, access controls and oversight of service providers.

The client MCP changes the data flow in one specific way. The client, not the firm, initiates the connection and chooses the assistant. Information then travels to an AI provider the firm has no contract with.

That raises two practical points. A firm’s written security programme should record that the feature exists, what it exposes and why the firm considers the risk acceptable. Engagement letters should tell clients that responses from their assistant are the assistant’s output, not the firm’s advice.

Professional liability is the less settled question. If an assistant misreports a deadline or summarises a status incorrectly, the client may still look to the firm. The signing and payment links go to the firm’s own screens, which limits the risk for actions, but not for the answers the assistant gives in between.

Accountio asked TaxDome about authentication, firm controls and client consent. The company’s published materials do not cover them. Auditors are also beginning to ask how clients use AI, as set out in AICPA guidance on AI use in audits.

The same checks apply to onboarding. Firms using the tools in Accountio’s guide to client intake and KYC already hold identity data that should stay out of any assistant connection.

What TaxDome clients and firms should watch next

TaxDome calls the release a product for early adopters, so uptake will be small at first. Clients who already use Claude or ChatGPT daily are the likeliest first users.

Rivals will respond. Every practice management vendor now faces the same decision on whether to open a client-side connection, and the answer will be visible in their next release notes.

For firms on TaxDome, the next step is internal. Settle the consent wording, update the information security programme, and decide which clients to invite before the 2026 filing season starts.