MCP server for QuickBooks — anyone tried connecting AI directly to accounting software?
saw that OpenAccountants has an MCP server for QuickBooks Online in the repo. for anyone unfamiliar: MCP (Model Context Protocol) lets your AI agent connect directly to external tools — so instead of exporting a CSV and feeding it to Claude, the agent can query QBO directly.
i've been testing it locally. the setup:
- clone the mcp-server directory
- configure OAuth with your QBO app credentials
- point your AI agent at the MCP server
- agent can now pull trial balance, P&L, balance sheet data directly
early impressions:
- pulls data correctly and quickly
- the agent can cross-reference QBO data against its tax knowledge in real time
- no more "export → clean → import" cycle
concerns:
- OAuth token management is fiddly
- read-only access only (good — i do NOT want an AI writing journal entries)
- haven't stress-tested with large data sets yet
has anyone else tried this? particularly interested in whether Xero or MYOB integrations are on the roadmap.
5 replies
tested it last week with a client's QBO. the killer feature for me: asking the agent "pull the P&L for Q1 and identify any expenses that look miscategorized based on the vendor name." it found 3 entries in about 10 seconds that would have taken me 20 minutes of scrolling.
agreed on read-only being the right default. the day an AI agent can post journal entries directly is the day i retire.
the MCP approach is the right architecture. instead of the agent "knowing" your client data (dangerous), it QUERIES it on demand (controlled). big difference for data privacy.
for EU practitioners: worth checking whether pulling client data through an MCP server to a cloud model triggers GDPR data processing obligations. it probably does. local-runtime models might be the safer path here.
this is really interesting but i have practical concerns about scaling. most of my clients are on Xero (Australia), not QBO. would love to see an MCP server for Xero — the API is well-documented so it should be feasible.
also: how are you handling the OAuth credentials? storing them locally? that's another thing the engagement letter needs to cover.
tested it briefly. works well for single-entity clients. haven't tried it with consolidated or multi-currency setups yet. that's where i'd expect it to get interesting (or break).
feature request: an MCP server that can pull from BOTH QBO and the local skill file simultaneously. agent reads the books AND the tax rules at the same time. that's the dream workflow.
my firm uses both QBO and Xero depending on the client. having MCP servers for both would be transformative for the bookkeeping-to-tax pipeline.
the current workflow of "export CSV, clean it, paste into prompt" is the weakest link in the whole AI workflow. direct integration fixes that.
Sign in as a verified accountant to reply.
Sign in