Claude CData Connect AI connectorWhat Claude can do in your CData Connect AI account.
The Claude CData Connect AI connector exposes 12 tools. 7 read your connected sources, from their structure to the rows themselves, 0 are documented as writing, and 5 are left undocumented. Below: what Claude queries, what stays unclear, and where the lists disagree.
Verified Trustpilot reviews · AI, automation & growth agency
What changes once Claude can reach CData Connect AI
CData Connect AI sits between Claude and the business systems you have already linked in your CData account, such as Salesforce, Snowflake or NetSuite; the publisher counts 350 sources it can reach. Instead of writing SQL or exporting spreadsheets, you ask Claude a question, and it explores those sources, then runs a read query to answer it.
Find where the data lives. A sales operations manager asks which connected systems hold customer records. Claude lists them with getCatalogs, then walks down through getSchemas and getTables until it reaches the right table.
Answer a question from live rows. Once it knows the columns, thanks to getColumns, Claude writes and runs a SELECT through queryData, for example open opportunities by region, and reads the result back to you.
Understand a stored procedure before anyone runs it. A finance analyst wants to know what a month-end procedure expects. getProcedures lists the procedures and getProcedureParameters shows the parameters each one takes.
What it will not do, as far as the sheet shows: no tool on it is documented as writing. queryData accepts SELECT statements only, according to CData, and five tools on the sheet have no description at all. Nothing runs by itself either: Claude queries only while it answers you. For a recurring sync between systems, an automation platform is the better fit; the Integrations hub lists those options, and the Claude agility-cms connector page covers a connector from another publisher.
Five words before you connect
The vocabulary around this connector, in one minute.
- Connector
- A link you set up once between Claude and an account you already own, so Claude can work in it while it answers you.
- Tool
- One named action the connector gives Claude. Claude picks the ones it needs on its own, and the directory lists each one by name.
- Authorization
- The CData sign-in screen where you hand Claude the access it will use afterwards. Granted once per person, and it can be taken back.
- Approval
- The confirmation Claude waits for before doing something that changes an account, shown in the conversation when it matters.
- MCP
- The shared standard connectors run on: it is what lets an assistant such as Claude talk to an outside service like CData.
Connect CData Connect AI to Claude in three steps
- 01
Find CData Connect AI in Claude
Open Claude's settings, go to Customize then Connectors, and look for CData Connect AI. On a Team or Enterprise workspace, an Owner or Primary Owner enables the connector first, then each member signs in on their own.
- 02
Launch the connection
Click Connect on its row, then sign in to CData in the window it opens. If the link breaks later, use Disconnect and connect again; that is the official way to repair it.
- 03
Read the authorization screen
Look at the CData authorization screen before accepting. It belongs to the service, not to Claude, and it decides what the access covers. You can also withdraw that access later from the CData side.
The 12 tools, split by what is known about them
CData Connect AI gives Claude 12 tools: 7 that read your account, 0 that change something in it, and 5 no official source describes.
Seven tools are described in CData's MCP documentation, and all of them read. The other five appear on the directory sheet with a name and nothing else. Names stay exactly as Claude shows them.
- 7 read
- 5 not documented
What Claude reads (7)
7 toolsSeven tools that explore your connected sources or query their rows without changing them.
getTables
Lists the tables available inside one catalog and schema of your connected sources, so Claude can see what data a given system actually holds before it asks for any rows.
getSchemas
Shows the schemas inside one catalog. In CData's terms, a schema groups the tables and stored procedures of a source, so this is the middle rung between a connection and its tables.
getProcedures
Returns the stored procedures available in a catalog and schema, meaning the blocks of SQL logic saved inside a source. Claude gets their names, not their results.
getProcedureParameters
Describes what one stored procedure expects: each parameter's name, data type and direction. Claude can then explain in plain words what you would have to supply.
getColumns
Lists the columns of one table, with their definitions, so Claude learns the structure before it builds a query and picks the right field names instead of guessing them.
getCatalogs
Gives the list of connections set up in your Connect AI account. Each connection acts as a catalog, the top level Claude starts from when it explores your data.
queryData
Runs a SQL query against your connected sources and brings the result back, in CSV format according to CData. This is the tool that turns a question into actual figures from your systems.
Undocumented (5)
5 toolsListed on the directory sheet, described by no official source. Nothing is known about whether they read or change anything.
getPrimaryKeys
The directory sheet names this tool, yet no official source describes it, CData's MCP page included. Nobody publishes what it does, and this page will not guess from its name.
getIndexes
Present on the sheet, absent from every official description: CData's documentation, dated September 2026, does not mention it. What it does is therefore not documented anywhere public.
getImportedKeys
Only its name is public. No official source documents this tool, neither the directory sheet nor CData's pages, so its behavior stays an open question here.
getExportedKeys
No source documents this one. It sits in the list of 12 on the sheet, while CData's own catalog of tools leaves it out entirely, which is part of the mismatch described in the limits section.
execData
Undocumented as well: the sheet lists it, CData's MCP page does not, and no other official text says what it does. The page leaves its effect blank rather than reading it into the name.
What Claude checks with you first
By default, Claude stops and asks before each action it takes on an account on someone's behalf, and the prompt appears in the conversation at that moment.
CData adds a finer layer: after connecting, you can open the connector's settings and mark each tool Always allow, Needs approval or Block, and Claude then asks according to those choices. On Team and Enterprise workspaces, owners decide whether members may let some actions through without a prompt, and they can cap a connector for the whole organization, for example reading open and writing shut. Claude also works with the rights of the person who connected, and CData itself points to granular permissions and audit trails on its side.
Which Claude plans include CData Connect AI
None of the 819 sheets in the official directory shows availability by plan. Connector by connector, that information is published nowhere.
The general rule is sourced: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner opens a connector before members can use it. For the live state of this one, check its sheet in the official directory. Note that only CData documents this connector; no Claude help page covers it.
Where this connector stops, and where sources disagree
A connector is not an automation. Claude calls these tools only while it answers you, so nothing fires when a record changes in one of your systems.
By default, the sheet only shows reading among its documented tools, and that is an observed floor, not a ceiling: an administrator can open actions no public sheet lists. CData also notes that Claude's setup process may change and points to Claude's own documentation. The partner badge in the directory is not a security audit, and Anthropic says on every sheet that it does not guarantee tools behave as announced.
Which tools does CData Connect AI actually give Claude?
- Claude directory sheet ↗2026-10-01Twelve tools, including getPrimaryKeys, getIndexes, getImportedKeys, getExportedKeys and execData, and none of the three writing tools named in CData's documentation.
- CData documentation, MCP page ↗2026-09-23Eleven tools, three of which insert or update data, under names that do not appear on the sheet; the five sheet-only tools are not mentioned.
What this page followsNeither list is marked out of date. The directory sheet is what Anthropic publishes for Claude; CData's page describes what its server can expose. Neither settles it for your account: after connecting, check the tool list Claude actually shows in the connector's settings.
Need help connecting CData Connect AI to Claude?
A person reads every message.