Dext AI Connector: Practice Data in Claude and ChatGPT

Dext announced the Dext AI Connector on October 22, 2026, a read-only server that lets accounting and bookkeeping practices query their Dext practice data from Claude, ChatGPT and Microsoft Copilot in plain language.

The connector is built on the Model Context Protocol (MCP), the open standard that lets AI tools call outside systems. It is the first time a bookkeeping automation vendor of Dext’s size has put its practice dashboards behind that standard for the three most widely used assistants.

For practice partners, the change is where the answer comes from. A question such as which clients have the lowest health scores is answered from Dext’s own records, not from a general model’s guess.

What the Dext AI Connector exposes

Dext’s help centre lists the data the connector can reach: clients, time tracking, financial snapshots, aged debtors and creditors, UK tax estimates, journals, fixed assets, bank balances and workflows. The list is not exhaustive, and Dext says some data is not yet available.

Dext gave examples of the questions partners can ask. They include which clients have the lowest health scores, which client took the most time last month, what a client’s live cash position looks like before a call, and which clients are missing a dividends account ahead of year end.

Partners can already see this data across Dext dashboards, from practice insights to team performance. The connector adds a second route to the same figures, from whichever AI tool the partner already has open.

The Dext AI Connector runs on the same models as the rest of Dext’s AI, which the company trained over more than 16 years and 2 billion receipts and invoices.

Permissions and the read-only limit

The connector is read-only. It cannot make changes in Dext, and Dext has not described any write-back to Xero, QuickBooks or any other accounting platform. Everything it does is retrieval.

It is also permission-aware. The tool surfaces only the data a user can already see inside Dext, with no elevated access. A junior bookkeeper who cannot open a client in Dext cannot reach that client through Claude either.

Chief executive Sabby Gill framed the design as a limit on the AI’s role.

“General-purpose AI is already part of how many practices work, but it doesn’t know a practice’s real numbers. AI Connector closes that gap: it puts the same Dext data our users already trust into the AI tools they’re already using, so the answer they get back is grounded in their own practice, not a guess.”

Sabby Gill, Chief Executive, Dext

Gill added that the launch is “an early step, and one we expect to build on.” Dext’s description is that the AI does the retrieving and the practice still does the deciding.

Dext’s help centre for the Dext AI Connector does not describe audit logging, and its setup articles point to a separate page on data security. Firms with client confidentiality obligations should read that page, and Dext’s Trust Center, before approving the connector.

Once data passes into Claude, ChatGPT or Copilot, the AI vendor’s own retention and training terms apply. That is a question for the firm’s workspace settings, not for Dext.

Which plans and accounts can use it

Availability is narrow. The Dext AI Connector works with Practice accounts only. Dext’s help centre says it is not yet available for Business accounts, and a Business admin cannot connect even with full admin rights.

Accountants and bookkeepers on the Practice Advanced plan can request access. Dext has not published a separate price for the connector. Its help articles set out eligibility by account type, not by fee.

The route to access differs by assistant:

Claude: the connector is listed in the Claude directory, and an organisation admin adds it from connector settings.
ChatGPT: it is listed in ChatGPT’s plugins, and an admin sets an installation policy for each role.
Copilot: firms contact their Dext account manager or support, then add Dext as an MCP tool in Copilot Studio.

Setup is done at workspace level, so personal Claude or ChatGPT accounts cannot use it. A firm’s IT administrator must add the connector first. Each user then authorises it once with their own Dext login, a process Dext puts at a couple of minutes.

Each Dext practice account can authenticate only one workspace. Firms that run separate AI environments need to pick the right one.

Copilot and the credential setting

The Copilot route carries the most risk. Agents published to a shared workspace should use end-user credentials, so colleagues with fewer privileges do not see Dext data they should not. Dext says this is the default and tells admins to check it under the tool’s credential settings.

A firm that publishes a Copilot agent with a partner’s shared credentials would defeat the permission model. The check takes seconds and belongs on the rollout list. Firms weighing wider use of Microsoft’s assistant can read Accountio’s coverage of Copilot in tax and audit.

Dext AI Connector and the wider MCP field

Dext sells to more than 12,000 accounting and bookkeeping firms and more than 700,000 businesses. Its move puts practice-level data, not ledger data, into the assistants firms already pay for.

That differs from where ledger vendors have focused. Xero, for one, has connected live ledger data to Google’s assistant, as covered in Accountio’s report on the Xero and Gemini integration. Practice questions about time spent, client health and missing accounts sit in the layer Dext manages, not in the general ledger.

Other vendors are also exposing spend data to chat assistants, as in the PEX AI launch. Practice management vendors such as Karbon, with its Kai coworker, are building AI inside their own products instead.

The split matters for budgets. A firm that wants one assistant across its tools needs each vendor to publish a connector. A firm that prefers an assistant inside each product relies on the vendors’ own models.

Dext has not named firms using the connector in production, and has published no usage figures or accuracy data.

What practices should do before connecting

The practical work sits with firm administrators. The data exposed is client data, so the same controls that apply to any outside processor apply here. Accountio’s guide to protecting client data sets out the baseline.

Three steps follow from Dext’s setup documentation. Confirm the practice is on a Practice account and the right plan. Check that user roles in Dext are correct, since the connector inherits them. For Copilot, confirm agents use end-user credentials.

Dext asks for feedback through its in-product chat assistant or at support@dext.com, with a screenshot and the AI tool used. Business account support, and a fuller list of covered data, are the next items to watch.