[ QuickBooks / AI agents ]

Ask QuickBooks in plain words

engini gives Claude, ChatGPT or your own agent a scoped way into QuickBooks Online. Owners, finance and account managers can ask which invoices are overdue, what a vendor was paid or what a customer bought, without a login or a report. You choose the tools, read only if you like, and every call is recorded.

QuickBooksClaudeChatGPTMCP
Read the QuickBooks guide →
An owner asks a question
  1. "Who owes us more than 60 days?"asked in Claude
  2. engini MCP serverread-only QuickBooks tools
  3. QuickBooks logo
    QuickBooks readinvoices with a balance due
  4. Answer with the invoices3 customers, 7 invoices
Illustration of the flow on this page, not a product screen.
What it does
Your AI assistant answers from live QuickBooks data
Systems
QuickBooks Online, Claude, ChatGPT, Cursor or your code
Built with
An engini MCP server, or a toolset over the SDK, CLI or REST API
Your control
Which tools; read only; every call recorded
[ 01 / The problem ]

The numbers are in QuickBooks. The questions come from everywhere.

Blurred landscape photo with the words AI agent for QuickBooks and the labels Connect, Scope, Add, Ask

In a growing company the people who need QuickBooks answers are rarely the bookkeeper: the founder wants to know who is overdue, an account manager wants a customer’s open invoices, operations wants to know whether a supplier bill was paid. Each question is a message to finance and a wait.

They already use Claude or ChatGPT. Letting the assistant read QuickBooks is the obvious step, as long as it can only read what you allow and nothing is changed by accident.

What has to be true first

  • Read-only access, unless you deliberately add more.
  • No QuickBooks password or token in a prompt.
  • A record of who asked what.
  • One setup for Claude, ChatGPT and your own agents.

How engini does it

You connect QuickBooks Online once with OAuth 2 and create an engini MCP server that exposes only the tools you choose, for example get records on invoices, bills and customers. People add it to Claude or ChatGPT and sign in through engini, with no key to copy. engini stores the credentials and adds them to each call, shows who uses each MCP server, and records every run under the user who triggered it.

[ 02 / How it works ]

QuickBooks in your assistant in four steps

01 / Connect

Connect QuickBooks

Connect QuickBooks Online in engini with OAuth 2, production or sandbox.

02 / Scope

Choose the tools

Create an MCP server with only the tools people need, for example get records on invoices, bills and customers.

03 / Add

Add it to the client

Add the server to Claude or ChatGPT as a custom connector and sign in through engini.

04 / Ask

Ask, with a record

Ask in plain words. Each call runs on the QuickBooks connection and is recorded under the person who asked.

This is the flow you will build. Start free and connect your systems.

[ 03 / What the agent reads and writes ]

What the assistant can reach

Only what the MCP server exposes. A typical read-only setup:

SystemRecordsAccess
QuickBooksInvoices and balancesRead
QuickBooksBills and vendorsRead
QuickBooksCustomers and itemsRead
enginiWho uses each MCP server; History and audit logRecorded

Connect these systems in engini and give the agent only these tools.

[ 04 / Build it with the engini skill ]

Describe it in plain words. The engini skill builds the workflow.

engini skills is engini’s plugin for Claude Code and Codex. Its workflow agent, Flo, turns a plain-language request into an engini workflow: it designs the steps, dry-runs them against your own engini account, shows you a proposal, and creates the workflow only after you approve it, always turned off. You check it in the engini designer and turn it on.

Blurred landscape photo with the QuickBooks logo, the engini mark and a frosted tile joined by a thin line, labeled read only: question, MCP server, answer

Editorial image: a question, answered from QuickBooks.

Claude Code: install once
/plugin marketplace add engini/skills
/plugin install skills@engini
Then ask for this solution
Build a workflow in my engini account that I can call from Claude over MCP: given a customer name, read that customer's open invoices from QuickBooks and return each invoice number, date, total and balance due.
  1. You need an engini account, the engini CLI (npm i -g @engini/cli) and a workspace-scoped API key, ideally a dedicated least-privilege one.
  2. Connect the systems this flow uses in engini first. Flo never creates or changes a connection and never handles your key; it tells you which command to run.
  3. Flo checks your login and workspace, searches the tool catalog, compiles the plan and shows a proposal table with every step. It creates the workflow only when you approve that proposal, and it creates it turned off.
  4. Open it in the engini designer, fill anything it left for you, and turn it on.
engini skills for Claude Code and Codex →
What the skill will never do on its own →
[ 05 / Agent Policy ]

The agent does only what you allow. Every run is on the record.

Agent Policy is how you govern agents in engini: the tools each agent may call, the account each tool uses, and a record of every call.

Toolsets

Scope every call

Hand the agent a toolset: only the tools it needs, each on the connection you choose, for example read only. engini enforces it on the server for CLI, SDK and REST API calls; a call outside the toolset is refused. An MCP server exposes only the connections and tools chosen when you set it up.

Identity

Acts with the account you connect

engini acts with the permissions of the connected account. Connect a person’s own account and it acts as that person; use a shared integration account and it acts as that account. Every run is recorded under the user who triggered it.

Audit

History and audit log

Each tool call and workflow run is recorded in History and the audit log, which supports export and streaming to your SIEM. Your agent never needs your credentials: engini stores them and adds them when it runs each call.

SOC 2 Type IIISO 27001GDPRHIPAA compliant
[ 06 / Try it now ]

Build it on your own data today

Start free, connect QuickBooks, and build this flow with the engini skill, in Workflow Studio, or from your own agent.

  • 01Workflow Studio. Build the flow on a visual canvas, with an AI agent step where judgment is needed. Start free →
  • 02Your own agent. Give Claude, ChatGPT or Cursor an engini MCP server with only these tools. MCP client setup →
  • 03The engini skill. Ask Flo in Claude Code or Codex and review its proposal. Install the skill →
[ 07 / Questions ]

Questions buyers ask before they start

Can Claude or ChatGPT read QuickBooks Online?

Yes, through an engini MCP server that exposes only the QuickBooks tools you choose. The client signs in through engini over OAuth.

Can we keep it read only?

Yes. Expose only get tools on the MCP server; the assistant cannot see or call anything else.

Does the assistant see our QuickBooks credentials?

No. Your agent never needs your credentials: engini stores them and adds them when it runs each call, so keys stay out of prompts and tool inputs.

Can we see who is using it?

Yes. engini shows who uses each MCP server and records every run under the user who triggered it.