A controller pulling up Claude mid-meeting to ask "what's our cash position right now" used to mean exporting a QuickBooks report first and then pasting the numbers into Claude. Intuit and Anthropic built a direct line between QuickBooks Online and Claude to make things much simpler.
CData Connect AI gives that same connection a governed path for teams that need more than one system in the conversation.
What connecting QuickBooks Online to Anthropic means in 2026
Connecting QuickBooks Online to Anthropic means giving Claude live, authenticated access to accounting data, so a controller can ask a question in natural language and get an answer from live books.
Quick definition: MCP (Model Context Protocol)
An open standard, introduced by Anthropic in November 2024, that lets AI applications connect to external data sources through one protocol instead of custom code for every integration. Anthropic donated MCP to the Linux Foundation's Agentic AI Foundation in December 2025, so it's now an open, vendor-neutral standard.
That open standard is why setups are faster to build and easier to govern than custom scripting projects. There are now two official paths into Claude: the Intuit QuickBooks connector listed in Claude's own connector directory, and Intuit's open-source MCP server for developers who want to build on top of it directly.
Before you begin: prerequisites and how the integration works
Before you connect anything, confirm you have:
An active Claude account.
An active QuickBooks Online or Intuit Enterprise Suite subscription (the Intuit connector currently serves US customers only, though more regions are planned).
Admin access to the QuickBooks account.
Claude reaches your books through Intuit's authorized OAuth connection. It doesn't scrape data or store your credentials, and Intuit's documentation states that QuickBooks data accessed this way isn't used to train Claude.
If you're building a custom MCP route instead of using the hosted connector, you'll also need to register an app on the Intuit Developer Portal and complete a one-time, browser-based OAuth handshake before Claude can authenticate.
Route | Access level | Best for |
Intuit QuickBooks connector (Claude directory) | Read and write, with draft confirmation before anything sends | Finance operators who want answers in Claude chat, no setup |
Intuit's open-source MCP server | Developer-configured | Teams building their own agent workflows on raw QuickBooks data |
CData Connect AI | Read and write, governed through one endpoint | Teams running QuickBooks alongside other systems Claude needs to reach |
Key terms: MCP, OAuth passthrough, and the managed endpoint
Quick definition: OAuth passthrough
A model where the AI connection enforces your existing source-system permissions at runtime, instead of granting Claude a separate, broader set of standing permissions.
A managed MCP endpoint is a single hosted URL that connects Claude chat, Claude Desktop, Claude Code, and the Anthropic Agent SDK to many systems at once, QuickBooks included.
Connect AI provides one governed MCP endpoint (https://mcp.cloud.cdata.com/mcp) that you can add directly to a client's Remote MCP Server URL field. The endpoint covers every source Claude needs to reach, QuickBooks today and any other application that the team adds later.
Why CData Connect AI (Anthropic's certified connectivity partner)
Anthropic selected Connect AI to bring enterprise data connectivity to Claude. One MCP endpoint connects Claude chat, Claude Desktop, Claude Code, and the Anthropic Agent SDK to hundreds of systems, QuickBooks Online among them.
The advantage grows once QuickBooks is no longer the only system Claude needs to reach. An independent MCP server built against the GitHub repository runs locally, and you own the developer app registration and OAuth token management yourself, patching included. Connect AI handles that layer and pushes joins, filters, and aggregations down to the source, so Claude spends its reasoning budget on the answer.
Step-by-step: connect QuickBooks Online to Claude
Using the direct Intuit connector:
Open Claude.ai and select Settings, then Connectors under Customize in the sidebar.
Search for "QuickBooks," in the Discover tab, select the "Intuit QuickBooks" connector, and click Connect.
Sign in with your Intuit account, pick the company to connect, and choose which permissions to grant Claude.
Confirm the connection by asking Claude a read request, such as a profit and loss summary. Once active, the connector can also benchmark you against industry peers, import and categorize transactions, and create invoices and estimates.
Using Connect AI for a governed, multi-source route:
Configure a QuickBooks Online data source inside Connect AI.
Open Claude.ai and select Settings, then Connectors under Customize in the sidebar, and log into your Connect AI account.
Click on the "+" button in the Claude chat, navigate to Connectors and ensure that the Connect AI MCP toggle is enabled. This provides Claude with direct governed access to your Quickbooks Online data via Connect AI.
If you build your own MCP server instead of using hosted route, double-check the redirect URI registered in the Intuit Developer Portal. It must match exactly, protocol, host, port, and path, or authorization fails before you get anywhere near Claude.
Request live QuickBooks data in Claude: example prompts and use cases
Once QuickBooks is connected, a few natural-language requests cover most of what an operator needs day to day:
"Which invoices are overdue right now?"
"Draft an invoice for Acme Co. for $1,500 in June design work."
"Summarize our current cash position across all accounts."
Claude asks for explicit confirmation before it sends an invoice or payment reminder, or deletes an invoice or estimate, so nothing changes in QuickBooks without someone approving it first.
Prompt | What Claude does | Access needed |
"Show me open invoices" | Returns a live accounts receivable list from QuickBooks | Read |
"Invoice Acme Co. for June design work" | Drafts an invoice for approval, then sends it | Read and write |
"What's our cash position this week?" | Pulls and summarizes current account balances | Read |
The consumer connector isn't built for juggling many client files at once, so firms managing multiple clients are better served by a read and write MCP route, where Connect AI's governance model scales more naturally than reconnecting the same consumer connector company by company.
Governance, security, and troubleshooting for QuickBooks + Claude
OAuth and SSO passthrough are the reason IT can treat this as governed access. They enforce QuickBooks' existing source-system permissions automatically, at runtime.
On top of that, Connect AI applies the controls, covered in full in its governance and audit controls documentation:
Least-privilege controls, so Claude gets only the read or write scope a given task needs.
CRUD restrictions, enforced per connection.
Audit trails that log who accessed what and when, available for routing to a SIEM platform. For IT teams that need to prove this to an auditor, Connect AI's audit trail guide covers what gets logged and why it holds up under review.
Quick definition: least-privilege
Granting an AI connection only the minimum read or write scope a task requires.
Both Intuit routes authenticate through Intuit's official OAuth flow, so Claude reaches your books through the authorized API, with no password stored in the connection.
If something looks off:
Verify the discrepancy in QuickBooks first, then contact QuickBooks support if the data itself is wrong.
For a self-hosted MCP server, check the redirect URI again. Production requires a public HTTPS callback, while sandbox environments allow localhost, and mixing the two is the most common cause of a failed handshake.
Start requesting QuickBooks Online data in Claude with CData Connect AI
Anthropic selected CData Connect AI as its connectivity partner, so one managed MCP endpoint carries QuickBooks Online's existing OAuth permissions straight into Claude. A finance operator gets live financials in chat without filing an IT ticket. A solutions engineer gets one governed endpoint that works the same way across Claude chat, Desktop, Code, and the Agent SDK.
Start a free trial of CData Connect AI.
Frequently asked questions
What do I need before I can connect QuickBooks Online to Anthropic's Claude?
An active Claude account and an active QuickBooks Online or Intuit Enterprise Suite subscription. The Intuit connector is US-only for now. A custom MCP route also needs a registered app on the Intuit Developer Portal.
How do I connect QuickBooks Online to Claude using CData Connect AI's MCP endpoint?
Configure a QuickBooks Online source in CData Connect AI, create a Remote MCP URL, then add "https://mcp.cloud.cdata.com/mcp" to Claude's Remote MCP Server URL field and authenticate.
Can Claude read and write live QuickBooks Online data, or is it read-only?
Both. Claude can pull live reports and also create invoices or send reminders, but it always shows a draft first and asks for confirmation before anything is created, sent, or deleted.
What can I actually do with Claude once it's connected to my QuickBooks Online account?
Pull a live accounts receivable list, summarize cash position, generate a profit and loss report, benchmark against industry peers, and import and categorize transactions, useful for month-end close and variance analysis.
How does CData Connect AI keep my QuickBooks Online data secure when Claude accesses it?
OAuth and SSO passthrough enforce QuickBooks' existing permissions at runtime. CData Connect AI adds least-privilege controls, CRUD restrictions, and audit trails available for routing to a SIEM platform.
Can I use QuickBooks Online as an MCP server with Claude Code or the Anthropic Agent SDK?
Yes. CData Connect AI's managed endpoint works the same way across Claude chat, Desktop, Code, and the Agent SDK. Developers can also build against Intuit's open-source MCP server on GitHub, managing their own OAuth tokens.
What should I do if Claude can't access my QuickBooks Online data after setup?
Confirm the issue exists in QuickBooks first. For a self-hosted MCP server, check the redirect URI matches exactly on protocol, host, port, and path, since mixing sandbox and production callbacks is the most common cause of failure.