LedgerCrossingLedgerCrossing Buy LedgerCrossing — $299

How to Connect Claude to QuickBooks Desktop (2026)

Short answer: Yes, but not with Intuit's Claude connector, which only supports QuickBooks Online. You need software that reaches the QuickBooks machine and exposes it to Claude, usually an MCP server. Every option is compared below.

QuickBooks Desktop has no cloud API. It accepts qbXML only through an interface on the Windows machine where it runs, so every option puts something on that machine: an MCP server, an ODBC driver, or the Web Connector feeding a hosted API. This guide compares them with prices, then walks through the five-minute setup for the one we build.

Updated November 3, 2026. QuickBooks is a trademark of Intuit Inc.; LedgerCrossing is not affiliated with or endorsed by Intuit.

Why the official Intuit connector doesn't work for Desktop

Intuit's QuickBooks connector for Claude (listed on claude.com/connectors) signs in with an Intuit account and talks to QuickBooks Online's cloud API. QuickBooks Desktop Pro, Premier, and Enterprise keep the company file on a local disk or file server and expose it only through the QuickBooks SDK's COM interface, using qbXML, on the Windows machine where QuickBooks is installed. There is no Intuit-hosted endpoint for a Desktop file, so no cloud connector, official or third-party, can reach it without something running locally. Every option below is a way of putting that "something" on the machine.

Your options, compared

Option How it reaches QuickBooks Desktop Works with Price (checked Oct 2026) Best for
LedgerCrossing (us) Windows app on the QuickBooks machine with a built-in MCP server and HTTP API; no Web Connector Claude Desktop, Claude Code, Cursor, VS Code; claude.ai and ChatGPT via Remote $299 one-time per machine (limited-time price, rises to $349); Remote $39/mo optional Anyone who wants Claude working against Desktop in minutes with no code
CData Code Assist MCP for QuickBooks Desktop An MCP server that reaches QuickBooks Desktop through CData's QuickBooks Desktop Gateway on the QuickBooks machine Claude Desktop, Claude Code, Cursor, Gemini Code Assist, GitHub Copilot Not listed; ask CData Teams already using CData connectors
Conductor (its own MCP server, or Activepieces) Conductor's hosted API, which reaches Desktop through the Web Connector; its MCP server (or Activepieces) calls that API Any MCP client (Conductor names Claude, ChatGPT and Cursor) $49/mo per company file, free test connection (conductor.is) Developers already building on Conductor
Apideck (QuickBooks Desktop connector, in beta) A unified accounting API; the Desktop side syncs through the Web Connector on a polling schedule; its MCP server covers 11 accounting resources Any MCP client Apideck subscription (see apideck.com) SaaS teams connecting many accounting systems through one API
ChatFin Its own AI-agent product; connects to Desktop through Intuit's SDK and the Web Connector ChatFin's agents (not a Claude connector) No public price; demo on request Finance teams that want a managed AI product
Boost Connect for QuickBooks Desktop Hosted connector; apps and agents call its API, QuickBooks side set up through a Web Connector (QWC) path Apps and agents that call its API Free tier; $29/mo single connection; $49/mo enterprise plus $19/mo per extra connection, per its site Developers who want a hosted API and accept a subscription and Web Connector dependency
CData ODBC/Python connector + your own MCP server ODBC driver on the QB machine; you write and run a Python MCP server over it Claude Desktop (stdio) From $599 (CData lists $599–$2,999); 30-day trial; plus your build time Developers comfortable maintaining a custom server
Make / Zapier style automation Webhook scenarios feeding exported Desktop data into a workflow Claude via HTTP modules Platform subscription plus a Desktop export mechanism you still have to build Occasional one-directional data pushes, not interactive Q&A
DIY: QuickBooks SDK + your own bridge Write a COM/qbXML service and an MCP wrapper Anything you build for Your time Teams that already maintain a QuickBooks integration

Two things to notice. First, many tools that come up for "QuickBooks" and "Claude" (Intuit's connector, Windsor.ai and many directory MCP servers) use QuickBooks Online's cloud API, which a Desktop company file doesn't have. Check that a tool names QuickBooks Desktop before you try it. Second, the Desktop options differ in three ways that matter: whether they depend on the Web Connector and its polling schedule, whether you pay once or every month, and which AI clients they work with. Conductor's MCP server and Apideck's connector both run through the QuickBooks Web Connector, which checks in on a schedule (polling). LedgerCrossing sends requests straight to QuickBooks instead: no Web Connector, no polling schedule, a one-time purchase per machine, and on your office network nothing leaves it. It works with any MCP client (claude.ai and ChatGPT over LedgerCrossing Remote).

Compatibility note. LedgerCrossing works with anything that can make a web request. Off-the-shelf apps that sync through the Web Connector today (ServiceTitan, JobNimbus, Connex, and similar) are controlled by their vendors, and LedgerCrossing is not a drop-in replacement underneath them. If you or your developer control the integration, switching is straightforward: send the same qbXML you send today as an HTTP POST.

Connect Claude to QuickBooks Desktop with LedgerCrossing

The full quickstart with every client's config is at /docs/mcp. The short version:

Before you start

Claude Desktop on the QuickBooks computer (about 5 minutes)

  1. Download ledgercrossing.mcpb. If your browser warns about the download, choose Keep.
  2. In Claude Desktop, open Settings > Extensions > Advanced settings.
  3. Under Extension Developer, click Install Extension… and choose the .mcpb file. Do not double-click the file; Windows has no file association for it.
  4. Leave the three settings at their defaults and enable the extension. On the same machine the bundle reads the API key from LedgerCrossing's own config, so there is nothing to copy.
  5. Ask Claude: "Which customers are 60+ days overdue?"

Claude Desktop on another computer in your office

Same bundle. On the QuickBooks machine, turn on Allow under LedgerCrossing Settings > Allowed Connections > Local network, then copy the MCP Server address and API key from that tab. On your workstation, install the LedgerCrossing .mcpb extension the same way, then enter that address and key in the extension's settings. The call goes across your LAN; nothing leaves the office and there is no subscription.

Claude Code, Cursor, VS Code

One command for Claude Code (replace YOUR_KEY with the API key from Settings > Allowed Connections):

claude mcp add --transport http quickbooks http://localhost:8284/mcp --header "X-Api-Key: YOUR_KEY"

Cursor and VS Code use the same URL and header in their mcp.json; configs are in the quickstart.

claude.ai or ChatGPT (outside the office)

The web apps can't send an API key, so a QuickBooks connection needs an HTTPS endpoint with sign-in. The only other choice, no authentication at all, isn't acceptable for your books. LedgerCrossing Remote ($39/mo) provides that, with per-person usernames and passwords the owner can make read-only or scope to specific company files. Setup: /docs/connect. Everything on the same machine or network above is free; Remote charges for hosted reachability, not for MCP.

What Claude can do once connected

LedgerCrossing's MCP server exposes six tools: list the 240 qbXML operations, get one operation's full field rules, validate a request locally, run it against QuickBooks, explain a QuickBooks status code, and check status. In practice that means Claude can answer questions like overdue receivables, items below reorder point, or this month's sales by rep, and can create or edit records: invoices, payments, customers, bills. The catalog is built from Intuit's own qbXML reference (field names, types, order, lengths and version gates), so Claude looks up operations on demand instead of being handed a giant prompt. To have Claude enter a bank or card statement, see How to import bank and credit card transactions into QuickBooks Desktop.

What a LedgerCrossing customer uses it for, in their words:

"I use it … when I need it to build out any reports. I just tell Claude to check in with QuickBooks and give me an Excel sheet of it or, when entering any invoices, I upload it to Claude and tell it to enter it into QuickBooks. When I wanted to reconcile a card, I just upload the statement to Claude, tell it to enter it into QuickBooks, and follow the previous rules of previous entries that I did manually so it knows what to do and you don't have to walk through all steps."

Zishe, LedgerCrossing customer

Before you let an agent write to your books

Frequently asked questions

Can Claude connect to QuickBooks Desktop? Yes, through a bridge app on the QuickBooks machine. Intuit's official Claude connector supports QuickBooks Online only. LedgerCrossing runs on the QuickBooks Desktop machine and includes an MCP server that Claude Desktop, Claude Code, Cursor, and VS Code connect to.

Does the Intuit QuickBooks connector for Claude work with QuickBooks Desktop? No. As of October 2026 it connects QuickBooks Online accounts. Desktop company files are local and need software running on that machine.

Do Windsor.ai or other Claude connectors work with QuickBooks Desktop? Most connect through QuickBooks Online's cloud API, which a Desktop company file doesn't have. Windsor.ai's guide, for example, signs in with a QuickBooks Online account. Check that a connector names QuickBooks Desktop (Pro, Premier or Enterprise) before you try it.

Can I use ChatGPT with QuickBooks Desktop? Yes, over LedgerCrossing Remote ($39/mo), which gives ChatGPT a secure address with per-person sign-in. ChatGPT can't reach a computer in your office directly. Step by step: How to connect ChatGPT to QuickBooks Desktop.

Is the QuickBooks Desktop MCP server free? It is included in LedgerCrossing, a $299 one-time purchase per machine (limited-time price; rises to $349). There is no separate MCP tier, preview, or subscription.

Can I use claude.ai, the web app, with QuickBooks Desktop? Yes, over LedgerCrossing Remote ($39/mo), which gives claude.ai and ChatGPT an HTTPS endpoint with per-person sign-in. On the same machine or office network, Claude Desktop connects free.

Is it read-only? Not on the QuickBooks computer or the office network: there the agent can create invoices, payments, and edits with the same capability as the REST API. Over LedgerCrossing Remote, each person starts read-only until the owner allows writes. Open-ended list and transaction queries are refused by default, and QuickBooks' Audit Trail records every posted transaction.

Is it safe to connect Claude to QuickBooks Desktop? LedgerCrossing runs on your QuickBooks computer, is code-signed by EFFIQUEST, LLC, and sends no QuickBooks data to us; the data Claude asks for goes to Anthropic under your Claude account. Access from outside the office is off until you set it up, LedgerCrossing Remote starts every person read-only, and every qbXML request is written to an audit log on the machine. The details for IT: Security and IT review.

Which QuickBooks Desktop versions work? Pro, Premier, and Enterprise, 2019 and later, on Windows 10 or 11, and Windows Server 2016–2025. Older versions back to 2014 use the same Intuit connection and should work, though we haven't tested them; the 30-day guarantee covers you.

Does this replace the Web Connector for my other apps? Not for vendor-controlled apps. LedgerCrossing works with anything that can make a web request, so integrations you or your developer control can switch by sending qbXML as an HTTP POST. See Web Connector alternatives.

Buy LedgerCrossing — $299 → One-time, per machine, unlimited company files, 30-day money-back guarantee.


QuickBooks is a registered trademark of Intuit Inc. LedgerCrossing is an independent product for QuickBooks Desktop and is not affiliated with or endorsed by Intuit. MCP (Model Context Protocol) is an open protocol; client and product names belong to their respective owners. Competitor prices are from vendor websites on the date shown and may change.