quickbooks-desktop-mcp
Provides an HTTP/qbXML API and MCP tools for QuickBooks Desktop (Pro, Premier, Enterprise), enabling agents to discover and validate qbXML operations, run queries and transactions such as customer lookups, invoice creation, and payments, and check QuickBooks status and errors.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
LedgerCrossing — MCP server and HTTP API for QuickBooks Desktop
LedgerCrossing gives QuickBooks Desktop (Pro, Premier, Enterprise) an HTTP/qbXML API and an MCP server that your apps and AI agents can reach from anywhere: the internet through LedgerCrossing Remote, your office network, or the same machine.
Claude, ChatGPT, Cursor, VS Code and any other MCP client get seven tools covering all 240 qbXML
operations, with lookups and changes in separate tools. Your own code gets POST /api/v1/qbxml: send qbXML, get qbXML back. No SOAP service
to host, and no Web Connector polling.
This repository holds documentation, examples, the MCP Registry entry (server.json) and, in its
releases, the Claude Desktop extension bundle (.mcpb). The LedgerCrossing app itself is a commercial Windows
app: a one-time purchase, licensed per machine, with unlimited company files. See
ledgercrossing.com for pricing. Its source is not in this repository, and
nothing here works without the app installed on the QuickBooks machine.
Compatibility: LedgerCrossing works with anything that can make a web request. Off-the-shelf apps that sync through the Web Connector today are controlled by their vendors, and LedgerCrossing is not a 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.
Why QuickBooks Desktop needs this
QuickBooks Desktop has no cloud API. It accepts qbXML only through a COM interface on the machine where it runs. Intuit's official AI connectors cover QuickBooks Online, not Desktop. LedgerCrossing runs beside QuickBooks on that machine and turns it into an endpoint your tools can call.
Related MCP server: QuickBooks Online MCP Server
Connect an AI client
Pick the path by where the AI runs relative to the QuickBooks computer.
Client | From | How | Needs |
claude.ai, ChatGPT, Meta Muse, Grok Bot | anywhere | LedgerCrossing Remote ($39/mo) | per-person sign-in (OAuth); Meta Muse needs LedgerCrossing 1.15.1 or later, Grok Bot 1.15.2 or later |
Claude Desktop | the QuickBooks computer | nothing to copy | |
Claude Desktop | another computer in the office |
| Settings > Allowed Connections > Local network turned on |
Claude Code, Cursor, VS Code | any of the above | MCP URL + API key (same machine or office); sign-in over Remote | |
Codex, Gemini CLI | the QuickBooks computer or the office | nothing on the QuickBooks computer (stdio); MCP URL + API key from another computer |
The MCP endpoint is http://<machine>:8284/mcp (streamable HTTP). Settings > Allowed
Connections in the app shows the exact address and the API key.
Claude Desktop
Download
ledgercrossing.mcpbfrom this repository's latest release.In Claude Desktop open Settings > Extensions > Advanced settings > Extension Developer > Install Extension… and pick the file. (Windows has no file association for
.mcpb, so double-clicking it won't work.)On the QuickBooks computer, leave the extension's three settings blank and enable it. On another office computer, copy the MCP Server address and API key from LedgerCrossing's Settings > Allowed Connections > Local network into LedgerCrossing address (optional) and API key (optional). If HTTPS is on, also paste the fingerprint from Settings > Advanced into TLS fingerprint (optional).
If LedgerCrossing.exe is set to Run this program as an administrator, extensions older than 1.15.4 can't connect and Claude shows only "Server disconnected". Install the 1.15.4 or later bundle from the latest release.
Prefer a config file? See examples/mcp-configs/claude_desktop_config.json
(stdio mode, same machine only).
Claude Code, Cursor, VS Code
claude mcp add --transport http quickbooks http://localhost:8284/mcp --header "X-Api-Key: YOUR_KEY"Cursor and VS Code configs are in examples/mcp-configs/. From another
office computer, replace localhost with the machine's name. From anywhere, connect over
LedgerCrossing Remote with per-person sign-in, the same way as claude.ai (see
/docs/connect).
Then ask: "Which customers are 60+ days overdue?"
The seven tools
Tool | What it does |
| Lists or searches the 240 qbXML operations, with category and minimum QuickBooks version |
| Full field reference for one operation (element order, required fields, max lengths, enums), plus a minimal example request |
| Checks a request against the catalog without touching QuickBooks |
| Runs a query or report in QuickBooks Desktop and returns the response. Refuses any request that would change data |
| Adds, modifies, deletes or voids records in QuickBooks Desktop. Refuses requests that change nothing |
| Turns a QuickBooks status code into what went wrong and what to change |
| Is QuickBooks up, which company file is open, is the bridge connected |
The agent discovers what it needs on demand (list_operations → get_operation →
validate_qbxml → read_quickbooks or write_quickbooks), so the catalog never floods its context.
Every tool carries a title and MCP annotations: write_quickbooks is the only one marked
destructive, and the other six are marked read-only. In LedgerCrossing 1.16.0, read_quickbooks
and write_quickbooks replaced run_qbxml; prompts and agent setups that name run_qbxml need the
new names.
Before you connect an agent: it can write. On the QuickBooks computer and the office network,
write_quickbooks can add, change, delete and void records, with the same power as the HTTP API. Over
LedgerCrossing Remote, each person starts read-only until the owner allows changes. Open-ended
list and transaction queries are refused by default,
and QuickBooks' Audit Trail records every posted transaction. Connect agents you trust, to company
files you mean them to touch.
Call it from your own code
curl -s http://localhost:8284/api/v1/qbxml \
-H "X-Api-Key: YOUR_KEY" -H "Content-Type: application/json" \
-d '{"qbxml": "<?xml version=\"1.0\"?><?qbxml version=\"13.0\"?><QBXML><QBXMLMsgsRq onError=\"stopOnError\"><CustomerQueryRq><MaxReturned>10</MaxReturned></CustomerQueryRq></QBXMLMsgsRq></QBXML>"}'More in examples/: Python, Node.js and PowerShell, plus validating a request
before sending it.
Endpoint | Purpose |
| Run a qbXML request |
| Validate qbXML against the catalog, no QuickBooks round-trip |
| Search the operation catalog |
| Field reference for one operation, e.g. |
| Explain a QuickBooks status code |
| Liveness check |
| MCP endpoint (streamable HTTP) |
Reach it from anywhere
Internet: LedgerCrossing Remote ($39/mo), a managed HTTPS relay with per-person sign-in, which claude.ai and ChatGPT require (Meta Muse and Grok Bot are verified over it too). Clients that can send an API key header can also use your own tunnel (guide).
Office network: turn on Settings > Allowed Connections > Local network; the app requires an API key first and manages its own firewall rule.
Same machine:
http://localhost:8284.
Requirements
Windows 10 or 11, or Windows Server 2016–2025, with QuickBooks Desktop Pro, Premier or Enterprise, 2019 and later. 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.
QuickBooks running with the company file open (or auto-openable). That is a QuickBooks Desktop constraint.
By default each request names its company file (QuickBooks File page: The caller names the file in each request). Ask your agent to use a file by name, or choose Always use this company file on the same page.
LedgerCrossing installed and activated on that machine (1.15.1 or later for Meta Muse, 1.15.2 or later for Grok Bot).
Links
Product and pricing: https://ledgercrossing.com
MCP quickstart: https://ledgercrossing.com/docs/mcp
Connect Claude to QuickBooks Desktop, every option compared: https://ledgercrossing.com/connect-claude-to-quickbooks-desktop
claude.ai and ChatGPT setup: https://ledgercrossing.com/docs/connect
Support: support@ledgercrossing.com
License
The documentation, examples and server.json in this repository are MIT licensed (see
LICENSE). The LedgerCrossing app and the .mcpb bundle are commercial software,
licensed per machine under the terms at ledgercrossing.com. The MIT
license does not cover them.
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. Client names belong to their respective owners.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
The best QuickBooks Desktop MCP server on the planet: every operation on every record type
Build QuickBooks Desktop integrations: validated API requests and workflows, answers by webhook.
QuickBooks Online in Claude and ChatGPT: 221 tools, full ledger, multi-company, Canada + US, FR/EN.
Kaiva Bridge turns your API, database or documents into a managed MCP server for Claude, ChatGPT, Cursor and VS Code. Point it at an OpenAPI or Swagger spec, an API docs link, a cURL command, a Postman collection, a GraphQL endpoint, Postgres, MySQL, MariaDB or SQL Server, spreadsheets, PDFs and other documents, or an MCP server you already run. Bridge reads the source and proposes tools, and you choose which ones your AI client sees. No code to write and nothing to run. Connect this server and your agent does the setup for you: it lists your servers, shows one, drafts a new server from an OpenAPI spec, and refreshes a server's tools when its API changes. Free plan: 10 servers and 200,000 tool calls a month, no credit card. Pricing: https://kaiv.ai/bridge/pricing Security: https://kaiv.ai/bridge/security Docs: https://kaiv.ai/bridge/docs
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceA secure, local-first MCP server that enables users to query QuickBooks data such as accounts, bills, and customers using natural language within Claude Desktop. It provides a direct interface to the QuickBooks API for streamlined financial data retrieval and management.10-
- AlicenseNot gradedqualityDmaintenanceProvides 55 tools for managing QuickBooks entities like customers, invoices, and bills via any MCP-compatible client, built on Cloudflare Workers with OAuth 2.0 authentication.11Apache 2.0
- AlicenseNot gradedqualityDmaintenanceA local MCP server that exposes QuickBooks Online data and actions as callable tools for AI assistants.MIT
- AlicenseNot gradedqualityDmaintenanceA self-hosted MCP server that provides AI assistants with secure access to multiple QuickBooks Online company files through a single connection, featuring a company registry, OAuth-based authorization, and comprehensive read/write tools.1MIT