Claude Code can query and work a QuickBooks Online company from the terminal through the same Model Context Protocol, or MCP, connection used by web assistants. The important difference is setup: Claude Code adds a remote server with a command, then completes OAuth when the server is first used.
This guide is for Claude Code specifically. If you use Claude in the browser, follow the Claude and QuickBooks connector guide. If you are comparing local and hosted servers before choosing one, start with the QuickBooks MCP server guide.
The One-Command Setup
Run this in your terminal:
claude mcp add --transport http deepledger https://mcp.deepledger.ai/mcp
That command registers a remote Streamable HTTP server named deepledger. There is no package to install and no local QuickBooks process to keep running.
Then:
- Start or return to a Claude Code session.
- Ask for a read-only QuickBooks action, such as "Pull this month's profit and loss."
- Complete the DeepLedger sign-in when Claude Code opens the OAuth flow.
- Select the QuickBooks organization this connection should reach.
- Return to the terminal and let the request finish.
Use claude mcp list to inspect your configured servers. Claude Code's MCP status view can also show whether the server is connected and whether authentication is waiting for action.
What the Command Connects To
The URL points to DeepLedger's hosted MCP server for accounting, not directly to the raw QuickBooks API. DeepLedger holds the QuickBooks Online connection that your organization authorized through Intuit OAuth and presents the work as 26 structured tools.
Twenty tools work with QuickBooks: transactions, reports, vendors and customers, bills, invoices, payments, expenses, deposits, journal entries, transfers, credits, estimates, recurring templates, customer email delivery, and attachments. Six platform tools coordinate the surrounding workflow: bank feeds, documents, durable client context, tasks, guided procedures, and the month-end close.
That tool layer is why the setup stays small. You do not have to create an Intuit developer app, implement token refresh, model QuickBooks entities, or build duplicate detection before the first useful request.
A Safe First Session
Start with reads, then move to a reviewed workflow.
1. Confirm the company. Ask the AI agent to read the QuickBooks company profile and state which organization it can access. This catches a wrong organization selection before any write.
2. Pull a report. Ask for a profit and loss, balance sheet, trial balance, or aging report. The result confirms the connection can reach the live ledger.
3. Inspect before acting. Try: "List uncategorized transactions from this month. Do not record anything." You can review what is present without changing it.
4. Use the review loop. Ask: "Work this month's bank feed. Record only items supported by QuickBooks history and create tasks for anything uncertain." Clear work can move; judgment calls appear in the DeepLedger portal with reasoning and a proposed treatment.
5. Close the loop. After you approve or correct a task, hand it back to the AI agent. The agent records the approved transaction and completes the task with the QuickBooks transaction reference.
Useful Claude Code Workflows for QuickBooks
Claude Code is especially useful when bookkeeping work sits beside files, scripts, or repeatable operating procedures.
- Migration checks. Compare a transformation script's output with live QuickBooks balances and open transactions.
- Receipt and invoice batches. Inspect local source files, extract the details, resolve vendors and accounts, and attach the evidence to supported QuickBooks entries.
- Financial analysis. Pull a live report, analyze it with a local model or notebook, and keep the source numbers tied to the underlying ledger.
- Bank-feed sweeps. Run a structured sequence that records supported items and routes uncertain ones to human review.
- Month-end preparation. Follow DeepLedger's six-step close procedure, update the shared Close Sheet, and stop for approval on proposed adjusting entries.
- Testing accounting automations. Use the live tool schemas while developing a local script or evaluation harness, without reimplementing the QuickBooks integration.
Claude Code can also read your repository, so be explicit about boundaries. A request to inspect a CSV is not automatically permission to record it. Say whether the session should read only, prepare a proposal, or write supported transactions.
Authentication and Scope
Interactive Claude Code sessions use OAuth. You do not paste a dl_live_ key into the command or commit a credential to .mcp.json. The grant is associated with your DeepLedger identity and the organization you select.
If your team uses a project-shared MCP configuration, share only the server definition. Each person should authenticate under their own account so access remains attributable and revocable. Headless jobs are different: they use a DeepLedger API key scoped to one organization, stored in a secret manager rather than source control. The dedicated LangChain and CrewAI guides show that pattern.
The organization boundary matters. A connection to one client company does not silently inherit access to every company in the portal. To work another company, create or authenticate the appropriate scoped connection.
Server-Side Guardrails Still Apply
Claude Code chooses tools, but the DeepLedger server controls the accounting contracts underneath them.
- Recording workflows resolve current QuickBooks entities and check for relevant open documents.
- Duplicate checks run before supported writes.
- Posted transactions cannot be deleted through the tool surface.
- Uncertain treatments become shared tasks with reasoning instead of silent guesses.
- Every call is logged in DeepLedger's worklog beside QuickBooks Online's own audit history.
- Proposed adjusting entries and the final close retain human approval boundaries.
These safeguards do not remove the need to review a broad or destructive request. They make the workflow inspectable and give unclear accounting decisions somewhere safe to go.
Troubleshooting Claude Code MCP
The server is listed but not authenticated. Trigger a read request, then complete the OAuth flow. Check the MCP status view for a pending sign-in.
The connection opens the wrong organization. Remove or re-authenticate the server and select the intended company during consent. Verify with a company-profile read before continuing.
No QuickBooks tools appear. Confirm the selected DeepLedger organization has a live QuickBooks connection in the portal. A DeepLedger account without a connected company has no ledger to expose.
A headless script cannot complete OAuth. Use an organization-scoped API key for a genuinely headless client. Do not put that key in a committed file; pass it through your environment or secret manager.
You only need browser chat. The terminal adds no advantage for an interactive bookkeeping conversation. Use the Claude custom connector setup instead.
DeepLedger gives Claude Code live QuickBooks Online tools through one hosted MCP URL, with organization-scoped access, review tasks for uncertain work, and a complete audit trail.
Create a DeepLedger account or read how the 26-tool system works.