Skip to content
QuickBooks Desktop (via Conductor) logo

QuickBooks Desktop (via Conductor) MCP server

Sync invoices, bills, customers, vendors and payments with QuickBooks Desktop through the Conductor API bridge.

QuickBooks Desktop (via Conductor) is not a separate install. One Activepieces MCP server exposes it alongside 760+ other apps, behind a single URL.

Tools
8
Works with
Any MCP client
Auth
Custom auth
License
MIT, open source
Updated
September 2026

About the QuickBooks Desktop (via Conductor) MCP server

Connect QuickBooks Desktop (via Conductor) once in Activepieces and every action it ships becomes a tool your assistant can call, behind the same server URL as the rest of your apps. Your agent reaches QuickBooks Desktop (via Conductor) and 760+ other apps over a single connection, on our cloud or a self-hosted install.

Tools

QuickBooks Desktop (via Conductor) tools your AI can run

Once connected, your assistant can call any of these QuickBooks Desktop (via Conductor) actions by asking in plain language.

  • Upsert Customer

    Creates a customer in QuickBooks Desktop, or updates it if one with the same name already exists.

    10 fields

  • Upsert Vendor

    Creates a vendor in QuickBooks Desktop, or updates it if one with the same name already exists.

    10 fields

  • Create Invoice

    Creates an invoice for a customer in QuickBooks Desktop.

    6 fields

  • Create Bill

    Creates a vendor bill (accounts payable) in QuickBooks Desktop, expensed against one or more accounts.

    6 fields

  • Record Payment

    Records a customer payment against open invoices, or a vendor bill payment by check or credit card, in QuickBooks Desktop.

    12 fields

  • Query Transactions

    Searches across all transaction types in QuickBooks Desktop (invoices, bills, payments, and more) with date and type filters.

    7 fields

  • List Items

    Lists Service and Non-Inventory items from QuickBooks Desktop, for finding the exact item name to use in Create Invoice's line items.

    3 fields

  • Custom API Call

    Make a custom API call to a specific endpoint

    10 fields

Triggers

QuickBooks Desktop (via Conductor) events your agent can watch

These start a run the moment something happens in QuickBooks Desktop (via Conductor), so work gets picked up on its own.

  • New or Updated Invoice

    Fires when an invoice is created or updated (e.g. line items, balance, or payment status changed) in QuickBooks Desktop. One event per invoice change, not create-only.

  • New Payment

    Fires once when a new customer payment is recorded (Accounts Receivable) in QuickBooks Desktop — a "Receive Payment" transaction, e.g. from the Record Payment action's Customer Payment mode. Create-only: editing an existing payment does not re-fire it. Vendor bill payments (Accounts Payable) do not fire this trigger.

Give your assistant QuickBooks Desktop (via Conductor)

Connect QuickBooks Desktop (via Conductor) once and every tool above is callable from Claude, Cursor or any MCP client, behind the same server URL as 760+ other apps. Free to start.

QuickBooks Desktop (via Conductor) MCP, answered.

No. That is the point of it. One Activepieces server exposes QuickBooks Desktop (via Conductor) alongside every other piece you connect, so your client keeps a single connection.

Yes. Activepieces is open source and free to start, and the MCP server is included on every plan, from the free cloud tier to any self-hosted deployment.

Connect QuickBooks Desktop (via Conductor) in Activepieces, enable the server under Settings → MCP Server, then paste your server URL into your client config. It authenticates over OAuth on first use.

It can call 8 tools, including Upsert Customer, Upsert Vendor, Create Invoice, and chain them with steps in other apps inside the same run.

Connections use OAuth2 with limited scopes and are stored under 256-bit encryption, with no API to read them back, so an agent gets scoped access rather than your keys.