# How do you connect QuickBooks to Claude? Connect QuickBooks to Claude through an MCP integration such as Composio, authorize the company file, and ask Claude about invoices, balances, and customers. Source: https://areaproperti.top/how-do-you-connect/ · based on the channel [Composio](https://www.youtube.com/channel/UCEuoGOJFuXUZZhprSAAK85Q) · Video: [How to connect QuickBooks to Claude (in under a minute)](https://www.youtube.com/watch?v=EBej9odHNJ8) · 2026-10-21 ![How do you connect QuickBooks to Claude?](https://areaproperti.top/how-do-you-connect/how-do-you-connect.webp) ## Key takeaways - Claude has no native QuickBooks connector, so the link is made through a third-party MCP integration such as Composio. - The setup takes under a minute: pick QuickBooks, authorize the company file, and copy the MCP endpoint into Claude. - Access is read and write, so Claude can create invoices and customers, not just read reports. - The connection runs on Intuit's OAuth 2.0, and tokens must be refreshed or the link breaks. - Claude Desktop, Claude Code, and the web app can all use the same MCP server endpoint. Claude does not ship with a built-in QuickBooks connector, so you connect the two through a third-party MCP (Model Context Protocol) integration such as Composio: you authorize your QuickBooks company file once, copy the generated MCP endpoint, and register it in Claude as a connector. After that, Claude can read invoices, customers, and account balances, and write new records, directly from a chat prompt. ## What connecting QuickBooks to Claude actually means Anthropic's Claude is a language model with a connector layer called MCP, and QuickBooks Online is a cloud accounting product from Intuit with a REST API. The bridge between them is an MCP server that wraps QuickBooks API calls as tools the model can call. Composio, the channel behind the walkthrough, is one of the services that hosts such a server for you, so you do not write OAuth code or host anything yourself. Once the link is live, QuickBooks appears to Claude as a set of callable actions: list invoices, fetch a customer, read a profit and loss report, create an invoice, add a customer. Claude decides which tool to call based on your prompt, executes it against your live company file, and summarizes the result in plain language. ## Prerequisites before you start Five things need to be in place, and missing any one of them is the usual reason a connection fails on the first attempt. 1. An active QuickBooks Online subscription. QuickBooks Desktop and the self-hosted Enterprise edition are not covered by the standard cloud API path. 2. Admin rights on the QuickBooks company, because the OAuth consent screen requires an administrator to approve the app. 3. A Claude account with connector support: Claude Desktop, Claude Code, or the Claude web app on a paid plan. 4. A Composio account, which issues the API key and the MCP endpoint you will paste into Claude. 5. A stable internet connection on the machine running Claude Desktop, since the MCP server is remote rather than local. ## Step-by-step: connect QuickBooks to Claude The whole flow is short because the authorization happens in the browser and the only technical artifact you handle is a single URL. 1. Sign in to the Composio dashboard and open the app catalog. 2. Search for QuickBooks and select it, then start a new connection. 3. Choose QuickBooks Online as the environment and click connect; you are redirected to Intuit's OAuth consent screen. 4. Pick the correct company file if your login has access to more than one, then approve the requested scopes. 5. Copy the MCP server URL that Composio generates for this connection, and copy the API key alongside it. 6. Open Claude, go to Settings, then Connectors, and add a custom MCP server. 7. Paste the URL, add the API key as a header or bearer token if the form asks for one, and save. 8. Start a new chat and ask something simple, such as listing the five most recent invoices, to confirm the tools are visible. If the connector list stays empty after saving, restart the Claude client; desktop builds cache the connector list at launch. ## What you can ask Claude to do once it is linked Read operations are the safest starting point. Typical prompts include summarizing unpaid invoices older than 30 days, pulling the balance for a specific bank account, listing customers in a given state, or comparing revenue between two periods. Claude calls the matching QuickBooks endpoint and returns a table or a short narrative. Write operations work too, and this is where the integration earns its keep. Claude can draft and create an invoice from a description of the work, add a new customer record with billing details, or attach a memo to an existing transaction. Every write hits your live books, so treat the first few prompts as tests on a sandbox company file and check the result inside QuickBooks before trusting the pattern. ## Common problems and how to fix them A failed connection almost always falls into one of four buckets. - Token expiry: Intuit access tokens are short-lived and refresh tokens rotate, so a connection left idle for weeks may need re-authorization from the Composio dashboard. - Wrong company: if the OAuth grant was approved for a different company file than the one you meant, disconnect and reconnect with the right file selected. - Scope mismatch: read-only approval blocks any create or update action, and Claude will report a permission error rather than silently failing. - Client caching: Claude Desktop sometimes needs a full restart before newly added MCP servers appear in the tool list. ## Security and access control Connecting an accounting system to an AI assistant is a real grant of authority, not a read-only preview. The OAuth token lets the MCP server act as you within the scopes you approved, so review those scopes on the consent screen instead of clicking through. Revoke access from the QuickBooks app management page or the Composio dashboard when a project ends, and prefer a dedicated QuickBooks user for the integration so audit trails stay readable. Keep the API key out of shared documents and chat threads; anyone holding it can reach the same company file. ## Summary QuickBooks and Claude are joined through an MCP server rather than a native plugin, and a hosted service like Composio reduces the setup to an OAuth approval and one URL pasted into Claude's connector settings. The result is a chat interface over your live accounting data that handles both lookups and record creation. Start with read-only prompts, verify write actions on a test company, and watch token expiry so the link does not quietly go stale. The video breakdown above comes from the Composio channel, which demonstrates the full flow in under a minute. ## Questions & answers **Does Claude have a native QuickBooks integration?** No. Claude supports MCP connectors, but Intuit does not ship an official Claude plugin, so the link is built through a third-party MCP server such as Composio. The server handles the QuickBooks API and OAuth on Claude's behalf. **Can Claude change data in QuickBooks, or only read it?** It can do both, provided you approved write scopes during the OAuth consent step. Claude can create invoices and customers and update records, and every change lands in your live company file, so test write prompts on a sandbox company first. **Why does my QuickBooks connection to Claude stop working after a while?** Intuit issues short-lived access tokens and rotates refresh tokens, so an idle connection eventually loses its grant. Reconnect from the Composio dashboard, or check whether the company file or scopes changed since the original approval. **Which QuickBooks versions work with this setup?** The integration targets QuickBooks Online, which exposes the cloud REST API. QuickBooks Desktop and self-hosted Enterprise installations are not covered by this MCP path and need a different middleware approach.