Skip to main content
Glama
QuickBooks MCP

QuickBooks MCP

by laf-rge

QuickBooks MCP Server

An MCP server for QuickBooks Online — built for bookkeepers, CFOs, and accountants who use AI assistants in their daily workflow.

Ask your AI assistant to pull a P&L report, create a journal entry, or investigate an account balance — using plain language, not API payloads.

Why This Server?

Intuit provides an official MCP server that's a solid starting point for developers exploring the QuickBooks API. This server takes a different approach: it's designed for financial professionals working in production books.

Use natural language, not internal IDs

Intuit's server requires QuickBooks internal IDs for every reference — you need to look up a vendor's ID before creating a bill. This server resolves names automatically:

"Create a bill for PG&E, $450 to Utilities, dated 2025-01-15"
→ Vendor, account, and department names are resolved automatically

Financial reports built in

This is the only QuickBooks MCP server with report tools. Pull a P&L, Balance Sheet, or Trial Balance — broken down by month, department, or class — without leaving your AI conversation.

Safe by default

Every create and edit operation defaults to draft/preview mode. You see exactly what will be written to your books before committing. No accidental journal entries or misclassified expenses.

One query tool instead of dozens

Instead of separate search tools for each entity type, a single SQL-like query tool works across all QuickBooks entities. AI assistants write SQL naturally, and QuickBooks validates it — no field whitelists to maintain.

"SELECT * FROM Purchase WHERE TxnDate >= '2025-01-01' AND TxnDate <= '2025-01-31'"

Production-ready credential management

Store credentials locally for personal use, or in AWS Secrets Manager for shared environments. OAuth tokens refresh automatically and persist across sessions.

At a glance

Intuit Official

This Server

Audience

Developers exploring the API

Bookkeepers, CFOs, accountants

Name resolution

Requires internal QB IDs

Resolves names automatically

Financial reports

None

P&L, Balance Sheet, Trial Balance

Write safety

Executes immediately

Draft preview by default

Query approach

Entity-specific search tools

SQL-like queries across all entities

Credentials

Local .env file

Local file or AWS Secrets Manager

Distribution

Clone from GitHub

npx quickbooks-mcp

Related MCP server: penni-mcp

Prerequisites

Installation Options

Choose the setup that fits your use case:

Setup

Best For

NPM Install

Quick setup, using your own QuickBooks app

Local Checkout

Development, customization

AWS Mode

Shared/production environments


Option 1: NPM Install

The simplest way to get started. Credentials are stored locally on your machine.

1. Create a QuickBooks App

  1. Go to developer.intuit.com and sign in

  2. Create a new app (or select an existing one)

  3. Go to "Keys & credentials"

  4. Note your Client ID and Client Secret

  5. Under "Redirect URIs", add: https://developer.intuit.com/v2/OAuth2Playground/RedirectUrl

2. Add to Claude Code

Add to your project's .mcp.json:

{
  "mcpServers": {
    "quickbooks": {
      "command": "npx",
      "args": ["-y", "quickbooks-mcp"]
    }
  }
}

3. Configure Credentials

Create ~/.quickbooks-mcp/credentials.json:

{
  "client_id": "your_client_id",
  "client_secret": "your_client_secret"
}

4. Authenticate

Once Claude Code is running, use the qbo_authenticate tool:

  1. Call qbo_authenticate with no arguments to get an authorization URL

  2. Open the URL in your browser and authorize the app

  3. Copy the code and realmId from the redirect URL

  4. Call qbo_authenticate again with the authorization code and realm ID

Your OAuth tokens will be saved and automatically refreshed.


Option 2: Local Checkout

For development or customization.

1. Create a QuickBooks App

Follow the same steps as Option 1 above.

2. Clone and Build

git clone https://github.com/laf-rge/quickbooks-mcp.git
cd quickbooks-mcp
npm install
npm run build

3. Add to Claude Code

Add to your project's .mcp.json:

{
  "mcpServers": {
    "quickbooks": {
      "command": "node",
      "args": ["/path/to/quickbooks-mcp/dist/index.js"]
    }
  }
}

4. Configure Credentials

Create ~/.quickbooks-mcp/credentials.json with your client credentials (same as Option 1), then run qbo_authenticate to complete the OAuth flow.


Option 3: AWS Mode

For shared or production environments. Stores credentials in AWS Secrets Manager.

1. Create AWS Resources

Create the secret in Secrets Manager:

aws secretsmanager create-secret \
  --name prod/qbo \
  --secret-string '{
    "client_id": "your_client_id",
    "client_secret": "your_client_secret",
    "access_token": "your_access_token",
    "refresh_token": "your_refresh_token",
    "redirect_url": "https://developer.intuit.com/v2/OAuth2Playground/RedirectUrl"
  }'

Store Company ID in SSM Parameter Store:

aws ssm put-parameter \
  --name /prod/qbo/company_id \
  --value "your_company_id" \
  --type SecureString

2. Configure the Server

Create a .env file in the quickbooks-mcp directory:

QBO_CREDENTIAL_MODE=aws
AWS_REGION=us-east-2
QBO_SECRET_NAME=prod/qbo
QBO_COMPANY_ID_PARAM=/prod/qbo/company_id

Note: Due to a known Claude Code bug, environment variables from .mcp.json are not reliably passed to MCP servers. The .env file workaround is required.

3. Add to Claude Code

{
  "mcpServers": {
    "quickbooks": {
      "command": "node",
      "args": ["/path/to/quickbooks-mcp/dist/index.js"]
    }
  }
}

4. IAM Permissions

The server needs these AWS permissions:

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": [
        "secretsmanager:GetSecretValue",
        "secretsmanager:PutSecretValue"
      ],
      "Resource": "arn:aws:secretsmanager:*:*:secret:prod/qbo*"
    },
    {
      "Effect": "Allow",
      "Action": ["ssm:GetParameter"],
      "Resource": "arn:aws:ssm:*:*:parameter/prod/qbo/*"
    }
  ]
}

Inline Output Mode

By default, large responses (reports, query results) are written to /tmp files and the server returns a file path. This works well for Claude Code in terminal environments but breaks in Claude Desktop and plugin environments where the model cannot read from /tmp.

Set QBO_INLINE_OUTPUT=true to return all responses inline instead.

Option A — via .env file (recommended for local checkout):

Create a .env file in the quickbooks-mcp directory:

QBO_INLINE_OUTPUT=true

Option B — via .mcp.json env block (recommended for NPM install):

{
  "mcpServers": {
    "quickbooks": {
      "command": "npx",
      "args": ["-y", "quickbooks-mcp"],
      "env": {
        "QBO_CREDENTIAL_MODE": "local",
        "QBO_INLINE_OUTPUT": "true"
      }
    }
  }
}

Note: Due to a known Claude Code bug, environment variables from .mcp.json are not reliably passed to MCP servers in some configurations. If Option B doesn't work, use the .env file workaround.


Environment Variables

Variable

Default

Description

QBO_CREDENTIAL_MODE

local

Credential storage: local or aws

QBO_CLIENT_ID

-

QuickBooks app Client ID (local mode)

QBO_CLIENT_SECRET

-

QuickBooks app Client Secret (local mode)

QBO_CREDENTIAL_FILE

~/.quickbooks-mcp/credentials.json

Custom credential file path. A leading ~ is expanded to your home directory, so it works in an MCP client's JSON env block where no shell is present to expand it.

QBO_INLINE_OUTPUT

false

Return responses inline instead of writing to /tmp files. Required when using Claude Desktop or plugin environments where file-based output is not accessible to the model.

QBO_SANDBOX

false

Use QuickBooks sandbox environment. Also switches the "View in QuickBooks" deep links to app.sandbox.qbo.intuit.com so they cannot open the production company.

AWS_REGION

us-east-2

AWS region (aws mode)

QBO_SECRET_NAME

prod/qbo

Secrets Manager secret name (aws mode)

QBO_COMPANY_ID_PARAM

/prod/qbo/company_id

SSM parameter path (aws mode)


Available Tools

Tool

Description

Setup

qbo_authenticate

Set up OAuth credentials (local mode only)

get_company_info

Get connected company information

Query & Reports

query

Run SQL-like queries against any QuickBooks entity

list_accounts

List chart of accounts with filtering

get_profit_loss

Profit & Loss report (by month, department, class, etc.)

get_balance_sheet

Balance Sheet report

get_trial_balance

Trial Balance report (flags: true adds a close-review pass for wrong-side and uncategorized/suspense balances)

get_report

Any of 24 other QuickBooks reports — A/R and A/P aging, customer and vendor balances, transaction lists, general ledger, journal, sales by customer/item/class/department, cash flow, and the detail variants

query_account_transactions

All transactions affecting a specific account (13 posting entity types, paginated, optional sub-account rollup; see docs/entity-coverage.md for limits)

account_period_summary

Period summary for an account (opening/closing balance, debits, credits, count)

Journal Entries

create_journal_entry

Create a journal entry (validates debits = credits; lines take entity_name/entity_type)

get_journal_entry

Fetch a journal entry by ID

edit_journal_entry

Modify an existing journal entry

Bills

create_bill

Create a vendor bill (lines take customer_name)

get_bill

Fetch a bill by ID

edit_bill

Modify an existing bill

Expenses

create_expense

Create an expense (Cash, Check, or Credit Card; payee may be a vendor, customer, or employee)

get_expense

Fetch an expense by ID

edit_expense

Modify an existing expense

Sales Receipts

create_sales_receipt

Create a sales receipt with item lines

get_sales_receipt

Fetch a sales receipt by ID

edit_sales_receipt

Modify an existing sales receipt

Invoices

create_invoice

Create an invoice with item lines (customer required)

get_invoice

Fetch an invoice by ID

edit_invoice

Modify an existing invoice

Deposits

create_deposit

Create a bank deposit (lines take entity_name/entity_type)

get_deposit

Fetch a deposit by ID

edit_deposit

Modify an existing deposit (lines take entity_name/entity_type)

Vendor Credits

create_vendor_credit

Create a vendor credit (lines take customer_name)

get_vendor_credit

Fetch a vendor credit by ID

edit_vendor_credit

Modify an existing vendor credit

Bill Payments

create_bill_payment

Pay bills and apply vendor credits (the QBO "check" / pay-bills flow)

receive_payment

Record a customer payment against open invoices (A/R counterpart to create_bill_payment); each line defaults to the invoice's open balance

create_transfer

Move money between two of the company's own accounts (bank↔bank, credit-card paydown)

get_bill_payment

Fetch a bill payment by ID; flags unapplied amounts

Vendors

create_vendor

Create a vendor (contact, billing address, terms, account number, 1099 flag)

edit_vendor

Sparse-update a vendor; active: false deactivates. Read vendors with query

Delete

delete_entity

Delete any transaction (journal entry, bill, invoice, deposit, sales receipt, expense, vendor credit, bill payment)

Naming Vendors, Customers, and Employees

Every write tool that can attribute a line or a header to a name list accepts a name and resolves it to an ID, the same way account_name and department_name do. Which parameter you get depends on what QuickBooks will actually store there:

Parameter

Where it applies

Accepts

entity_name + entity_type

create_deposit / edit_deposit lines, create_journal_entry / edit_journal_entry lines, create_expense / edit_expense header payee

Vendor, Customer, or Employee. entity_type defaults to Vendor.

customer_name

create_bill / edit_bill, create_expense / edit_expense, create_vendor_credit / edit_vendor_credit lines

Customer only — QuickBooks stores a CustomerRef on these lines and has no vendor or employee option.

vendor_name

create_bill, create_vendor_credit, create_bill_payment headers

Vendor only.

customer_name (header)

create_invoice, create_sales_receipt

Customer only. Their item lines have no per-line entity.

Each also has an _id form (entity_id, customer_id) if you already know the internal ID. On edit tools, the rule for line parameters is:

  • omit the parameter and a line addressed by line_id keeps the entity it already has;

  • name one and it is set or replaced;

  • pass an empty string (entity_name: "") and it is cleared.

See docs/quickbooks-api-limitations.md for the underlying QBO field shapes, which are not uniform.

Parameter Names Are Enforced

Arguments are checked against the schema each tool advertises, before anything runs. An unknown parameter is an error that names the closest valid one, a missing required parameter is an error, and an edit_* call with no field to change is an error rather than a write that reports success.

The alternative is silence. A handler reads the parameters it knows about, so a misspelled one is simply absent: a create call that puts the date under the wrong key posts on today's date, an as-of report asked for a date range returns today's balances, and an edit whose fields are all misspelled comes back "updated successfully" having changed nothing. None of those raise anything for the caller to notice.

Relatedly, when QuickBooks accepts an update without advancing the record's SyncToken — meaning the payload matched what was already stored — the edit tools report no change instead of success.


Token Refresh

The server automatically refreshes OAuth tokens on each request and persists them back to your credential store (local file or AWS Secrets Manager).


Development

npm run dev      # Run in development mode
npm run build    # Build
npm run typecheck # Type check
npm test         # Run the test suite

Tests live in tests/, mirroring src/. They are TypeScript, compiled by tsconfig.test.json into dist-test/ and run by Node's built-in test runner — no test framework dependency. Type errors in a test are build failures, so a test referencing a renamed export fails loudly rather than silently skipping. Anything needing a QuickBooks client passes a hand-written stand-in covering just the calls under test, so the suite runs offline with no credentials.


Troubleshooting

"QuickBooks credentials not configured"

Run the qbo_authenticate tool to set up OAuth credentials (local mode only).

"Authorization code expired"

Authorization codes are only valid for a few minutes. Start the OAuth flow again.

Token refresh fails

  • Check that your refresh token hasn't expired (~100 days)

  • Verify your client credentials are correct

  • Try re-authenticating with qbo_authenticate

AWS credential errors

  • Ensure .env file has QBO_CREDENTIAL_MODE=aws

  • Check your AWS credentials and permissions

  • Verify the secret and parameter names match your configuration

Available Tools

36 tools
account_period_summaryB

Get a period summary for an account: opening balance, total debits/credits, closing balance, and transaction count. Uses the General Ledger report. Supports department filtering.

Inputs: account (required), start_date, end_date, department, +1 more.

create_billA

Create a vendor bill. Accepts vendor/account/department names (will lookup IDs automatically). Note: DepartmentRef is header-level only — for multi-department splits, create separate bills (one per department). Returns bill details and a link to view in QuickBooks.

Inputs: txn_date (required), lines (required), vendor_name, vendor_id, +7 more.

create_bill_paymentA

Create a bill payment (the QBO 'check' / 'pay bills' flow). Pays one or more existing bills and optionally applies vendor credits, clearing Accounts Payable. Use this to record vendor ACH/EFT debits or checks so the bank feed can match them — especially when a bank charge equals bills minus credit memos. Amounts default to each bill's open balance and each credit's remaining balance. Returns payment details and a link to view in QuickBooks.

Inputs: payment_account (required), txn_date (required), bills (required), vendor_name, +5 more.

create_customerA

Create a customer or sub-customer. Accepts name parts, contact info, addresses, and hierarchy settings. Use parent_ref to create sub-customers or jobs. Returns customer details and a link to view in QuickBooks.

Inputs: display_name (required), given_name, middle_name, family_name, +15 more.

create_depositA

Create a bank deposit. Accepts account/department/vendor names (will lookup IDs automatically). Lines represent the sources of the deposit — amounts can be positive (income) or negative (fees, deductions). QuickBooks computes the total from line amounts. Returns deposit details and a link to view in QuickBooks.

Inputs: deposit_to_account (required), txn_date (required), lines (required), department_name, +3 more.

create_expenseA

Create an expense (Purchase). Accepts account/department/vendor names (will lookup IDs automatically). Covers Cash, Check, and Credit Card payment types. Note: PaymentType cannot be changed after creation. DepartmentRef is header-level only. Returns expense details and a link to view in QuickBooks.

Inputs: payment_type (required), payment_account (required), txn_date (required), lines (required), +7 more.

create_invoiceA

Create an invoice. Accepts item/customer/department names (will lookup IDs automatically). Either customer_name or customer_id is REQUIRED — invoices must have a customer. Lines use SalesItemLineDetail (product/service references, not accounts). Returns invoice details and a link to view in QuickBooks.

Inputs: txn_date (required), lines (required), customer_name, customer_id, +11 more.

create_journal_entryB

Create a journal entry. Accepts account/department names (will lookup IDs automatically). Validates debits=credits before creating. Returns entry details and a link to view in QuickBooks.

Inputs: txn_date (required), lines (required), memo, draft, +1 more.

create_sales_receiptA

Create a sales receipt. Accepts item/customer/department names (will lookup IDs automatically). Lines reference items (products/services) not accounts. Returns receipt details and a link to view in QuickBooks.

Inputs: txn_date (required), lines (required), customer_name, customer_id, +6 more.

create_vendor_creditA

Create a vendor credit. Accepts vendor/account/department names (will lookup IDs automatically). Lines represent credit amounts applied to expense accounts. Returns credit details and a link to view in QuickBooks.

Inputs: txn_date (required), lines (required), vendor_name, vendor_id, +6 more.

delete_entityA

Permanently delete a QuickBooks transaction. Supports journal entries, bills, invoices, deposits, sales receipts, expenses, vendor credits, and bill payments. Uses a two-step flow: first call previews what will be deleted, second call with confirm=true executes the deletion. Note: Customers cannot be deleted — use edit_customer with active=false to deactivate instead.

Inputs: entity_type (required), id (required), confirm.

edit_billA

Modify an existing bill. Can update vendor, date, due date, memo, and/or lines. For lines: provide line_id to update existing line, omit to add new line, set delete=true to remove. Note: DepartmentRef is header-level only — lines do not support department.

Inputs: id (required), vendor_name, txn_date, due_date, +5 more.

edit_customerA

Modify an existing customer. Can update name, contact info, addresses, notes, taxable status, active status, hierarchy (parent/sub-customer), delivery method, and payment terms. Set active=false to deactivate (QuickBooks equivalent of delete).

Inputs: id (required), display_name, given_name, middle_name, +17 more.

edit_depositA

Modify an existing deposit. Can update date, memo, deposit account, department, and/or lines. CRITICAL for line changes: The QB Deposit API does NOT replace lines - it merges them. Lines WITH line_id update existing lines. Lines WITHOUT line_id are ADDED as new. Lines NOT included are KEPT unchanged. To 'delete' a line, you must include ALL existing lines with their line_ids and set unwanted lines to amount: 0. Line amounts must sum to the original deposit total (use expected_total to override for corrupted deposits).

Inputs: id (required), txn_date, memo, deposit_to_account, +4 more.

edit_expenseA

Modify an existing expense (Purchase). Can update date, memo, payment account, and/or lines. Note: PaymentType (Cash/Check/CreditCard) cannot be changed after creation.

Inputs: id (required), txn_date, memo, payment_account, +5 more.

edit_invoiceA

Modify an existing invoice. Can update date, due date, memo, customer, department, terms, email, online payment settings, and/or lines. For lines: provide line_id to update existing line, omit line_id to add new line (requires item_name), set delete=true to remove.

Inputs: id (required), txn_date, due_date, memo, +9 more.

edit_journal_entryA

Modify an existing journal entry. Can update date, memo, doc_number, and/or lines. For lines: provide line_id to update existing line, omit line_id to add new line, set delete=true to remove a line. Validates debits=credits before saving.

Inputs: id (required), txn_date, memo, doc_number, +2 more.

edit_sales_receiptA

Modify an existing sales receipt. Can update date, memo, deposit account, department, and/or lines. For lines: provide line_id to update existing line, omit line_id to add new line (requires item_name), set delete=true to remove.

Inputs: id (required), txn_date, memo, deposit_to_account, +3 more.

edit_vendor_creditA

Modify an existing vendor credit. Can update vendor, date, memo, ref number, and/or lines. For lines: provide line_id to update existing line, omit line_id to add new line (requires amount and account_name), set delete=true to remove. Note: DepartmentRef is header-level only — lines do not support department.

Inputs: id (required), vendor_name, txn_date, memo, +3 more.

get_balance_sheetB

Get a Balance Sheet report. Can be broken down by department/location.

Inputs: as_of_date, summarize_by, department, accounting_method.

get_billA

Fetch a single bill by ID with full details including SyncToken (needed for edits). Returns vendor, date, due date, amount, AP account, line details.

Inputs: id (required).

get_bill_paymentA

Fetch a single bill payment by ID with full details including SyncToken. Shows vendor, date, pay type, bank account, linked bills/credits with applied amounts, and flags any unapplied amount (payment total not matching net applied lines).

Inputs: id (required).

get_company_infoA

Get information about the connected QuickBooks company.

Inputs: no named parameters.

get_customerA

Fetch a single customer by ID with full details including SyncToken (needed for edits). Returns name, contact info, addresses, balance, hierarchy (parent/sub-customer), and active status.

Inputs: id (required).

get_depositA

Fetch a single deposit by ID with full details including SyncToken (needed for edits). Returns deposit account, date, memo, and line details showing source accounts and amounts.

Inputs: id (required).

get_expenseA

Fetch a single expense (Purchase) by ID with full details including SyncToken. Covers Expenses, Checks, and Credit Card charges. Returns payment type, account, date, amount, line details.

Inputs: id (required).

get_invoiceA

Fetch a single invoice by ID with full details including SyncToken (needed for edits). Returns customer, date, due date, balance, department, line details with items/qty/price.

Inputs: id (required).

get_journal_entryA

Fetch a single journal entry by ID with full details including SyncToken (needed for edits). Returns formatted summary and writes full object to temp file.

Inputs: id (required).

get_profit_lossC

Get a Profit and Loss (Income Statement) report. Can be broken down by department/location.

Inputs: start_date, end_date, summarize_by, department, +1 more.

get_sales_receiptA

Fetch a single sales receipt by ID with full details including SyncToken (needed for edits). Returns customer, date, deposit account, department, line details with items/qty/price.

Inputs: id (required).

get_trial_balanceA

Get a Trial Balance report. Useful for month-end close and reconciliation. Note: Trial Balance does not support department/location breakdown in QuickBooks Online.

Inputs: start_date, end_date, accounting_method.

get_vendor_creditA

Fetch a single vendor credit by ID with full details including SyncToken (needed for edits). Returns vendor, date, memo, ref number, AP account, and line details showing expense accounts and amounts.

Inputs: id (required).

list_accountsA

List all accounts in the chart of accounts. Returns AcctNum (the user-facing account number), Name, AccountType, AccountSubType, and CurrentBalance. Use AcctNum to reference accounts in other queries or operations.

Inputs: account_type, active_only.

qbo_authenticateA

Authenticate with QuickBooks using OAuth (local credential mode only). Step 1: Call with no arguments to get the authorization URL. Step 2: After authorizing in browser, call with authorization_code and realm_id from the callback URL. This tool only works when QBO_CREDENTIAL_MODE is 'local' (the default).

Inputs: authorization_code, realm_id.

queryA

Execute a QuickBooks query using SQL-like syntax. Supports querying any entity type (Customer, Vendor, Invoice, Bill, Account, Item, Department, etc.). Results are written to a file to preserve context. Defaults to MAXRESULTS 1000 if not specified. Examples: 'SELECT * FROM Customer', 'SELECT * FROM SalesReceipt WHERE TxnDate >= '2025-11-01' AND TxnDate <= '2025-11-30''

Inputs: query (required).

query_account_transactionsA

Query all transactions affecting a specific account. Searches across JournalEntry, Purchase, Deposit, SalesReceipt, Bill, Invoice, and Payment. Returns consolidated list with date, type, amount (debit/credit), and description. Useful for investigating account balance discrepancies.

Inputs: account (required), start_date, end_date, department.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4/5.0

    Scored across 36 tools

    Disambiguation5/5

    Each tool targets a distinct entity or operation (e.g., create_bill vs. create_invoice, get_balance_sheet vs. get_profit_loss). There is no overlap in purpose; even similar operations like edit_bill and edit_expense operate on different business objects. Clear disambiguation.

    Naming Consistency4/5

    Most tools follow a consistent verb_noun pattern (create_bill, get_invoice, list_accounts). Minor deviations include query (no noun) and qbo_authenticate (prefix instead of verb), but these are isolated and still intuitive.

    Tool Count5/5

    With 36 tools covering CRUD for multiple financial entities, reports, and utilities, the count is appropriate for a comprehensive QuickBooks integration. Each tool addresses a specific need without unnecessary duplication.

    Completeness5/5

    The tool set covers the full lifecycle of core entities (customers, vendors, invoices, bills, payments, deposits, expenses, journal entries) with create, read, update, and delete operations. Reports and a generic query tool fill gaps, making it functionally complete for typical accounting workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessUsually handled

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to query and manage QuickBooks Online data through natural language, including customers, invoices, bills, vendors, accounts, and financial reports.
      7
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      AI bookkeeper for small businesses that connects to QuickBooks Online. Enables users to query financial data like bank balances, P\&L reports, and invoices through natural language in Claude Desktop or Cursor.
      6
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Connects AI assistants to QuickBooks Online, enabling management of invoices, customers, expenses, and reports through natural language.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables full CRUD operations on 29 QuickBooks Online entity types and 11 financial reports via natural language, allowing users to manage customers, invoices, payments, and more through MCP-compatible clients.
      Apache 2.0