The ultimate guide to QuickBooks MCP 2026.
Every credible way to connect an AI assistant to QuickBooks Online with the Model Context Protocol — official, community, cloud platform, and hosted — with the GitHub repos, real pricing, write-access, permissions, and setup effort laid out plainly. Start here for the full market map, then jump to the deeper comparison or setup guide that fits your situation.
Want the shorter head-to-head first? See QuickBooks MCP servers compared for the six main routes buyers usually shortlist.
The basics
What is a QuickBooks MCP server?
The Model Context Protocol (MCP) is an open standard, introduced by Anthropic in November 2024, that lets AI assistants connect to outside systems through one common interface. A QuickBooks MCP server is the piece in the middle: it exposes your QuickBooks data (and, on some servers, actions like creating an invoice) as "tools" an assistant such as Claude, ChatGPT, or Gemini can call.
In plain terms: instead of exporting a report and pasting it into a chat, the AI reads your live QuickBooks records and answers from them. The options differ on three things that matter more than any feature list — whether the AI can change your books, who is allowed to use it, and who runs and pays for the server.
The landscape
Four categories of option.
Open-source & free
Server code you run yourself, locally or on your own cloud. Free software; you own setup, credentials, and uptime.
Managed cloud platforms
Multi-app platforms (Zapier, Composio, Pipedream, CData) that host the connection and manage auth. Paid by tasks, tool calls, or subscription.
Hosted finance layer
A vendor-run, read-only layer built for finance teams — no code, per-user permissions, audit trail. Paid subscription.
QuickBooks Desktop
A different technical stack (Desktop SDK / qbXML). Not covered by QBO MCP servers — see the FAQ.
Category 01 · Free
Open-source & free servers
Best for developers. The code is free; the real cost is your time, credentials, and — if you host remotely — infrastructure. With any server that holds accounting credentials, read the code first.
Official · from Intuit Start here if you're a developer Intuit official server
intuit/quickbooks-online-mcp-server ↗The reference implementation from the platform owner, and the broadest documented surface: 144 tools across 29 entity types plus 11 financial reports. Runs locally as a stdio process; authenticates with an app you create on the Intuit Developer Portal (OAuth 2.0).
- Transport
- Local stdio
- Write access
- Read-write by default; env flags to disable
- License
- Apache-2.0 — free & open source
- Setup effort
- High — dev app, OAuth, local process
Wyre qbo-mcp
CommunityA community TypeScript server listing 130+ tools across 22 entities plus 10 reports, notable for gateway-style deployment (header injection) alongside local stdio. Read-write for many entities.
- Transport
- Local stdio + gateway
- Write access
- Read-write (verify surface)
- License
- Open source (free)
- Setup effort
- High — read the code first
LibreChat QBO MCP
CommunityA QBO server rebuilt for Cloudflare Workers with OAuth 2.0, typed Zod schemas, and Streamable HTTP/SSE transport (55 tools). Notable because it's remote — an HTTP server rather than a local subprocess — which suits LibreChat-style stacks.
- Transport
- Cloudflare Workers · HTTP/SSE
- Write access
- Verify before use
- License
- Open source (free + infra)
- Setup effort
- Medium-high — deploy a Worker
CData QuickBooks MCP (OSS)
Vendor OSSA read-only Java server that exposes QuickBooks data as SQL-queryable tables through three tools (list tables, list columns, run SELECT). Genuinely read-only by design — but it requires licensing CData's JDBC driver underneath.
- Transport
- Local Java · JDBC
- Write access
- Read-only (by design)
- License
- Free server + paid JDBC driver
- Setup effort
- Medium-high — driver + config
Other community servers exist (for example laf-rge/quickbooks-mcp and nikhilgy/quickbooks-mcp-server). Treat any unfamiliar repo as unverified until you've checked its license, tools, and write behavior.
Category 02 · Paid, usage-based
Managed cloud platforms
Best when QuickBooks is one of many apps you're wiring to AI and you want managed auth. These are mostly action-first and priced by usage — budget for it if a team will ask questions all day.
Zapier MCP
zapier.com/mcp ↗Action-first: create a bill, add a customer, record a deposit — and the same endpoint reaches 30,000+ actions across 9,000+ apps, so one connection can drive QuickBooks alongside your CRM and project tools. The tool list is dominated by create/update operations.
- Model
- Workflow / action MCP
- Write access
- Read-write (action-oriented)
- Pricing
- Included in Zapier plans; 1 MCP call = 2 tasks
- Best for
- AI taking actions across apps
Composio
composio.dev ↗Managed auth and hosted MCP servers across 1,000+ toolkits, aimed at teams building AI agents. Handles OAuth and tool routing so your agent gets QuickBooks tools without you running a server.
- Model
- MCP gateway / managed auth
- Write access
- Read-write (tool-based)
- Pricing
- Free 20K tool calls/mo; $29 (200K); $229 (2M)
- Best for
- Agent builders
Pipedream Connect
pipedream.com/apps/quickbooks ↗Workflow MCP at scale — 10,000+ pre-built tools across 3,000+ apps, embeddable in your own app with managed end-user auth. (Workday announced its agreement to acquire Pipedream on November 19, 2025; by February 24, 2026, Workday reported the acquisition had closed.)
- Model
- Workflow MCP, embeddable
- Write access
- Read-write (tool-based)
- Pricing
- Free 100 credits/mo; Connect $99/mo + $2/user
- Best for
- Embedding tools in your product
CData Connect AI
cdata.com/ai ↗CData's commercial cloud platform — a remote MCP endpoint for natural-language queries and governed write actions (insert, update, delete) across QuickBooks and hundreds of other sources, aimed at IT and data teams standardizing AI access.
- Model
- Cloud query + action platform
- Write access
- Read-write, IT-scoped per source
- Pricing
- ≈$79/mo Standard, $159/mo Growth (annual); Business custom
- Best for
- IT/data teams, many sources
Category 03 · Paid, hosted
Hosted finance layer
Best when the users want answers, not tools — and read-only, permissions, and an audit trail are requirements rather than nice-to-haves.
Kipper
Hosted · read-onlyKipper is a hosted, read-only layer built for the whole company, not just developers. Writing to QuickBooks is architecturally impossible, permissions are set per user or team in an admin portal, and every question is logged. It answers natively in Slack, Teams, and SMS today; the Kipper MCP beta extends the same governed access to Claude, ChatGPT, and Gemini. It runs against a synced copy of your data rather than live API calls, so cross-entity comparisons come back as single queries.
- Write access
- Impossible by architecture
- Permissions
- Per user / team, per query
- Pricing
- $200/mo — 10 users, 2,000 Qs
- Setup effort
- Low — web portal, no code
The full landscape
Nine options, one table.
| Option | Type | Hosting | Write access | Per-user permissions | Audit trail | Cost | Setup effort |
|---|---|---|---|---|---|---|---|
| Intuit (official) | Open source | Local (stdio) | Read-write | No | No | Free (Apache-2.0) | High |
| Wyre qbo-mcp | Open source | Local + gateway | Read-write | No | No | Free | High |
| LibreChat QBO | Open source | Cloudflare Workers | Verify | No | No | Free + infra | Med-High |
| CData (OSS) | Vendor OSS | Local Java (JDBC) | Read-only | Driver auth | No | Free + driver licence | Med-High |
| Zapier MCP | Cloud platform | Zapier cloud | Read-write | Scoped per endpoint | Task history | Plan + 2 tasks/call | Low-Med |
| Composio | Cloud platform | Composio cloud | Read-write | Managed auth | Platform logs | Free → $29 → $229 | Low-Med |
| Pipedream | Cloud platform | Pipedream cloud | Read-write | Managed auth | Platform logs | Free → $99/mo | Low-Med |
| CData Connect AI | Cloud platform | CData cloud | Read-write | IT-scoped per source | Platform logs | ≈$79–$159/mo | Low-Med |
| Kipper | Hosted finance layer | Kipper cloud | Impossible | Yes, per query | Every Q&A logged | $200/mo (10 users) | Low (no code) |
Figures from each vendor's own README / pricing page, July 2026. This category changes monthly — re-verify before relying on it.
What it actually costs
What each option actually costs.
"Free" software is rarely free to run — factor in the QuickBooks subscription, an Intuit developer app, hosting, and your own time.
| Option | Software | Hosting / infra | Ongoing cost | Notes |
|---|---|---|---|---|
| Intuit / Wyre / LibreChat | Free (open source) | Your machine, or cloud hosting you run | $0 software + your time & infra | You own setup, OAuth, and uptime |
| CData (OSS server) | Free server | CData JDBC driver licence (trial available) | Driver licence | Read-only, SQL-style access |
| Zapier MCP | Included in Zapier plans | None (Zapier cloud) | Task-based; 1 MCP call = 2 tasks | Shared task pool across all Zaps |
| Composio | Free tier (20K calls/mo) | None (Composio cloud) | $29/mo (200K) → $229/mo (2M) | Usage-based on tool calls |
| Pipedream Connect | Free tier (100 credits/mo) | None (Pipedream cloud) | $99/mo (10K credits) + $2/user | Embeddable; Workday-owned |
| CData Connect AI | Subscription | None (CData cloud) | ≈$79–$159/mo (annual); Business custom | Many data sources, one endpoint |
| Kipper | Subscription | None (hosted) | $200/mo — 10 users, 2,000 questions | 14-day free trial, no credit card |
Decide faster
Two questions that sort the whole market.
Read or write?
Intuit's server (by default), Wyre, Zapier, Composio, Pipedream, and CData Connect AI let AI write to your books; CData's open-source server and Kipper cannot. An AI that reads badly gives someone a wrong number; an AI that writes badly is a bookkeeping incident. If you want write workflows, restrict who holds the connection and test in a sandbox company first.
One user or the whole team?
A local MCP server is one user, one machine, one OAuth connection. Cloud platforms and hosted layers serve more people — but with raw servers, per-user permissions, token storage, and audit logging become yours to build. That gap, between "raw tools for me" and "governed answers for everyone," is the real boundary, and it's the one tool counts don't capture.
Under the hood
The limitation nobody mentions: the QuickBooks API itself.
One caution applies to every tool-per-entity server above, including Intuit's own. QuickBooks Online's query language is deliberately narrow: no joins, no GROUP BY, one entity per query, and a 1,000-row cap per page. Standard report endpoints cover standard questions — the official server does expose aged receivables and payables, so "MCP can't do AR aging" is false.
But custom cross-entity questions ("compare this quarter's expense categories to last, by vendor") force the AI to stitch together multiple API calls and do the math itself — which is where wrong answers creep in. That's the design reason a synced relational copy (Kipper's approach) matters: comparisons and breakdowns become single queries against complete records. It's a fair test to run on any option — ask a cross-entity question and check the answer against QuickBooks.
Security & governance
Six questions to ask before you connect.
Tool count is not the buying criterion. For accounting data, these decide it.
- Can it write to production QuickBooks data — and can that be turned off?
- Where are OAuth tokens stored, and who can reach them?
- Is access scoped per user, or is it one shared connection?
- Is every question and answer logged for an audit trail?
- Can non-finance staff use it without getting a QuickBooks login?
- Does it answer custom cross-entity questions, or only call raw API tools?
The bottom line
Which should you choose?
Developers
Start with Intuit's official server for free, full-surface, official API access inside an MCP client. Reach for Wyre or LibreChat if their deployment shape (gateway or Cloudflare Workers) fits better. Set the disable flags if you want read-only.
Setup guide: QuickBooks MCP locallyAgent & automation builders
Use a managed platform — Zapier, Composio, or Pipedream — when QuickBooks is one of many apps your agent touches and you want managed auth. Budget carefully: these are action-first and priced by tasks or tool calls.
Zapier vs. Composio vs. Pipedream comparedIT & data teams
CData Connect AI (or the OSS JDBC server) fits when you think in SQL and are standardizing AI access to QuickBooks alongside many other data sources.
CData's two QuickBooks options comparedFinance, ops & the whole company
If the users want answers rather than tools — and read-only, per-user permissions, and an audit trail are requirements — a hosted finance layer like Kipper connects once, stays read-only by architecture, and answers in Slack, Teams, SMS, and (via the MCP beta) Claude, ChatGPT, and Gemini.
See Kipper's QuickBooks MCP serverFAQ
QuickBooks MCP: frequently asked questions
The questions developers, finance teams, and business owners ask most.
Keep reading
QuickBooks MCP servers compared
The six-option comparison, in depth.
ReadSet up QuickBooks MCP with Claude
Step-by-step, official and hosted routes.
Read30 questions to ask AI about QuickBooks
What good looks like once you're connected.
ReadSet up QuickBooks MCP locally
The developer setup, end to end.
ReadKipper's QuickBooks MCP server
The hosted, read-only route for teams.
ReadZapier vs. Composio vs. Pipedream
Managed platforms for AI agents, compared.
ReadCData's two QuickBooks offerings
SQL access via MCP, OSS vs. Connect AI.
ReadWant answers, not tools to maintain?
Kipper is the hosted, read-only route: connect QuickBooks once and let your whole team ask — in Slack, Teams, SMS, and soon Claude, ChatGPT, and Gemini.
Sources & further reading