How to Connect Claude to QuickBooks Desktop (2026)

You can connect Claude to QuickBooks Desktop, but not through Intuit's official Claude connector, which supports QuickBooks Online only. QuickBooks Desktop has no cloud API; it only accepts qbXML through a local interface on the machine where it runs. To use Claude with a Desktop company file you need software on that machine that exposes QuickBooks to Claude, either an MCP server, an ODBC driver with a custom script, or an automation platform bridge. This guide compares every working option, with prices, and then walks through the five-minute setup for the one we build.

Updated September 19, 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

Two things to notice. First, the community "QuickBooks MCP servers" you find on GitHub and MCP directories (glama.ai, mcpservers.org, Composio, Windsor, Coupler, Pipedream) are all QuickBooks Online servers; they use the QBO cloud API and cannot open a Desktop file. Second, of the Desktop options, only one is a one-time purchase and only one gives you both an MCP server and a REST API without writing code.

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

• LedgerCrossing installed and activated on the QuickBooks machine (buy it here, $299 one-time).
• QuickBooks Desktop running with the company file open (or auto-openable).

Claude Desktop on the QuickBooks computer (about 5 minutes)

1. Download ledgercrossing.mcpb. The bundle is unsigned, so expect a Windows SmartScreen prompt.
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, tick Allow connections from other machines on the network in LedgerCrossing Settings > General, then copy the MCP URL and API key from Settings > Connect. On your workstation, paste them into 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 (get the key from Settings > Connect):

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 accept only OAuth connectors, so they need an HTTPS endpoint with sign-in. LedgerCrossing Remote ($39/mo) provides that, with per-person connect codes 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 generated from Intuit's qbXML specification, so Claude discovers operations on demand instead of being handed a giant prompt.

Before you let an agent write to your books

• It is not read-only. The agent has the same capability as the REST API, including creating and editing transactions. Connect agents you trust to company files you mean to let them touch. QuickBooks' Audit Trail records every posted transaction.
• Runaway queries are refused by default. Unbounded query requests are rejected unless you opt out, so an agent cannot accidentally pull the whole company file in one call.
• QuickBooks must be running with the company file open. That is a QuickBooks Desktop constraint and the reason cloud-only servers can't do this job.

Frequently asked questions

Can Claude connect to QuickBooks Desktop? Yes, through a local bridge. 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 September 2026 it connects QuickBooks Online (and Intuit Enterprise Suite) accounts. Desktop company files are local and need software running on that machine.

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? No. The agent can create invoices, payments, and edits with the same capability as the REST API. Unbounded queries are refused by default, and QuickBooks' Audit Trail records every posted transaction.

Which QuickBooks Desktop versions work? Pro, Premier, and Enterprise on Windows 10 or 11.

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.