Meridian Connector for QuickBooks

Yes. Anthropic's directory lists delete_entity, delete_transaction and delete_attachment among the 64 tools. Intuit's Accounting API documents Delete as an endpoint that removes the object and says nothing about undoing it; its support material addresses recovery only as re-entering the transaction by hand from the audit log. Prefer voiding.

Voiding is reversible bookkeeping; deleting is not. The connector exposes both, as void_entity and void_invoice alongside delete_entity and delete_transaction. Intuit documents them as separate operations: voiding leaves the transaction active with all amounts zeroed and Voided written into its private note, while deleting removes the object entirely.

More than 64. Nine of its tools take a QuickBooks entity type as an argument rather than naming one, so create_entity, update_entity, delete_entity, void_entity and set_entity_active reach every entity type Intuit's Accounting API supports. The tool count measures the interface, not the reach into your books.

Yes, and it is per company. Pilot's FAQ states you choose read-only or read-write access separately for each company when you connect it, and that reconnecting a company changes its access level later. Pilot's terms add that read-only companies cannot be changed through the Connector, so the guard is server-side.

No. The server's own descriptor advertised exactly qbo.read, qbo.write and offline_access on 2026-08-22. Write is one undivided grant, so any authorisation that lets an agent create an invoice also lets it delete a journal entry. The boundary that matters is the per-company read-only setting, not the scope list.

It records payments but does not send them. Pilot's terms state plainly that the Connector does not initiate payments or move money. Tools like create_bill_payment and create_deposit write the accounting record of a payment into QuickBooks; no funds transfer results from calling them.

No, and Pilot explains why it built a separate one. Pilot's FAQ states the official connector cannot read transaction-level details, only run reports, and cannot create journal entries or arbitrary other objects. Intuit's own MCP server is a different project again — self-hosted, 145 tools, one tool per entity per verb.

Pilot says it does not keep a copy of your books. Its FAQ states the connector processes QuickBooks data only to answer your requests, then sends the result onward and does not retain it. Pilot does retain encrypted QuickBooks credentials, company identifiers, your Intuit account details and limited operational logs.

Not yet. Pilot's FAQ states that only one user can access a given client company today and that shared access to the same client is not supported. Its launch announcement repeats the limit and points firms needing shared access, review and close workflow at the full Meridian product instead.