quickbooks-desktop-mcp
Related Servers
Alternatives to quickbooks-desktop-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceLocal Windows MCP server for QuickBooks Desktop (Pro, Premier, Enterprise; not QuickBooks Online). Read customers, vendors, items, invoices, bills and reports through the installed QuickBooks SDK. Read-only by default; changes are opt-in with previews, confirmation tokens, masking of sensitive numbers and an audit log.2MIT
- AlicenseNot gradedqualityCmaintenanceProvides complete coverage of the QuickBooks Online Accounting API v3, enabling queries, financial reports, sales and expense management, and write operations with deployment-controlled access.MIT
- AlicenseNot gradedqualityBmaintenanceEnables an MCP client such as Claude Code to run financial reports, query records, and create, update, void, delete, deactivate, email, or attach records in a company's QuickBooks Online books through the Accounting API. It runs locally over stdio with read and write tools separated, dry-run previews, an optional read-only mode, and a local audit log so the owner stays in control of every change.Apache 2.0
- AlicenseNot gradedqualityDmaintenanceA comprehensive MCP server for QuickBooks Online, providing 144 tools for full CRUD operations on 29 entity types and 11 financial reports, with built-in safety guards against unintended writes.5Apache 2.0
- AlicenseBqualityCmaintenanceEnables MCP clients such as Claude Desktop to read and, after per-transaction confirmation, write accounting data—invoices, customers, items, payments, deposits, checks/bank charges, and journal entries—with two-step confirmation and revert of its own runs.25MIT
- AlicenseNot gradedqualityBmaintenanceExposes six tools that let MCP clients such as Claude, ChatGPT, Cursor and VS Code discover, validate and execute any of 240 qbXML operations against a QuickBooks Desktop company file, explain QuickBooks error codes, and check bridge status, plus a matching HTTP endpoint for sending qbXML from your own code. It runs beside QuickBooks on the Windows machine and can be reached locally, over the office network, or via a managed relay.MIT
TDQS
Scored across 12 tools
Each tool has a clearly distinct purpose, from adding transactions and vendors to checking duplicates, querying, and reverting operations. No two tools overlap in function; even 'vendor_history' and 'list_vendors' serve different needs (history lookups vs. listing names).
Most tools follow a 'qb_verb_noun' pattern (e.g., add_transaction, list_accounts, revert_run), but 'company_info' and 'vendor_history' use a 'noun_info/history' pattern, breaking strict consistency. However, the prefix 'qb_' unifies them, and the naming is still predictable.
With 12 tools, the set is well-scoped for a QuickBooks Desktop integration. It covers essential operations (CRUD for transactions and vendors, plus supporting tools for company info, duplicates, and undo) without being overwhelming or sparse.
The tool surface covers core workflows: adding/deleting/modifying transactions, managing vendors, querying, and undoing operations. Missing are vendor updates or transaction header modifications, but the provided tools handle most common needs, and the undo system adds robustness.