LedgerCrossing for QuickBooks Desktop

com.ledgercrossing由 ledgercrossing.com 发布v1.15.1更新于 Oct 30, 2026

QuickBooks Desktop MCP server: all 240 qbXML operations for Claude, ChatGPT, Cursor and VS Code

已验证Streamable HTTP可网页运行金融开发者工具商业与电商

概览

AI 生成的概览

让 AI 助手通过发现、校验并执行 qbXML 操作来查询和修改 QuickBooks Desktop 公司账套的 MCP 服务器。

可以做什么
  • 发现与查阅 qbXML 操作:列出或搜索 240 个操作,并查看单个操作的完整字段说明
  • 在不接触 QuickBooks 的情况下校验 qbXML 请求
  • 在 QuickBooks Desktop 中执行 qbXML 并返回响应
  • 解释 QuickBooks 状态码,并检查 QuickBooks 是否运行、打开了哪个公司账套、桥接是否连通
适用场景
当助手需要读取或修改 QuickBooks Desktop(Pro、Premier 或 Enterprise)公司账套中的数据,例如查找逾期客户或创建发票,且没有可用的云端 API 时适用。适合自行掌控集成、能够发送 qbXML 的团队。
运行要求
Windows 10/11 或 Windows Server 2016–2025,安装 QuickBooks Desktop 并打开公司账套。需在该机器上安装并激活商业版 LedgerCrossing 应用(一次性购买,按机器授权)。本机或办公网络访问需要应用提供的地址和 API 密钥(X-Api-Key 请求头);通过 claude.ai 或 ChatGPT 从互联网访问需要付费的 LedgerCrossing Remote 中继及每人登录。
安装前请注意
助手可以写入:run_qbxml 能创建发票、付款和修改,权限与 HTTP API 相同,因此只应连接可信的助手到你希望其操作的公司账套。远程访问为付费订阅,每个人初始为只读,需由所有者开启修改权限。API 密钥可访问 QuickBooks 所在机器,应妥善保管。该应用为闭源商业软件,不在仓库中。

安装

在 SourceWeft 中

  1. 打开 控制台中的 LedgerCrossing for QuickBooks Desktop,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

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 same machine, your office network, or the internet through LedgerCrossing Remote.

Claude, ChatGPT, Cursor, VS Code and any other MCP client get six tools covering all 240 qbXML operations. 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.

Connect an AI client

Pick the path by where the AI runs relative to the QuickBooks computer.

ClientFromHowNeeds
Claude Desktopthe QuickBooks computer.mcpb bundlenothing to copy
Claude Desktopanother computer in the office.mcpb bundle + address and API keySettings > Allowed Connections > Local network turned on
claude.ai, ChatGPT, Meta MuseanywhereLedgerCrossing Remote ($39/mo)per-person sign-in (OAuth); Meta Muse needs LedgerCrossing 1.15.1 or later
Claude Code, Cursor, VS Codeany of the aboveHTTP configMCP URL + API key (same machine or office); sign-in over Remote
Codex, Gemini CLIthe QuickBooks computer or the officequickstartnothing 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

  1. Download ledgercrossing.mcpb from this repository's latest release.
  2. 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.)
  3. Leave the settings at their defaults on the QuickBooks computer. On another office computer, set LedgerCrossing address (for example http://qb-server:8284) and paste the API key.

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 six tools

ToolWhat it does
list_operationsLists or searches the 240 qbXML operations, with category and minimum QuickBooks version
get_operationFull field reference for one operation: element order, required fields, max lengths, enums
validate_qbxmlChecks a request against the catalog without touching QuickBooks
run_qbxmlRuns the qbXML in QuickBooks Desktop and returns the response
explain_errorTurns a QuickBooks status code into what went wrong and what to change
get_statusIs 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 → run_qbxml), so the catalog never floods its context.

Before you connect an agent: it can write. On the QuickBooks computer and the office network, run_qbxml can create invoices, payments and edits, with the same power as the HTTP API. Over LedgerCrossing Remote, each person starts read-only until the owner allows changes. Unbounded 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

bash
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.

EndpointPurpose
POST /api/v1/qbxmlRun a qbXML request
POST /api/v1/validateValidate qbXML against the catalog, no QuickBooks round-trip
GET /api/v1/docs?search=Search the operation catalog
GET /api/v1/docs/{operation}Field reference for one operation, e.g. CustomerQuery
GET /api/v1/errors/{code}Explain a QuickBooks status code
GET /api/v1/healthLiveness check
POST /mcpMCP endpoint (streamable HTTP)

Reach it from anywhere

  • Same machine: http://localhost:8284.
  • Office network: turn on Settings > Allowed Connections > Local network; the app requires an API key first and manages its own firewall rule. Free.
  • Internet: LedgerCrossing Remote ($39/mo), a managed HTTPS relay with per-person sign-in, which claude.ai and ChatGPT require (Meta Muse is verified over it too). Or run your own tunnel with the free guide for clients that can send an API key header.

Requirements

  • Windows 10 or 11, or Windows Server 2016–2025, with QuickBooks Desktop Pro, Premier or Enterprise.
  • QuickBooks running with the company file open (or auto-openable). That is a QuickBooks Desktop constraint.
  • LedgerCrossing installed and activated on that machine (1.15.1 or later for Meta Muse).

Links

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.

来源:README.md,提交 76bc53f

工具

0
SourceWeft 尚未读取此服务器的工具。

版本历史

1
  1. v1.15.1最新Oct 30, 2026

评分

已满足适用检查项的 50%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分

    请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。

  • 已声明认证方式必需10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分