Qount MCP connector: what it reads, what access it gets, how to connect

Qount offers a read-only MCP Connector for its practice data on the Intelligence tier; data coverage, endpoint and sign-in aren't published. Verified 21 Oct 2026.

Official MCP connector · read-only

Hosting: Qount doesn't describe how the connector is hosted. The server URL is not published as of 21 Oct 2026. Qount doesn't publish a local server or public repo.
Auth: Not documented by the vendor.
Read / write: Currently read-only, per Qount: connected AI tools can't change the firm's Qount data.
Works with: ChatGPT, Claude and other MCP-compatible tools, per Qount.
Plan requirement: Qount Intelligence tier, per Qount. Qount's pricing page lists Intelligence at $139 per user per month billed annually ($149 monthly), with a $5,000 yearly minimum. The pricing page doesn't mention MCP.
Last changed: 2026-09-22: Qount announces the MCP Connector on the Intelligence tier (blog)
Verification: Verified 21 Oct 2026 by theFinanceStack · confidence: high

What can an agent do with Qount through MCP?

It can read the firm's Qount practice management data to answer questions, though Qount doesn't publish exactly which data the connector covers. It can't change anything in Qount.

Qount is practice management software for tax and accounting firms. Its 22 Sep 2026 announcement says firms can connect their Qount practice management data to AI tools and that the implementation is currently read-only.

Good to know

Qount doesn't publish which data types or tools the connector covers, or a tool count.
Its examples are partner questions about revenue and realization, pricing, staff capacity, overdue or bottlenecked work, and billing and collections trends.
Qount says sensitive client identifiers stay inside Qount and aren't exposed through MCP.
With no write path, there are no drafting, posting or payment tools to map.

Can

Read the firm's Qount practice management data to answer questions, per Qount; Qount doesn't publish exactly which data the connector covers

Cannot

Make any change to the firm's Qount data; Qount says the connector is currently read-only
Expose EINs, SSNs, dates of birth or addresses, which stay in Qount, per Qount

What access does it get?

Read-only access to the firm's Qount data. The firm decides which staff can use it and which tools they get. Qount doesn't publish scope names or the sign-in method.

Where	Scopes and permissions (as documented)	Admin requirement
Qount MCP Connector (hosted)	Not documented by the vendor. Qount says firms control which staff members have access and which tools they can use, and that the connector is read-only.	Qount Intelligence tier. Qount doesn't document who in the firm enables it. Claude Team/Enterprise: an Owner adds custom connectors. ChatGPT Business/Enterprise: an admin enables developer mode and publishes the app.

How do I connect it?

Qount doesn't publish setup steps or the server URL, so ask Qount for the connector address on an Intelligence account. Then add it as a custom connector in your AI client.

Ask Qount for the MCP Connector URL; Qount lists Claude as supported but doesn't publish the address.
In Claude (web or desktop), go to Customize › Connectors and choose Add custom connector. Team/Enterprise: an Owner adds it under Organization settings › Connectors.
Paste the URL from Qount, add it, then connect and complete whatever sign-in Qount presents.
In a chat, turn the Qount connector on from the connectors menu.

Not in Claude's connector directory as of 21 Oct 2026. These are Claude's standard custom-connector steps; Qount doesn't document its own.

What should a finance team watch for?

Qount says the connector is currently read-only. It hasn't published the endpoint, sign-in method, tool list, data coverage or limits, so ask Qount for these before connecting.

No published endpoint, auth method, scopes, tool list, data coverage or rate limits. Ask Qount for these before connecting.
Get the connector address only from Qount directly. Ignore addresses found in emails, forum posts or third-party lists, and check the address uses HTTPS on a Qount domain before an Owner adds it for the organisation. A look-alike address would receive the firm's practice data and sign-in details.
Limit access before connecting. Qount says firms control which staff members have access and which tools they can use, so give it only to the staff and tools that need it. In the AI client, a Claude Team/Enterprise Owner adds custom connectors and a ChatGPT Business/Enterprise admin publishes apps, so keep those roles narrow.
Plan cost: the connector is part of the Intelligence tier, which Qount prices at $139 per user per month billed annually ($149 monthly), against $114 for Pro and $74 for Essentials. Qount doesn't say whether every user must be on Intelligence to use the connector. There's a $5,000 yearly software minimum, and onboarding is a separate one-time fee that Qount sets by users and scope.
Currently read-only, per Qount, so the agent can't change Qount records; re-check this if Qount adds write tools. Answers are still AI summaries; check figures against Qount reports before relying on them.
If the connector returns free text such as task notes or client communications (Qount doesn't say), an injected instruction in that text could steer the agent's answer or push it to act in another connected tool. Keep approval on for any write-capable connectors in the same chat.
Answers send firm data to your AI provider. Qount says EINs, SSNs, dates of birth and addresses aren't exposed through MCP, and advises firms to review their AI provider's security and data-use settings. Qount makes no training statement; check its terms and your AI provider's.

How could finance teams and accounting firms use it?

Qount is built for tax and accounting firms. The connector is read-only, so it suits questions and reporting on work, capacity and billing.

Inside a company

For an internal tax or advisory team that runs its work in Qount, ask where work is becoming overdue or bottlenecked and who owns it.
See where staff capacity went this month across recurring close or tax work.
Draft a short brief on workload and capacity before a planning meeting, then edit it before sharing.

At an accounting firm

Ask where revenue and realization are falling short by client or service line (Qount gives this kind of example).
Spot overdue or bottlenecked work across the firm and see who has capacity to take it.
Draft a recurring management brief covering billing, collections and workload, then edit it before sharing.
Prepare for a client call by summarising recent activity, open work and billing status for that client, where the connector exposes it.

Whatever the use, a person reviews AI summaries before they reach clients, and any change to Qount stays a manual step in Qount.

Want Qount connected to Claude for your team?

We set up scoped, read-only connections and a review step for AI summaries before they reach clients. Fixed fee.

Book a 30-minute setup call

Change log

Date	Change	Source
2026-10-21	Re-verified: still read-only and on the Intelligence tier; data coverage, endpoint, auth and setup steps still unpublished; sensitive-field exclusion noted	qount.io/blog/using-mcp-to-make-ai-more-useful-for-accountin
2026-09-22	Qount announces its read-only MCP Connector, available on the Qount Intelligence tier	qount.io/blog/using-mcp-to-make-ai-more-useful-for-accountin

FAQ

Is this official?

Yes. Qount announced the MCP Connector on its own blog in September 2026. It isn't listed in Claude's connector directory, and Qount hasn't published technical documentation for it.

Is it free?

No separate MCP charge is documented, but the connector is part of the Qount Intelligence tier, which Qount lists at $139 per user per month billed annually. Your AI client may also need a paid plan.

Does it change data in Qount?

No. Qount says its MCP implementation is currently read-only, so connected AI tools can't change the firm's Qount data.

Is my data used to train models?

Qount doesn't address training. It says sensitive client identifiers aren't exposed through MCP and advises reviewing your AI provider's data-use settings. Check Qount's and your AI provider's terms before connecting.

Can my accountant use it on my behalf?

Qount doesn't document this. It says firms control which staff members have access and which tools they can use.

Something wrong or out of date? Tell us and we'll email you when it's fixed.

Sources

Verified by theFinanceStack, 21 Oct 2026. Vendor list on the CFO Software Market Map courtesy of Jason Staats; AI connectivity data by theFinanceStack. Not tax, compliance or financial advice.