Intuit pilots a hosted MCP server for AI agents in QuickBooks Online
Intuit is running an invitation-only pilot that lets AI assistants connect to QuickBooks Online through the MCP standard, at no charge for now.
Intuit is testing a hosted service that lets AI agents read and act on QuickBooks Online data. The service speaks the Model Context Protocol, usually shortened to MCP, an open standard that AI tools use to connect to other software. Access is by invitation only, through the Intuit App Partner Program, and participation is free for now. The vendor has warned that behavior and pricing may change.
For most readers, nothing changes today. Nothing appears in your settings, and there is nothing to install. The pilot matters if you build software on the QuickBooks platform, or if you want a preview of how AI assistants will plug into your books.
What is MCP, and why should QuickBooks users care?
MCP lets an AI client ask a server what it can do, then call those actions in the middle of a conversation. Intuit’s hosted server offers a curated set of QuickBooks Online actions in that shape. Desktop AI assistants, coding tools, and custom agents built on the major AI platforms can discover and invoke them.
Intuit hosts the service itself. Partners connect to one service instead of wiring their own bridge, and Intuit decides which actions to expose.
The design target is the agentic case, where the model chooses the next step rather than following a fixed script. The vendor’s guidance is direct on this point: predictable, code-driven integrations should stay on the standard QuickBooks Online developer interface. The pilot adds nothing for them.
Who is in the pilot, and how did they get there?
Membership is limited to invited partners in the Intuit App Partner Program. Onboarding runs through an assigned Intuit solution engineer. Each partner shares four things: the network addresses its app will connect from, its primary use case, the AI model behind the app, and its app identifier. Once cleared, the app can reach the hosted service.
We read the pilot terms closely, and three points stand out. Participation carries no charge. The software ships without guarantees, as a test. And Intuit reserves the right to change how it works, or to charge for it later.
Does this change how an app reaches your books?
No. Authorization follows the same account approval flow that connected apps use today. An app gets in only after you sign in and grant it, and its access is tied to a single company. Partners reuse the developer credentials they already hold, so there is no separate login system to learn.
You keep the off switch. An agent-style app will present a permission prompt like any other connected app. Read it, grant only what you understand, and remove apps you no longer use from your connected apps settings. That habit counts for more when software, not a person, chooses the next action.
What should you watch for?
Signals that the pilot is widening would include an open sign-up, published pricing, or the technology appearing inside partner apps you already use. The vendor cites quote-to-cash as an example use case, which points at quoting, invoicing, and payment follow-up as early territory.
A wider release would raise fair questions, such as the audit trail for actions an agent takes on its own. The pilot material does not answer them.
None of those signals has appeared. Until one does, the practical move for most readers is housekeeping rather than adoption.
Steps you can take now
If you build on the QuickBooks platform, the entry point is the partner program plus an assigned engineer, and your app must already sit in the developer portal. If your integrations are scripted and predictable, stay on the standard developer interface. The pilot serves a different kind of build.
For business owners and bookkeepers, there is nothing to enable. Review the apps connected to each company, drop the stale ones, and read the permission screen whenever an app mentions an AI agent. That prompt is where your control lives.