SideQuest and Intuit's official QuickBooks Claude connector: AND, not OR
Intuit shipped an official QuickBooks connector for Claude this spring. Customers started asking us the same question: do I have to choose? The short answer is no. Install both. They never collide and they cover different parts of the job.
Here is the long answer, because the long answer is what wins back the people who already installed Intuit's tool and assumed they were done.
What Intuit's connector actually does
From Intuit's own docs and from the third-party reviews already out there: their connector is read-only. It lets Claude analyze your QuickBooks books — answer "what's my AR aging," "what's YTD revenue," "who are my top customers by quarter" — and generate reports. It does not create invoices. It does not record payments. It does not modify transactions. That's a deliberate Intuit choice and it's the right call for a v1 official connector.
So Intuit owns the analytics seat at the table. A distributor who wants to ask Claude questions about their existing books gets that for free now, from the vendor who literally writes QuickBooks.
What SideQuest does that Intuit's doesn't
SideQuest is the order-entry layer. The inbound side. The part of the day where your inside sales team retypes POs from Gmail into QuickBooks.
| Capability | Intuit's official | SideQuest |
|---|---|---|
| Ask "what's my AR aging?" | Yes | No |
| Generate financial reports / dashboards | Yes | No |
| Read books, query transactions | Yes | Partial (catalog + customer lookup) |
| Read inbound POs from Gmail | No | Yes |
| OCR scanned PO PDFs and faxes | No | Yes |
| Five-stage SKU matching cascade | No | Yes |
| Cross-reference auto-learning per customer | No | Yes |
| Write draft Estimates to QuickBooks | No | Yes |
| Draft Gmail replies to buyers | No | Yes |
| Local-first, customer data never leaves the user's computer | No (routes through Intuit cloud) | Yes |
The two connectors do not overlap on a single capability that matters.
How they coexist in Claude Desktop
Both register as separate MCP servers in claude_desktop_config.json. SideQuest's tools live under the namespace qb-distributor.*. Intuit's live under their own namespace. No tool-name collisions. Claude routes naturally — ask a financial-analysis question and Claude calls Intuit's connector; ask "process this incoming PO from Acme" and Claude calls ours. Same chat window. Same install of Claude Desktop. No friction.
One example from a customer test session last week. The rep asked, in one Claude conversation:
- "Top 5 customers by revenue this quarter." → Intuit's connector answered from QB's full ledger.
- "List my incoming purchase orders." → SideQuest answered from Gmail.
- "Draft an estimate for the first one." → SideQuest parsed the PO, matched lines, built the draft.
- "Submit it." → SideQuest pushed to QuickBooks.
- "What's my AR aging now after that estimate?" → Intuit's connector answered the financial impact.
Claude never had to be told which connector to use. The tool descriptions are specific enough that Claude picks correctly. The customer gets read + write + email + analytics in one continuous conversation, from two MCP servers that don't know each other exist.
The data-privacy difference
Intuit's connector routes through their cloud. That's how all consumer-grade hosted MCP connectors in Claude Desktop work — there's no local execution. The data leaves your machine in the normal way Anthropic and Intuit have already arranged.
SideQuest runs locally. The Python process executes on the customer's own computer. Their QuickBooks Estimates, their email content, their customer list — none of it touches our infrastructure. We see counters (how many POs you processed this month, for billing) and nothing else. For distributors stewarding fifteen-year customer relationships, that distinction is the difference between a yes and a "let me check with our IT person."
The risk we're tracking
If Intuit's connector gains write capability in a future version — create Estimate, post Invoice — they step closer to our turf. We don't think it's imminent. Their roadmap signals are about analytics, not workflow. And even if write lands, the hard parts of SideQuest are not the QB API calls. The hard parts are:
- Reading messy PO formats (handwritten, scanned, EDI body-text, photos)
- Matching customer part numbers to your QB SKUs across five fallback strategies
- Learning cross-references automatically from how the rep edits drafts
- Detecting price variance against contract pricing
- Drafting buyer replies on the right Gmail thread
None of that is on Intuit's path. They're a general-purpose accounting tool. We're a vertical workflow for industrial and wholesale distributors. Both can win.
What this means for evaluators
If you already installed Intuit's QuickBooks connector and you handle a meaningful number of incoming POs by email, install SideQuest alongside it. The install prompt is at sidequestautomation.com/install-prompt. The free tier covers your first 20 POs per month with no credit card.
The two tools will look like one product to your reps. That's the point.