How to connect QuickBooks Desktop to Microsoft Copilot Studio (MCP server setup)
Give a Microsoft Copilot Studio agent read and write access to QuickBooks Desktop or QuickBooks Enterprise by adding https://mcp.conductor.is/mcp as an MCP tool that sends a Conductor API key in an Authorization header, then testing it in the Test your agent panel.
To connect QuickBooks Desktop to Microsoft Copilot Studio, create an API key on the Conductor Dashboard's MCP tab, then add https://mcp.conductor.is/mcp as a Model Context Protocol (MCP) tool on your agent's Tools page, with the key sent as Bearer sk_conductor_... in an Authorization header. Conductor's MCP server lets a Copilot Studio agent read and write QuickBooks Desktop and QuickBooks Enterprise data.
You need a Conductor account and an agent with generative orchestration turned on. QuickBooks and the Web Connector must be running on the Windows computer connected to Conductor. Setup takes six steps.
Before you start
A Copilot Studio agent reaches a company file only after that file is connected to Conductor, so you need these first:
A Windows computer that runs QuickBooks Desktop and the QuickBooks Web Connector, with the company file connected to a Conductor project by opening Conductor's config file in the Web Connector.
A supported edition: QuickBooks Enterprise Solutions in any version or year, or QuickBooks Premier (Plus), QuickBooks Desktop Pro (Plus), or QuickBooks Accountant Desktop (Plus) 2018 or later. QuickBooks Desktop for Mac has no Web Connector and is not supported.
A Conductor account and project, which you create at dashboard.conductor.is.
A Copilot Studio agent that uses generative orchestration, which Microsoft requires for MCP. New agents use it by default. For an older agent, open its Settings page and, in the Generative AI section under Orchestration, select Yes for "Use generative AI orchestration for your agent's responses?".
In production, Conductor costs $49 per company file per month, with no platform fee and no monthly minimum. The free Trial tier includes 1 connection for testing and development.
Create a Conductor API key and add the server to Copilot Studio
Copilot Studio connects to Conductor through a Model Context Protocol tool on the agent's Tools page that sends a Conductor API key in the Authorization header. The company file must already be connected to the Conductor project you create the key in.
In the Conductor Dashboard, open your project's MCP tab, pick Copilot Studio, and click Create key and fill in config. The dashboard fills your key into the value for step 5. Conductor's MCP setup guide lists the same steps under its Copilot Studio tab.
In Copilot Studio, open your agent's Tools page, click Add a tool, then click Model Context Protocol. If Copilot Studio shows New tool first, click it, then Model Context Protocol. Copilot Studio opens Microsoft's MCP onboarding wizard.
Name it
Conductor, describe it asReads and writes QuickBooks Desktop data through Conductor, and paste the URL below as the server URL, keeping the/mcp. The agent's orchestrator reads that description to decide when to call the tool.Under Authentication, choose API key, set the type to Header, enter
Authorizationas the header name, and click Create. Leave the OAuth 2.0 options alone, because Copilot Studio's OAuth flow doesn't work with Conductor.In the Add tool dialog, open the Not connected dropdown and click Create new connection. Paste the value from the dashboard, shown below with a placeholder key, as the key value and click Create.
The value is the word
Bearer, one space, and your key, with no quotes and noAuthorization:in front.Click Add and configure (or Add to agent).
For a read-only connection, follow the same six steps, but in step 3 name the tool Conductor read-only, describe it as Reads QuickBooks Desktop data through Conductor, and paste this server URL, which has no /mcp on the end:
Copilot Studio sends only the Authorization header, so this URL is what makes the connection read-only.
Check that it works
To check that the Copilot Studio agent reaches the company file, open the Test your agent panel (select Test at the top of any page if the panel is hidden) and enter this prompt:
Show the 5 most recent invoices using my most recently successful QuickBooks Desktop connection.
A working setup answers with the five most recent invoices from the company file. A "connected" indicator on the tool proves only that the config worked, because Conductor checks the key on first use.
To check a read-only connection, ask the agent to create a test customer in QuickBooks. If it can't, read-only mode is on. If it can, the agent still has full access, so check the server URL.
What this does and does not do
Through Conductor, a Copilot Studio agent can read and write data in every company file connected to its Conductor project, in QuickBooks Enterprise of any year and in every other Windows edition of QuickBooks Desktop from 2018 or later.
Conductor does not connect to QuickBooks Online, which is a separate product. Intuit publishes its own QuickBooks Online MCP server for that.
Conductor supports QuickBooks hosted on Rightworks, with one limit: Rightworks stops all background programs when you disconnect, so the agent's requests need an active Rightworks remote desktop session with QuickBooks open. Conductor's Rightworks guide covers the Web Connector setup there.
Read-only mode blocks creates, updates, and deletes before they reach QuickBooks. Use the full-access URL https://mcp.conductor.is/mcp for an agent that enters or changes accounting data, and the read-only URL https://mcp.conductor.is/read-only for a trial, an accountant, or co-workers who should only read.
Connection | Server URL | Tool name | Use it for |
|---|---|---|---|
Full access |
|
| An agent that enters or changes accounting data |
Read-only |
|
| A trial, an accountant, or co-workers who should only read |
Read-only mode is a guardrail, not a security boundary: anyone with the Conductor key can still write through the Conductor API.
If a data policy in your environment regulates Power Platform connectors, it also governs the Conductor tool, because Copilot Studio reaches MCP servers through those connectors.
Limit or revoke the Copilot Studio agent's access
A Copilot Studio agent reaches every company file connected to the Conductor project its API key belongs to, so create the key in a project that holds only the connections the agent needs. To revoke the agent's access, delete its key on the project's API Keys page in the Conductor Dashboard.
A key works on any number of computers and AI tools, but give each person their own key so you can revoke one person at a time. When someone leaves, remove them on the Members page, then delete their keys on the project's API Keys page, where the "Created by" column shows whose each key is. Removing a member doesn't delete their keys. Pricing is per company file, so more keys or co-workers on the same company file cost nothing extra.
How this works
Model Context Protocol (MCP) is an open-source standard for connecting AI applications to outside tools and data. When a Copilot Studio agent connects to an MCP server, each tool the server publishes becomes available to the agent with the name, description, inputs, and outputs the server provides.
Conductor's hosted MCP server at https://mcp.conductor.is/ connects QuickBooks Desktop and QuickBooks Enterprise to Microsoft Copilot Studio. Copilot Studio calls exactly the server URL you entered, https://mcp.conductor.is/mcp or https://mcp.conductor.is/read-only, over Streamable HTTP, the MCP transport it supports, and sends the Conductor key in the Authorization header of every request.
The server publishes two tools. search_docs searches Conductor's API documentation. execute runs code the agent writes against Conductor's TypeScript SDK in an isolated sandbox with no web or filesystem access, and whatever that code returns or prints comes back to the agent. That code is what reads and writes QuickBooks records.
Conductor reaches the company file through the QuickBooks Web Connector, a Windows program that ships with every version of QuickBooks Desktop and runs on the computer that holds the file. You connected that computer once by opening Conductor's config file in the Web Connector and authenticating. Conductor forwards each request from the agent to the Web Connector, which hands it to QuickBooks, and the answer comes back the same way.
If it does not work
When the Conductor tool fails in Copilot Studio, match the message or symptom to a heading below. Each heading is an entry in Conductor's MCP troubleshooting guide.
Copilot Studio says the MCP server rejected the request
Copilot Studio shows that message when 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 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 six steps above, and create a new connection.
API key missing or invalid (if you pasted a key)
The "API key missing or invalid" error means the Copilot Studio connection isn't sending a valid Conductor key. Pick Copilot Studio on the project's MCP tab and click Create key and fill in config to create a new key, then remove the Conductor tool and add it again with steps 2 to 6, pasting the new value in step 5.
Requests to QuickBooks fail
Failed requests usually mean QuickBooks Desktop or the Web Connector isn't running on the computer you connected to Conductor. Make sure both are running there; on Rightworks, keep the remote desktop session connected. Connecting Copilot Studio needs no Web Connector changes.
I see SEO tools, not QuickBooks (wrong Conductor)
Tools named ai_brand_insights or keyword_insights mean the agent is connected to the MCP server of an unrelated SEO company at conductor.com, which returns "couldn't identify the caller" errors. Remove that tool and add https://mcp.conductor.is/mcp with the six steps above. The QuickBooks server at conductor.is has only the execute and search_docs tools.
Frequently asked questions
Does this work with QuickBooks Enterprise?
QuickBooks Enterprise works with Copilot Studio through Conductor in any version or year and in every edition: Accountant, Contractor, Manufacturing and Wholesale, Nonprofit, Professional Services, and Retail. Enterprise is a tier of QuickBooks Desktop that uses the same Web Connector, so the six steps do not change.
Does QuickBooks Desktop need to be open?
QuickBooks and the Web Connector must both be running on the Windows computer connected to Conductor whenever the agent sends a request. The Copilot Studio agent itself can run anywhere.
Can I give Copilot Studio read-only access?
Copilot Studio gets read-only access when you add the tool with https://mcp.conductor.is/read-only as its server URL. Conductor then blocks creates, updates, and deletes before they reach QuickBooks. Anyone holding the key can still write through the Conductor API, so give each person their own key.
Why does Copilot Studio use an API key instead of OAuth?
Copilot Studio's OAuth 2.0 options don't work with Conductor, so the connection authenticates with an API key instead. The tool sends that key as Bearer sk_conductor_... in the Authorization header.
What does it cost?
In production, Conductor charges $49 per month for each company file connection in use: one that Conductor has established and that an API call reached within the rolling past month. The free Trial tier covers 1 connection for testing and development. Connections to QuickBooks sample company files and trial installations are free.
Is Conductor SOC 2 certified?
Conductor is SOC 2 Type 2 certified for the Security Trust Service Criteria, audited by Insight Assurance. Requests are processed through a SOC 2 compliant backend hosted by AWS in the US West (Oregon) region.
Connect QuickBooks Desktop to other AI tools
Each of these AI tools has its own setup guide for the Conductor MCP server:
To compare Conductor with the other options, read QuickBooks Desktop MCP server options. For tasks an agent can take on once connected, read AI agent use cases for QuickBooks.
