How to Connect Microsoft Copilot to QuickBooks Online

"Connect Copilot to QuickBooks" is really three different questions, because Microsoft Copilot is a family of products with different extension points. Here is the honest map before anything else:

The common plumbing is MCP, the open protocol Microsoft adopted across its agent stack, with support generally available in Copilot Studio. DeepLedger's hosted MCP server exposes QuickBooks Online as 26 structured, permissioned, logged tools, and it speaks Streamable HTTP natively, which matters here: Copilot Studio requires Streamable HTTP and no longer accepts SSE-only servers.

One nice coincidence of sizing: Microsoft recommends keeping an agent to roughly 25 to 30 tools for reliable tool selection. DeepLedger exposes exactly 26, shaped like accounting work rather than raw API endpoints, so the whole server fits a Copilot agent without trimming.

Before You Start

1. A DeepLedger account with QuickBooks connected. Sign up at deepledger.ai and connect your QuickBooks Online company through Intuit's official OAuth flow. The first month is free, no credit card required.
2. A DeepLedger API key. Copilot Studio runs your agent server-side, so it authenticates like a headless client. Create a key in the DeepLedger portal under Settings → API Keys. Each key is scoped to one QuickBooks organization and can be revoked at any time.
3. Copilot Studio access, which comes with Microsoft 365 Copilot licensing or its own subscription and trial.

Connect Copilot Studio to QuickBooks, Step by Step

1. In Copilot Studio, open the agent you want to give bookkeeping abilities (or create a new one, e.g. Bookkeeper)
2. Go to the Tools page and select Add a tool → New tool → Model Context Protocol
3. Fill in the wizard:
   • Server URL:

     https://mcp.deepledger.ai/mcp
     

   • Authentication: API key, sent as a header. Header name Authorization, value Bearer dl_live_... (your key from the DeepLedger portal)
4. Finish the wizard. The DeepLedger tools load onto the agent, all enabled by default; you can toggle individual tools off if you want, say, a read-only reporting agent
5. Test in the built-in chat pane: "What's my net profit for July?"

The wizard also offers OAuth 2.0 for MCP servers. DeepLedger supports OAuth for interactive clients, but for a Copilot Studio agent the API key is the dependable route: no token juggling, instant revocation from the portal, and every call the agent makes is attributed to that key in the worklog.

Publish to Microsoft 365 Copilot and Teams

A Copilot Studio agent is not just a test pane. Publish it to the Microsoft 365 channel and it shows up where your team already works:

• In Microsoft 365 Copilot chat, as an agent anyone you share it with can invoke
• In Teams, as a chat participant you can ask about the books directly

That turns "check the aging list" into a Teams message: "Which invoices are more than 30 days overdue?" And because the underlying tools carry DeepLedger's review workflow, a request like "categorize this week's bank transactions" records the clear items and escalates the uncertain ones to the task list in the DeepLedger portal, where a human approves, corrects, or rejects before anything ambiguous is posted.

Scoping tip for firms: an API key is bound to a single QuickBooks organization, so one agent maps cleanly to one company. If you run several client companies, create separate keys, and either separate agents or one agent per team that owns a client.

GitHub Copilot in VS Code

If you live in an editor, this is the two-minute version. VS Code supports remote MCP servers with OAuth (version 1.101 or later), so no API key is needed:

{
  "servers": {
    "deepledger": {
      "type": "http",
      "url": "https://mcp.deepledger.ai/mcp"
    }
  }
}

Add that to your mcp.json (or run MCP: Add Server from the command palette), start the server, and VS Code walks you through the DeepLedger sign-in the first time a tool is used. GitHub Copilot's agent mode can then pull reports, query transactions, and record entries while you work, which is a surprisingly good fit for building financial scripts, checking data during a migration, or just asking the books a question without leaving the editor.

What About the Consumer Copilot App?

Honestly: not yet. The consumer Copilot at copilot.microsoft.com and the Copilot mobile apps do not support connecting your own MCP servers today. If your team is on Microsoft 365, the Copilot Studio route above gets QuickBooks into the Copilot surfaces people actually use at work. If you want a personal assistant on your books today with zero building, Claude and ChatGPT connect in two steps.

The Guardrails Underneath

Whatever the client, the same server-side rules apply:

• No delete. No tool can delete a posted transaction; void, which zeroes amounts but preserves the record, is the only destructive operation.
• Duplicate checks before writes, built into the recording tools.
• Escalation instead of guessing. Uncertain items become tasks for human review in the DeepLedger portal, with the agent's reasoning attached.
• Two audit trails. Every action is logged in DeepLedger's worklog beside QuickBooks Online's native audit log, so the paper trail holds up.
• Instant revocation. Delete the API key (or remove the tool from the agent) and access ends immediately.

For the deeper story on why this architecture is the safe way to give AI write access to a ledger, see what AI write access to QuickBooks actually means.

DeepLedger connects QuickBooks Online to Microsoft Copilot via Copilot Studio, to GitHub Copilot in VS Code, and to any MCP-capable client or framework, with scoped access, human review built into the workflow, and a complete audit trail. The first month is free, no credit card required.

Create your DeepLedger account or read how the whole system works.