ConnectQuickBooks connector

A QuickBooks connector for any AI agent.

LedgerLou is a hosted MCP server for QuickBooks Online. Any agent that can reach a remote MCP server with a key can work with your books: Grok, Cursor, VS Code, or one you built yourself.

  • Available now

What your agent can do

Your agent, working in your QuickBooks.

Your agent picks the right tool for what you ask. You don’t name tools or write queries.

Look anything up

Find invoices, bills, expenses, customers and vendors with a QuickBooks query, or read one record in full.

Run reports

Profit and Loss, Balance Sheet, Cash Flow, Trial Balance, General Ledger, and aged receivables and payables.

Make the changes you allow

With a read-and-write key: create and edit transactions, void or delete them, and email invoices and estimates.

Files and PDFs

Attach a receipt to an expense, or fetch the PDF of an invoice to save or send on.

Every company, one key

A key reaches every QuickBooks company connected to your LedgerLou account.

The whole accounting API

Fourteen tools cover the QuickBooks Online accounting API, not a few canned actions.

Every tool, and what each one does, is in the tool reference.

Set up

One key, and your agent’s MCP settings.

Every client needs the same two things: LedgerLou’s address and your key, sent as a header. Here they are, then the exact setup for a few common agents.

  1. 1

    Create your account and a key

    Create a free account and connect QuickBooks. Then open Settings → API keys, choose read-only or read-and-write, and copy the key. We show it once.

  2. 2

    Point your agent at LedgerLou

    Use these settings in any MCP client:

    URL
    https://app.ledgerlou.com/api/mcp
    Transport
    Streamable HTTP
    Header
    Authorization: Bearer YOUR_KEY
  3. 3

    Ask your agent

    Start a new session and ask it to list my QuickBooks companies. Every other request works in one of those companies.

Grok

With Grok’s command-line tool, add LedgerLou in one command. Developers on the xAI API can attach the same URL and key as a remote MCP tool; the API runs tools without asking first, so start it on a read-only key. Connectors added on grok.com sign in rather than take a key, so they can’t connect yet.

Terminal
grok mcp add --transport http ledgerlou https://app.ledgerlou.com/api/mcp --header "Authorization: Bearer YOUR_KEY"

Cursor

Add this to ~/.cursor/mcp.json, your settings for every project, and restart Cursor.

~/.cursor/mcp.json
{
  "mcpServers": {
    "ledgerlou": {
      "url": "https://app.ledgerlou.com/api/mcp",
      "headers": { "Authorization": "Bearer YOUR_KEY" }
    }
  }
}

VS Code

Run MCP: Open User Configuration from the Command Palette and add this. VS Code asks for the key the first time and keeps it out of the file.

mcp.json
{
  "inputs": [
    { "id": "ledgerlou-key", "type": "promptString", "description": "LedgerLou key", "password": true }
  ],
  "servers": {
    "ledgerlou": {
      "type": "http",
      "url": "https://app.ledgerlou.com/api/mcp",
      "headers": { "Authorization": "Bearer ${input:ledgerlou-key}" }
    }
  }
}

Clients change their menus and file locations; if a step doesn’t match what you see, your agent’s own MCP documentation has the current one. Using Claude Code? See the Claude setup.

In your control

You decide what your agent can touch.

Read-only or read-and-write

You choose per key. A read-only key can look things up and run reports but can't change anything.

Revoke at any time

Revoke a key under Settings → API keys and it stops working at once.

A record of every write

Each change made through Connect is recorded, whether it succeeded or failed.

Worth knowing: Connect doesn't use Lou's approval gate. A change posts when your agent makes it, so its own permission prompt is the only checkpoint, and not every agent has one: the xAI API runs tools without asking. If you only want answers, create a read-only key.

Questions

Connecting other agents, answered.

Which agents can connect?

Any MCP client that connects to remote servers over Streamable HTTP and lets you send an Authorization header. That includes Claude Code, Grok's command-line tool and the xAI API, Cursor and VS Code.

Can I connect from grok.com?

Not yet. Connectors added on grok.com connect by signing in, and LedgerLou connects with a key today. Grok's command-line tool and the xAI API accept the key.

Is there anything to install?

No. LedgerLou is a hosted, remote MCP server. Your agent connects to it over HTTPS with your key.

Where should I keep the key?

Somewhere private: your user-level settings rather than a project file that could be committed, or a prompt or environment variable where your client supports one. If a key leaks, revoke it under Settings → API keys and create another.

Do I need an Intuit developer account?

No. You connect QuickBooks to LedgerLou through Intuit's own sign-in, and LedgerLou handles the QuickBooks API for you.

Want every change previewed first?

“Ask me inside LedgerLou. I work in the same QuickBooks companies, draft each change for you to review, and post nothing until you approve it.”

Lou, the bookkeeper built into LedgerLou

How Lou works

Give your agent your books.

Create a free account, connect QuickBooks, and create a key. You decide whether it can change anything.