QuickBooks Online MCP

Diff the current AR and AP aging picture against the snapshot recorded by the previous aging-delta run: who slipped an aging bucket, whose balance grew or shrank, who appeared or cleared. QuickBooks reports are point-in-time with no memory; the snapshot history lives in the local store. Each run records a new snapshot unless --no-save is set. Use this command to see what changed in aging since the previous snapshot (who slipped a bucket). Do NOT use it for the current point-in-time aging picture; use 'ar-aging' or 'ap-aging' instead. Run `sync` first.

The payables mirror of ar-aging: bucket open bill balances by age (0-30 / 31-60 / 61-90 / 90+) and roll them up by vendor, computed from the local store. Run `sync` first to populate the store.

Bucket open invoice balances by age (0-30 / 31-60 / 61-90 / 90+) and roll them up by customer, computed from the local store. No single QuickBooks API call returns aging — this joins open invoices to customers and does the date math offline. Run `sync` first to populate the store.

One view of bank/AR/AP account balances (rolled up by account type) plus total customer receivables and total vendor payables. Spans three entity types, so it is only possible once they coexist in the local store. Run `sync` first.

Project net cash movement over the next --weeks weeks by bucketing open invoice balances (inflows) and open bill balances (outflows) by DueDate — scheduled, not predicted. Overdue amounts and amounts beyond the window are reported separately. Use this command to project net cash movement forward by week from due dates. Do NOT use it for the current static cash position; use 'balances' instead. Run `sync` first.

Get API domain context: resource taxonomy, auth requirements, query tips, and unique capabilities. Call this first.

Join invoices, payments, and customers across the whole synced book into one per-customer view: lifetime invoiced, payments received, net outstanding, open balance, and realized average days-to-pay from payment-to-invoice links. Use this command for per-customer net position (invoiced minus paid) and days-to-pay. Do NOT use it for a single-metric balance ranking; use 'customers top' instead. Run `sync` first.

Compute DSO — (open AR balance / credit sales over the trailing --days window) x window days — the headline collections-efficiency KPI, plus realized average days-to-pay per customer from payment-to-invoice links, slowest payers first. Computed offline from the local store. Run `sync` first.

Fuzzy-match customers or vendors by normalized display name and email to catch duplicate records ("Acme Inc" vs "Acme, Inc.") before they fragment AR/AP. Cross-record comparison over the full synced set. Run `sync` first.

Find duplicate customers by normalized name or shared email

Find duplicate vendors by normalized name or shared email

Export paginated API data to a local file. Supports JSONL (one JSON object per line, streaming-friendly) and JSON (array). JSONL is recommended for large datasets as it has no memory pressure.

Import data from a JSONL file by issuing POST requests for each record. Each line must be a valid JSON object. Failed records are logged to stderr but do not stop the import.

Execute one quickbooks API endpoint by its endpoint_id (from quickbooks_search). Params are passed as a JSON object; path placeholders and query strings are resolved automatically.

Search the quickbooks API for endpoints matching a natural-language query. Returns ranked endpoints with params_schema describing executor input names, locations, types, required fields, and known enum values. Call this first to find the endpoint to execute.

Run the composed close-hygiene sweep over the synced store: unapplied payments, duplicate customers and vendors, unbalanced or suspense-touching journal entries, and inactive records still referenced by open transactions — one findings list with a clean/not-clean verdict. Use this command for the full month-end hygiene sweep across all checks. Do NOT use it when you only need unapplied payments; use 'payments unapplied' instead. Run `sync` first.

Pull QuickBooks financial statements directly from the Reports API. Use this for recognized revenue, gross/operating margin, and balance-sheet balances (deferred revenue, accrued interest, debt) — figures the /query endpoint cannot aggregate. Read-only.

Pull the QBO Balance Sheet as of a date (default: today). Returns every account leaf and summary total. Pass --highlight to total and surface any account or group by name substring (repeatable), e.g. "deferred revenue" or "accrued interest". Read-only.

Pull the QBO Profit & Loss report for a period (default: last closed month). Returns recognized revenue by account, COGS, gross profit/margin, operating income/margin, and net income — the closed-books numbers, accrual basis.

Full-text search across all synced data. Faster than paginating list endpoints. Requires sync first.

Run read-only SQL against local database. Use for ad-hoc analysis, aggregations, and joins across synced resources. Requires sync first.

Sync data from the API into a local SQLite database. Supports resumable incremental sync (only fetches new data since last sync) and full resync. Once synced, use the 'search' command for instant full-text search. Exit codes & warnings: Resources the API denies access to (HTTP 403, or HTTP 400 with an access-policy body) are reported as warnings rather than failing the run. In --json mode each is emitted as a {"event":"sync_warning",...} line carrying status, reason, and message fields, and a final {"event":"sync_summary",...} aggregates the run. Exit 0 when at least one resource synced and no resource flagged in the spec as critical (x-critical: true) failed; non-critical failures emit {"event":"sync_warning","reason":"exit_policy_default_changed", ...} so callers can detect that a partial failure was tolerated. Pass --strict to exit non-zero on any per-resource failure. Exit is always non-zero when every selected resource failed, regardless of --strict. Resource scoping: --resources runs the named top-level resources, plus any parent-keyed dependent whose own name is listed OR whose parent table is listed. Naming a parent therefore cascades to its dependents (so "sync this parent and its children" works without listing every nested resource by hand). There is no flag today to suppress the cascade for a named parent. To run a dependent without re-syncing its parent, list only the dependent by name; the parent table must already be populated from a prior sync.

Compound workflows that combine multiple API operations

Archive fetches all syncable resources from the API and stores them in a local SQLite database. Supports incremental sync (only new data since last run) and full resync. After archiving, use 'search' for instant full-text search.

Show local archive status and sync state for all resources