Skip to main content
Conductor’s MCP lets Claude, ChatGPT, Codex, Cursor, and other AI tools work with your QuickBooks Desktop and Enterprise company files. Ask in plain English who owes you money or for last month’s profit and loss, or have the AI tool create an invoice or record a payment. The AI tool reaches every QuickBooks Desktop record type and report: it can read, create, and update records, and delete or void transactions. Claude reads without asking and asks before each change unless you choose Always allow. Read-only mode lets the AI tool read your books without changing them.

Server address

Conductor’s MCP server is at https://mcp.conductor.is/, and an AI tool connects to it by signing in to Conductor or with a Conductor key. For read-only access, use https://mcp.conductor.is/read-only instead. If you’re building your own agent on Conductor’s MCP, or you’re an AI agent learning how it works, the MCP tools reference lists every tool and how each call behaves.

Setup

Most AI tools connect by signing in to Conductor in your browser, so there’s no key to copy. Your AI tool can run anywhere, but QuickBooks Desktop and the Web Connector must be running on the computer you connected to Conductor.
These steps work for claude.ai, Claude Desktop, and Cowork.
  1. In Claude, open Customize > Connectors, click Add, then click Add custom connector.
  2. Name it Conductor, paste the URL below, and click Continue.
  3. Leave Sign in now and Use Claude’s published identity selected, click Add, then click Connect.
  4. Sign in to Conductor, pick your project, and click Allow. This adds an “MCP (Claude)” key to your Conductor project’s API Keys page. If you ever need to revoke access, delete that key.
  5. In a Claude chat, turn on Conductor under + > Connectors. Claude reads without asking and asks before each tool that changes QuickBooks; choose Always allow to stop asking for that tool (in Cowork, Allow for all tasks).
On a Claude Team or Enterprise plan, an Owner adds the connector in Organization settings > Connectors instead, and members click Connect on it to sign in. The Owner should leave the write tools at Always allow under Tool permissions, or members can’t choose Always allow in step 5, so Claude asks them before every change. In Cowork, members must approve each task until the Owner turns on Organization settings > Cowork > Permissions > Allow “Always allow” for connector tools, which is off by default.If Claude Desktop still has a conductor entry in its local config from the conductor-node-mcp package, remove it; the connector replaces it. To connect Claude Desktop’s local config with a key instead, on Windows or macOS, follow the Other clients steps.

Read-only mode

Read-only mode lets the AI tool read your QuickBooks data and blocks creates, updates, and deletes before they reach QuickBooks. Use it for a trial, an accountant, or co-workers who should only read. The URL or header below limits the connection, not the Conductor key.
Follow the Claude steps in Setup, but name the connector Conductor read-only and paste the URL below. The Claude Free plan allows only one custom connector, so remove the full-access connector first if you added it.
The read-only connector’s key is named “MCP (Claude, read-only connection)” on your Conductor project’s API Keys page.
To test read-only mode, ask the agent to create a test customer in QuickBooks Desktop. If it can’t, read-only mode is on; if it can, the agent still has full access, so check the URL or header above.
Read-only mode is a guardrail, not a security boundary: anyone with the Conductor key can still write through the Conductor API. Give each person their own key, as signing in does, and revoke it when needed.
To limit an AI tool to certain QuickBooks company files, connect it to a Conductor project that has only those files’ QuickBooks Desktop connections. An AI tool can reach every company file connected to its project.

Verify it works

Ask the agent: “Show the 5 most recent invoices using my most recently successful QuickBooks Desktop connection.” If it returns real data, you are set up. A “connected” indicator proves only that the sign-in or key worked; QuickBooks Desktop is reached only when a tool runs. If your project has several company files, the AI tool usually asks which one you mean, or you can name the file in your question.

Timeouts and QuickBooks Desktop

Your AI tool reaches QuickBooks Desktop through the Web Connector on the computer that holds the company file, so QuickBooks Desktop and the Web Connector must be running there.
  • QuickBooks Desktop answers one request at a time for each company file. Calls to the same file wait their turn, so asking for several things at once doesn’t make them faster.
  • The first request after a pause can take 3 to 10 seconds, and up to 90 seconds when the Web Connector must open the company file.
  • When QuickBooks doesn’t answer in time (90 seconds, or 50 seconds through the conductor-node-mcp package except in Claude Code), the call fails with QBD_REQUEST_TIMEOUT. A change that timed out may still have been saved, so ask the AI tool to check before repeating it.
  • Codex waits up to 300 seconds for a tool by default (its docs page still says 60). If you use execute, or your Codex stops a call at 60 seconds, add tool_timeout_sec = 300 under [mcp_servers.conductor] in ~/.codex/config.toml.

Troubleshooting

This usually means the Conductor key behind the connector was deleted, and Claude doesn’t ask you to sign in again on its own. In Claude, open Customize > Connectors, disconnect Conductor, and click Connect on it again. Then sign in to Conductor, pick your project, and click Allow. If the error mentions QuickBooks Desktop or the Web Connector, signing in again won’t help; see “Requests to QuickBooks fail” below.
This means the URL you entered isn’t one of Conductor’s: https://mcp.conductor.is/ or https://mcp.conductor.is/read-only. Remove the connector in Claude or the plugin in ChatGPT, then add it again with the URL from the steps above.
This means the server URL is wrong: use https://mcp.conductor.is/mcp, or https://mcp.conductor.is/read-only for read-only access. If the message says “(HTTP 401)” instead, the connection’s key value isn’t Bearer sk_conductor_...: the word Bearer, one space, and your secret key, with no quotes and no Authorization: in front. Remove the tool, add it again with the Copilot Studio steps in Setup, and create a new connection.
This means the Conductor sign-in didn’t finish. Sign in with the email your company uses for Conductor (on the Conductor page that opens, click Use a different account), or ask a teammate to add you on the Members page, then connect again.
Claude asks before each tool that changes QuickBooks, such as create_invoice, until you choose Always allow for that tool; tools that only read don’t ask. On a Claude Team or Enterprise plan, members can’t choose Always allow for a tool an Owner set to Needs approval under Tool permissions. If Claude Desktop also has a conductor entry from the local conductor-node-mcp package, open Settings > Developer > Edit Config, remove that entry, then fully quit and reopen Claude Desktop.
MULTIPLE_COMPANY_FILES means your project has several connected company files and the AI tool didn’t say which; it usually lists them and asks you, or you can name the file in your question. COMPANY_FILE_NOT_FOUND means the AI tool named a company file that isn’t in the project your key belongs to; ask it to list your company files and use one of those. NO_COMPANY_FILE means no company file in the project has answered a request yet: finish connecting one in the Conductor Dashboard, then make sure QuickBooks Desktop and the Web Connector are running.
This means the answer was too long for one result, so records were dropped from the end. Ask for fewer records, a shorter date range, or narrower filters; for a report, shorten the period or filter it. When you need all of it, such as for a total, ask the AI tool to read every page or the whole report in one call with execute.
READ_ONLY_CONNECTION means the connection uses the read-only URL or header, which blocks changes. To make changes, add a second connection to https://mcp.conductor.is/ with the Setup steps, or remove the read-only header.
This means the AI tool started more calls at once than one Conductor key can run. QuickBooks Desktop answers one request at a time for each company file anyway, so more parallel calls would only wait. Wait a few seconds and try again, or ask the AI tool to make fewer calls at once. Co-workers who share one key share this limit; signing in gives each person their own key.
QBD_REQUEST_TIMEOUT means QuickBooks Desktop didn’t answer in time, often because it was opening the company file or busy with another request. Ask again; a change that timed out may already be saved, so ask the AI tool to check before repeating it.EXECUTE_TIMEOUT means execute code didn’t finish within about 5 minutes (50 seconds through the conductor-node-mcp package except in Claude Code): the job may be too big for one call, or QuickBooks Desktop may have been slow to answer a request. First ask the AI tool to check what the code saved, since a change it sent can be saved even after the error. Then ask it to run the code again if the code makes only a few requests, or to split the job across shorter calls if it works through many records.Codex waits up to 300 seconds for a tool by default (its docs page still says 60). If you use execute, or your Codex stops a call at 60 seconds, add tool_timeout_sec = 300 under [mcp_servers.conductor] in ~/.codex/config.toml (see the Codex CLI setup steps).
This means your AI tool isn’t sending a valid Conductor key. Create a new key on your project’s API Keys page in the Conductor Dashboard (for other clients, the MCP tab’s Create key and fill in config fills it into the config for you). Paste the new key or config into your AI tool, then restart it. If the local conductor-node-mcp package fails to start, install Node.js (LTS), then fully quit and reopen your tool.
Grok’s connectors on grok.com can’t connect to Conductor. Grok Bot in Cursor’s cloud agents works with a key from the Other clients setup above.
This usually means QuickBooks Desktop or the Web Connector isn’t running on the computer you connected to Conductor. Make sure both are running there. Connecting an AI tool doesn’t need any Web Connector changes.
Yes. A key works on any number of computers and AI tools, so co-workers can paste the same key. In any tool that signs in, each co-worker can instead sign in to Conductor with their own account, which creates a separate key for them; they must be members of your Conductor organization. Pricing is per QuickBooks company file, so you aren’t charged extra for more co-workers, keys, or AI tools connecting to the same company file.When someone leaves, remove them on the Members page in the Conductor Dashboard, then delete their keys named “MCP (…)” on the project’s API Keys page; the “Created by” column shows whose each key is. Removing a member doesn’t delete their keys.
This means you’re connected to the MCP server of an unrelated SEO company at conductor.com. Its tools include ai_brand_insights and keyword_insights, and it returns “couldn’t identify the caller” errors. Remove it and add https://mcp.conductor.is/ instead. Ours is at conductor.is, and its tools include list_invoices and run_summary_report.

Support

Email support@conductor.is with the AI tool you use, the address it connects to, when the problem happened, and the error text the tool returned. Current incidents are on status.conductor.is.