Connect MotherDuck to Well

From Well, open Connections, find MotherDuck, and click Connect. Well discovers the OAuth metadata at api.motherduck.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 MotherDuck's side. No client_id or client_secret to paste; the handshake takes roughly a minute.

Well brings in table row, database, and query from MotherDuck and reshapes each entity into your workspace: table row becomes indexed record; database becomes workspace context. Every record arrives with the source identifier preserved, so MotherDuck stays the source of truth while Well lets you query the data alongside the rest of your stack.

On connect, Well reads MotherDuck's schema and proposes a column-to-entity mapping based on naming conventions and the workspace types Well already knows. You confirm or override the mapping once; subsequent syncs apply it. Column type changes in MotherDuck surface as a notice in your workspace settings.

Each MotherDuck table row is scored against the candidate indexed records in your workspace on identifier overlap, amount or quantity match, date proximity, and counterparty resolution. Matches above the auto-link confidence threshold flow through cleanly; below the threshold they queue for a one-click human review, with the most likely indexed record prefilled and the MotherDuck source attached.

Well combines live MotherDuck events with periodic reconciliation reads of table row, database, and query. New rows appear within seconds when MotherDuck pushes them; periodic reads catch anything a push missed. The first connect backfills history from MotherDuck in the background.

Open Connections > MotherDuck in Well and click Disconnect. Well calls MotherDuck's token revocation endpoint and stops calling MotherDuck immediately on its side; provider-side propagation to MotherDuck's admin panel varies by provider. The table row, database, and query Well already synced stay in your workspace by default; ask Support to purge them if your compliance flow requires it.

MotherDuck 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.