CData QuickBooks MCP: SQL Access, Connect AI vs. Open-Source
CData's two ways to give AI SQL access to QuickBooks: an open-source, read-only JDBC server, or the commercial Connect AI platform, compared for IT teams.
On this page +
If your team standardizes AI access to business systems around SQL rather than app-specific tool calls, CData is probably already on your radar. It shows up twice in the QuickBooks MCP space, as two genuinely different products that are easy to conflate. One is a free, open-source, read-only server you run yourself. The other is a commercial cloud platform aimed at IT teams connecting QuickBooks alongside hundreds of other sources. This post covers what each one actually is, what it costs, and which fits an IT or data team’s evaluation.
Compared in this post:
- The open-source CData QuickBooks MCP server
- CData Connect AI (the commercial platform)
- How the two compare side by side
- Governing AI access across many data sources
What QuickBooks SQL access means for AI
Most QuickBooks MCP servers, Intuit’s official one included, expose QuickBooks as a set of entity-specific tools: get a customer, list invoices, create a bill. That model fits a developer building a specific integration, but it doesn’t fit a data team’s usual approach, which is standardizing access across many systems behind one query interface. CData’s answer to that is to expose QuickBooks as SQL-queryable tables instead: list the available tables, list a table’s columns, and run a SELECT query, the same shape a data team already uses for a database, a data warehouse, or any other source they connect.
The open-source CData QuickBooks MCP server
CDataSoftware/quickbooks-mcp-server-by-cdata is a Java MCP server that registers exactly three tools: list the available tables, list a table’s columns, and run a SQL SELECT query against QuickBooks data. It’s explicitly described as read-only. There’s no create, update, or delete tool in the server at all, and CData’s own documentation points teams to its commercial offering if they need write capability.
The shape of it, once connected:
-- Three tools total: list_tables(), list_columns(table), run_query(sql)
SELECT Name, Balance
FROM Customers
WHERE Balance > 1000
ORDER BY Balance DESCThe catch is licensing: the MCP server code is free and MIT-licensed, but it runs on top of CData’s QuickBooks JDBC driver, which you register for separately (a trial license to start, or a paid license for production use). So “free server” is accurate but incomplete; the driver underneath it isn’t automatically free.
Choose it when: you’re comfortable running a local Java process, want genuinely read-only access with no write surface at all, and can license the JDBC driver.
CData Connect AI
CData Connect AI is a different product: a commercial, cloud-hosted MCP platform CData describes as giving AI assistants and agents connectivity, semantic context, and access control across hundreds of enterprise systems, with QuickBooks being one of many possible sources rather than the sole focus. It’s built for IT and data teams that want one governed connection point for AI access across their whole stack, with identity-based security and OAuth/SSO integration, rather than per-application MCP servers to manage individually. Unlike the open-source server, this one writes: alongside query, insert, update, and delete are core operations, and CData’s own QuickBooks + ChatGPT example describes “bidirectional” access with identity passthrough, plus “Source Tools” that scope exactly which actions are allowed per connected system. That’s a materially different access model from the read-only server above, not just a hosted version of it.
Pricing: Standard is $99/month ($79/month billed annually), including one user and one data source; Growth is $199/month ($159/month billed annually), including access to more source tiers plus derived views; Business is custom, with pooled tool calls and enterprise features like SCIM and premium support. Additional users and data sources beyond each tier’s included amount are billed as add-ons.
Choose it when: QuickBooks is one source among several you’re standardizing AI access to, you want a managed platform rather than a server you run and patch yourself, and you may need governed write actions, not just queries.
Comparing the two
| Open-source MCP server | CData Connect AI | |
|---|---|---|
| Model | Local Java process, SQL-style tools | Cloud platform, managed MCP endpoint |
| Write access | No, read-only by design | Yes, governed insert/update/delete via IT-scoped Source and Custom Tools |
| Cost | Free server + licensed JDBC driver | $99/mo Standard ($79/mo annual) to $199/mo Growth ($159/mo annual) to custom Business |
| Best for | Teams comfortable running and licensing their own server | IT/data teams standardizing AI access across many sources |
| Scope | QuickBooks only, per install | QuickBooks plus hundreds of other connectors on one platform |
Figures current as of publish; re-verify against CData’s own pages before relying on them, as this category changes monthly.
Governing AI access across many data sources
The reason CData shows up on an IT/data team’s shortlist at all is governance, not just SQL syntax: a team connecting AI to ten systems doesn’t want ten different auth models, ten different tool surfaces, and ten different places to check who accessed what. The two CData options land in different places on that governance question, though. The open-source server sidesteps write governance entirely by having no write tools at all; it’s one install per system, with authentication and audit left to you. Connect AI centralizes auth and access control across multiple sources, and it’s designed for write actions to be part of that: scoped per source, per connected system, under IT control, rather than wide open.
If the actual requirement is that writing stays architecturally impossible, not just governed, that’s a different bar than Connect AI is built to clear; the open-source server meets it by having no write path, and so does a hosted layer like Kipper. See how Kipper’s QuickBooks MCP server is architected read-only with per-user permissions and every question logged, for comparison.
FAQ
What’s the difference between CData’s open-source QuickBooks MCP server and CData Connect AI?
They’re separate products, often confused because both come from CData. The open-source server is a free, read-only Java MCP server that exposes QuickBooks as SQL-queryable tables through three tools, but requires a separately licensed CData JDBC driver underneath. CData Connect AI is a commercial cloud platform: a managed, remote MCP endpoint for natural-language queries across QuickBooks and hundreds of other sources, aimed at IT and data teams standardizing AI access.
Is the CData QuickBooks MCP server free?
The server code itself is MIT-licensed and free. What isn’t free is the CData JDBC Driver for QuickBooks it depends on: you register for a trial or a paid license separately. So the honest answer is free server, licensed driver.
Is CData’s QuickBooks MCP server read-only?
Yes, by design. It exposes exactly three tools (list tables, list columns, run a SQL SELECT query), with no write, update, or delete tools at all. CData’s own documentation points to its commercial offering for read-write capability.
How much does CData Connect AI cost?
As of publish: Standard is $99/month ($79/month billed annually) with one user and one data source included; Growth is $199/month ($159/month billed annually) with access to more source tiers and derived views; Business is custom-priced with pooled tool calls and enterprise features. Additional users and data sources are billed as add-ons on top of each tier.
Why would an IT or data team want SQL access to QuickBooks instead of MCP tool calls?
Because SQL is how data teams already think about standardizing access across many systems: one query language and one governance model instead of learning each app’s tool-call API individually. CData’s pitch to this audience is exactly that: QuickBooks becomes one more SQL-queryable source alongside everything else they connect.
Can these CData options write to QuickBooks?
Only one of them. The open-source server cannot: it’s read-only by design, with no write tools registered at all. CData Connect AI can: it supports governed insert, update, and delete actions alongside queries, scoped per source through IT-defined Source Tools and Custom Tools. So the open-source server is the strictly read-only option; Connect AI is not.
Want the full picture across all QuickBooks MCP options? See QuickBooks MCP servers compared, or the ultimate QuickBooks MCP guide.
Want governed answers instead of SQL access? See Kipper’s QuickBooks MCP server.