Connect CData Connect AI to Well
Materialise CData Connect AI table row, source, and query into your workspace, queryable in conversation and through agents.
What Well pulls from CData Connect AI
CData Connect AI feeds table row, source, query into Well as a source. The connection is read-only; disconnect at any time from your workspace settings to revoke CData Connect AI’s access.
| From CData Connect AI | In Well | Relation | |
|---|---|---|---|
| Table row | Indexed record | Becomes | |
| Source | Workspace context | Groups under | |
| Query | Audit entry | Captures as |
- Sync mode
- MCP hybrid
- Refresh
- live + reconciliation reads
- Direction
- CData Connect AI → Well
What Well does with your CData Connect AI connection
Connect
Connect CData Connect AI over OAuth (MCP DCR): Well registers a client through CData Connect AI's OAuth Dynamic Client Registration and you approve on CData Connect AI's side, so the password never reaches Well; Well holds only a scoped token it can refresh.
Sync
Well brings table row, source, and query in from CData Connect AI on live events backed by periodic reconciliation reads. The first sync backfills history in the background and the connection stays live after.
Enrich
Well resolves each CData Connect AI entity into indexed record, workspace context, and audit entry, assigns categories, and links every record to an audit trail across the rest of your connected tools.
Available
Your data from CData Connect AI lands in the workspace as indexed record, workspace context, and audit entry you can search, chart, and automate.
Questions CData Connect AI unlocks
Ask in plain language. Well answers from your connected CData Connect AI connection, resolved against the rest of your stack.
Ask anything about your CData Connect AI connection
Ask about your CData Connect AI connection…
Connect CData Connect AI in three steps
- 01
Authorise CData Connect AI via MCP
From Well's Connections panel, search for CData Connect AI and click Connect. Well discovers CData Connect AI's MCP OAuth metadata from its .well-known endpoint, registers a client via Dynamic Client Registration, and routes you through the authorize prompt on CData Connect AI's side. No client credentials to paste.
- AuthOAuth (MCP DCR)
- DiscoveryMCP .well-known
- MCP servermcp.cloud.cdata.com/mcp
- 02
Map your entities
Well's MCP client discovers table row, source, and query from CData Connect AI that CData Connect AI's MCP server exposes and brings them into your workspace using the canonical mappings defined in Well's data-views layer. You can inspect the workspace data model from Settings > Data Model.
- Mappingpreconfigured by Well
- 03
Use the data
Ask questions in conversation, build records tables, or let agents act on CData Connect AI records. Because CData Connect AI ships through MCP, Well treats every entity it exposes as queryable graph state alongside the rest of your connected tools.
- First syncstarts as soon as connect completes
MCP handshake typically completes under a minute on warm connections. Resource enumeration runs immediately after; full backfill of historical CData Connect AI records happens in the background.
How CData Connect AI stays secure with Well
Well connects to CData Connect AI's MCP server (mcp.cloud.cdata.com/mcp) via the Model Context Protocol. The MCP server itself handles credential issuance through OAuth Dynamic Client Registration; Well never sees a long-lived CData Connect AI secret. Tokens are scoped to the table row, source, and query CData Connect AI exposes and refreshed server-side. Reads only, Well cannot modify or delete CData Connect AI records.
- granted
Read CData Connect AI records
Resources the CData Connect AI MCP server exposes, scoped by your OAuth approval.
- granted
Resolve table row, source, and query across your stack
Match identifiers in CData Connect AI against the same entities your other connected tools expose, so each record carries cross-tool context.
- refused
Modify or delete CData Connect AI records
Not granted; CData Connect AI is read-only in Well. Write-back is opt-in per connector when a write surface exists.
- refused
Store CData Connect AI passwords or session cookies
Authentication runs through OAuth (MCP DCR) tokens we never see.
Frequently asked questions about CData Connect AI and Well
From Well, open Connections, find CData Connect AI, and click Connect. Well discovers the OAuth metadata at mcp.cloud.cdata.com/mcp/.well-known/oauth-authorization-server, registers a client on the fly via Dynamic Client Registration, and walks you through the authorize prompt on CData Connect AI's side. No client_id or client_secret to paste; the handshake takes roughly a minute.
Well brings in table row, source, and query from CData Connect AI and reshapes each entity into your workspace: table row becomes indexed record; source becomes workspace context. Every record arrives with the source identifier preserved, so CData Connect AI stays the source of truth while Well lets you query the data alongside the rest of your stack.
Well tracks the last sync watermark per table and only requests rows that changed since then, using whatever incremental marker CData Connect AI exposes (last_updated, sequence_id, or partition key). Backfills run in the background on first connect; subsequent reads stay cheap and the load on CData Connect AI's side stays bounded.
Well watches for updates to table rows and applies them on the next sync, preserving the original workspace identifier so anything downstream (records tables, conversation history, agent runs) keeps pointing at the right indexed record. Edits flow in incrementally; nothing is duplicated, and the CData Connect AI source identifier is retained on every revision.
Well combines live CData Connect AI events with periodic reconciliation reads of table row, source, and query. New rows appear within seconds when CData Connect AI pushes them; periodic reads catch anything a push missed. The first connect backfills history from CData Connect AI in the background.
Open Connections > CData Connect AI in Well and click Disconnect. Well calls CData Connect AI's token revocation endpoint and stops calling CData Connect AI immediately on its side; provider-side propagation to CData Connect AI's admin panel varies by provider. The table row, source, and query Well already synced stay in your workspace by default; ask Support to purge them if your compliance flow requires it.
CData Connect AI records are stored in the region Well operates for your workspace. Specific region details and the steps to change region are available from Support. See /privacy for the current data-handling policy.
Pairs well with CData Connect AI
More in Data
BigQuery
Connect BigQuery to Well to sync data pipelines and warehouse connections.
ClickHouse
Connect ClickHouse to Well to sync data pipelines and warehouse connections.
Coupler.io
Connect Coupler.io to Well to sync data pipelines and warehouse connections.
MotherDuck
Connect MotherDuck to Well to sync data pipelines and warehouse connections.
Popular cross-category
Ready to connect CData Connect AI?
Connect once. Every table row, source, query from CData Connect AI becomes searchable, queryable, and ready for your agents and tables. Disconnect any time.