Skip to content
Custom Connectors

Connect QuickBooks Online to Claude Code

Have Claude draft invoices and record expenses in QuickBooks Online. From the terminal, inside the sessions where you already work.

How do you connect QuickBooks Online to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect QuickBooks Online, you add a QuickBooks Online MCP server: a small hosted service that exposes QuickBooks Online's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own QuickBooks Online account. No API keys pasted into config files.

claude mcp add --transport http quickbooks-online https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in QuickBooks Online once connected?

Full read-write QuickBooks Online access lets Claude draft an invoice, record a bill or expense, record purchases and customer payments, add customers and vendors, and post once you approve. The bookkeeping that used to mean re-keying between Claude and the register happens where the financials already live.

  • Draft an invoice for a customer with line items, then send after you approve
  • Record an expense or bill against the right account and vendor
  • Record purchases and expenses directly to the right account and vendor
  • Create or update customer and vendor records
  • Record a customer payment against an open invoice
  • Prepare a credit memo or estimate for your review

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same QuickBooks Online access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the QuickBooks Online API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when QuickBooks Online changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build QuickBooks Online connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same QuickBooks Online connector work in claude.ai and Claude Code?
Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own QuickBooks Online account, so access always matches what that person can already see and do.
Do I need to host or maintain anything myself?
No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on QuickBooks Online's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.
Is it safe to give a coding agent write access to QuickBooks Online?
Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the QuickBooks Online account it signs in with. Revoking access is one click in QuickBooks Online.

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.