MotherDuck
Read and write support varies by record
Record types covered in the setup guide
| Record types | Coverage and requirements |
|---|---|
| See connector requirements. Confirm field permissions and sync direction. |
Data warehouse / Database · Two-way sync platform
MotherDuck and Supabase integration — two-way sync
Keep supported MotherDuck and Supabase records aligned with two-way sync. Give each team access to current data while controlling which system can update each field.
Set this up from Claude or ChatGPT- Field mappings and sync direction under your control
- Inspect and resolve record errors in one dashboard
Built for teams where self-serve, reliability and scale matter
Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Example workflow
Plan table mappings between MotherDuck and Supabase
Validate the selected objects and operations even where connector-level direction is documented.
Starting eventA selected source table needs an operational replica, a reporting projection, or a migration copy.
Choose actual tables in MotherDuck and Supabase and compare their schemas and record types.
Specify the primary/business key, type conversions, filter boundaries, relationship dependencies, and the source of each writable field.
Plan two-way sync around connector support and your update rules; use a source-to-destination copy for read-only records. Keep source views, aggregate outputs, and writable base tables distinct.
What to verifyCounts reconcile within identical filters; updates preserve keys; precision, nulls, deletes, and schema changes follow the agreed mapping rules.
Review records and field ownershipAI assistant
Set up MotherDuck and Supabase from Claude or ChatGPT
Connect the Stacksync MCP server to your AI assistant, then ask for the sync in plain language. You only sign in; there is no code to write and no API key to paste.
1. Add the Stacksync MCP server
Server URL
https://mcp.stacksync.com/mcp In Claude
- Open Customize → Connectors, select + Add, then Add custom connector.
- Name it Stacksync and enter https://mcp.stacksync.com/mcp.
- Select Connect, sign in to Stacksync and choose your workspace.
In ChatGPT
- Open Settings → Apps → Advanced settings and turn on Developer mode.
- Select Create app, name it Stacksync, enter https://mcp.stacksync.com/mcp and choose OAuth.
- Sign in to Stacksync, then enable Stacksync from the tools menu in a chat.
Set up Codex or Claude Code
Codex
codex mcp add stacksync --url https://mcp.stacksync.com/mcp
codex mcp login stacksyncComplete the browser sign-in with your Stacksync account, then start a new Codex session.
Claude Code
claude mcp add --transport http stacksync https://mcp.stacksync.com/mcpOpen Claude Code, run /mcp, select stacksync and complete the browser sign-in.
Then ask: “List my Stacksync workspaces.” Sign-in connects your assistant; it does not create a sync yet.
Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI and other assistants: setup steps in the docs.
2. Ask your assistant
Create a two-way sync between my MotherDuck and Supabase.
Also from the same chat
You can also ask for workflows and AI agents (Genies) that use MotherDuck and Supabase. The assistant checks what each app supports, for example:
- “Build a workflow that messages our team in Slack when a MotherDuck record changes.”
- “Create a Genie that answers questions about our Supabase data in Slack.”
What happens next
- Signs you in with your Stacksync login (OAuth). No API key is pasted into the chat.
- Gives you a secure sign-in link for each app it connects; you open it and sign in to that app.
- Builds the sync with your permissions in Stacksync, nothing more. Turn on Ask before every change in the MCP settings to approve each change first.
New to Stacksync? Create an account first, then sign in from your assistant.
Mapping essentials
Records and field ownership
Match records by stable IDs and assign an owner for each field. The record notes identify the coverage to check.
Download the mapping worksheetCSV · No email required
Choose the tables you need in MotherDuck and Supabase, then map their keys, field types, and filters. Your schemas determine how records relate and which system should own each field. Use the worksheet to document those choices before testing the first load.
Why teams connect MotherDuck and Supabase
Put your MotherDuck and Supabase data to work
Start with the work your team needs to complete: keep records up to date, make operational data available for reporting, or move data to a new system. Choose one MotherDuck and Supabase workflow to test, define what success looks like, and decide who handles failed updates.
Land CRM and operational database records in MotherDuck so a small team gets warehouse-style analytics without cluster management
Sync modeled MotherDuck tables outward to operational tools for activation
Sync application tables in Supabase with the CRM two-way so new signups appear as contacts and sales edits flow back to the app
Mirror billing and subscription records into Supabase tables the application can join directly
What records can you sync?
Start with the records your workflow needs. Check each system’s read and write requirements before mapping fields.
Supabase
Read and write support varies by record
Record types covered in the setup guide
| Record types | Coverage and requirements |
|---|---|
| See connector requirements. Confirm field permissions and sync direction. |
Connection essentials
Review how each system connects, detects changes, and permits access to your records.
View setup requirements and limits| Connection requirement | MotherDuck | Supabase |
|---|---|---|
| Integration interface | SQL through DuckDB clients and drivers using a MotherDuck (md:) connection | PostgreSQL connection through the Supabase IPv4-compatible Transaction Pooler |
| Authentication | Access token created in MotherDuck | Postgres database credentials entered in the secure Stacksync connection form |
| Change detection | The saved Stacksync guide does not specify the change-detection mechanism. | Postgres connector requirements apply. |
| Read access | Available for supported records | Available for supported records |
| Write access | Available for supported records | Available for supported records |
Enterprise controls
Security and control for your integrations
Explore security controlsCompliance and data transfers
As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.
- SOC 2 Type II
- ISO 27001
- HIPAA BAA
- GDPR
- CCPA
- DPF US-EU-UK-CH
SSO & SCIM
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Alerts
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Secure connection options
Securely connects to your systems with:
Record-level recovery
Inspect sync errors and use retry and revert controls to resolve failed updates.
Read the recovery guideImplementation
Technical reference
Review setup, record relationships, testing, and recovery for your implementation.
Authentication, permissions and API limits
Connection requirements and limits
MotherDuck
- Integration interface
- SQL through DuckDB clients and drivers using a MotherDuck (md:) connection
- Authentication
- Access token created in MotherDuck (Settings > General > Create Token), pasted into Stacksync; database name and schema configurable if not using defaults
- Change detection
- The saved Stacksync guide does not specify the change-detection mechanism. Confirm it for the selected objects.
- Read access
- Available for supported records
- Write access
- Available for supported records
Setup requirements
- Generate a MotherDuck access token in Settings > General and enter it in the Stacksync connection form.
- Specify the intended database and schema and confirm read/write coverage for the selected tables.
Limitations to check
- Two-way sync is documented at connector level. Confirm table eligibility, writable columns, and the change-detection interval during setup.
Technical documentation
Documentation reviewed 2026-09-15. Check the linked guides for current account and record requirements.
Supabase
- Integration interface
- PostgreSQL connection through the Supabase IPv4-compatible Transaction Pooler
- Authentication
- Postgres database credentials entered in the secure Stacksync connection form; use the Supabase IPv4-compatible Transaction Pooler connection string.
- Change detection
- Postgres connector requirements apply. If logical replication permissions are unavailable, the documented Postgres Heroku connector provides a trigger-based alternative, including for non-Heroku databases.
- Read access
- Available for supported records
- Write access
- Available for supported records
Setup requirements
- Connect the Supabase database through the Postgres connection flow using an IPv4-compatible Transaction Pooler connection string.
- Each synced table needs a single-column primary key with an automatically generated default.
- The database role needs table ownership and the documented read, write, trigger and logging-schema permissions. Confirm the appropriate Postgres connector before creating the sync.
Limitations to check
- IPv6 connections are not supported by Stacksync; select the IPv4-compatible Supabase pooler.
- This evidence covers Postgres tables. It does not establish support for Supabase Auth or Storage APIs, or write access to managed schemas.
- Verify the actual tables, fields and permissions in the connected workspace before enabling either direction.
Technical documentation
Documentation reviewed 2026-10-20. Check the linked guides for current account and record requirements.
Prepare MotherDuck and Supabase access
Set up both accounts before testing the mapping. Use test records where available, and identify the account administrator who can approve access and help resolve setup errors.
MotherDuck setup checklist
- Generate a MotherDuck access token in Settings > General and enter it in the Stacksync connection form.
- Specify the intended database and schema and confirm read/write coverage for the selected tables.
Supabase setup checklist
- Connect the Supabase database through the Postgres connection flow using an IPv4-compatible Transaction Pooler connection string.
- Each synced table needs a single-column primary key with an automatically generated default.
- The database role needs table ownership and the documented read, write, trigger and logging-schema permissions. Confirm the appropriate Postgres connector before creating the sync.
Setup guides: Authorize SupabasePostgres connectorRequired Postgres permissions
Prepare to go live
Record the fields each system can update, the first-load cutoff, both record IDs, the expected update delay, and who handles errors. Complete the tests before production before expanding to more records.
Use the MotherDuck and Supabase planning worksheet to capture these decisions. Record the access owner in the worksheet and enter credentials only in the connection setup.
Record identity and field ownership
Keep each record tied to its source ID. Use the references below to choose field owners and preserve relationships between records.
Download the mapping worksheet · CSV, no email required
Choose the tables you need in MotherDuck and Supabase, then map their keys, field types, and filters. Your schemas determine how records relate and which system should own each field. Use the worksheet to document those choices before testing the first load.
Compare integration approaches
Choose your tables and update rules before the integration method. A live application copy, a reporting table, and a one-time migration need different handling for updates, history, deletes, and reconciliation.
Stacksync managed sync
- Best fit
- Two-way sync for supported objects. Choose the records, writable fields, and permissions for your workflow.
- Operating responsibility
- Fits ongoing record synchronization when the required operations are supported. Add workflow steps for approvals or business actions that go beyond copying fields.
- Before you choose
- Provide your table or object schemas and one example update; confirm the supported keys, fields, and direction.
Native vendor integration
- Best fit
- A vendor-built integration may fit if it supports your MotherDuck and Supabase record types.
- Operating responsibility
- Can reduce setup for a supported workflow. You may need another method for records or business steps it does not cover.
- Before you choose
- First check whether either vendor offers this integration. If available, verify your record types, update direction, account tier, and related-record handling.
Custom API or workflow
- Best fit
- Consider when MotherDuck and Supabase need a transformation, approval, or action outside a direct record sync.
- Operating responsibility
- Provides control over business steps; the team owns credentials, version changes, error queues, and reconciliation.
- Before you choose
- Verify endpoint permissions, pagination, quotas, duplicate detection, and failure recovery.
File or scheduled snapshot
- Best fit
- Consider for a one-time MotherDuck / Supabase migration or a reporting need with an explicit freshness window.
- Operating responsibility
- Can simplify a bounded transfer; later changes and deletion history require another extraction or a separately designed incremental process.
- Before you choose
- Record the extraction cutoff, source IDs, encoding, date/number formats, and reconciliation totals.
Workflow scenarios and expected results
Plan table mappings between MotherDuck and Supabase
Validate the selected objects and operations even where connector-level direction is documented.
Starting event: A selected source table needs an operational replica, a reporting projection, or a migration copy.
- Choose actual tables in MotherDuck and Supabase and compare their schemas and record types.
- Specify the primary/business key, type conversions, filter boundaries, relationship dependencies, and the source of each writable field.
- Plan two-way sync around connector support and your update rules; use a source-to-destination copy for read-only records. Keep source views, aggregate outputs, and writable base tables distinct.
Expected result: Counts reconcile within identical filters; updates preserve keys; precision, nulls, deletes, and schema changes follow the agreed mapping rules.
If it fails: Compare current source state, key mapping, and destination constraints before retrying. Reconcile the backlog after any schema or permission change.
Initial load and acceptance testing
Keep both record IDs with the expected and actual result. Reconcile the same filters and time window in each system.
Direction and permissions
Test case
Check that each connected account can read and write the chosen objects. Exercise both directions with a test record before enabling production changes.
Expected result
Only an approved, supported direction and permitted fields are written.
Schema, keys, and reconciliation
Test case
Use an actual MotherDuck and Supabase table. Compare key uniqueness, nulls, decimal precision, timezone conversions, and counts within identical filters.
Expected result
The process meets its agreed freshness target and reconciliation has no unexplained differences.
Failed updates, retries and recovery
Start with the failed record and the destination error, then inspect the source value, field requirements, and access.
A record type or update is unavailable
Investigate
Check the MotherDuck and Supabase connector guides, account permissions, and any operations marked On Request.
Next action
Ask the integration team to confirm a supported way to handle that record. Verify whether it needs connector configuration or a separate workflow step.
Source and destination disagree after a retry
Investigate
Compare current source values, destination validation, identity mappings, and any side effects already completed.
Next action
Stacksync issue retry reads the current source state. Decide the intended state before retrying or reverting; reconcile downstream effects separately.
Read the Stacksync issues dashboard guide for retry and revert behavior.
Change detection and update delivery
How updates move between MotherDuck and Supabase
See how each system detects changes and which updates the other system can receive. Each direction has its own permissions and record requirements.
MotherDuck Supabase Timing depends on the connected systems
Detect changesThe saved Stacksync guide does not specify the change-detection mechanism. Confirm it for the selected objects.
Apply updatesSelected writable fields update in Supabase. Its permissions and validation rules still apply; rejected records can be inspected in the Issues dashboard.
Supabase MotherDuck Timing depends on the connected systems
Detect changesPostgres connector requirements apply. If logical replication permissions are unavailable, the documented Postgres Heroku connector provides a trigger-based alternative, including for non-Heroku databases.
Apply updatesSelected writable fields update in MotherDuck. Its permissions and validation rules still apply; rejected records can be inspected in the Issues dashboard.
Update timing and record limits
- Measure initial-load and ongoing-change latency separately. Source detection, selected objects, account limits, and destination validation determine the observed delay.
- Two-way sync is documented at connector level. Confirm table eligibility, writable columns, and the change-detection interval during setup.
FAQ
MotherDuck and Supabase integration FAQ
-
Stacksync connects MotherDuck and Supabase with two-way sync for supported records. Authorize the accounts, select the record types, and map compatible fields. Both connectors support reading and writing; object permissions determine the available fields. Use the Issues dashboard to inspect and resolve rejected updates.
-
Stacksync supports two-way sync between writable records in both systems. The chosen objects and fields must permit updates in both directions. Read-only fields can supply values but cannot receive updates. Stacksync can read database views; it does not write back to the view.
-
Prepare both accounts, the selected object schemas, stable source and destination IDs, and the expected outcome. Generate a MotherDuck access token in Settings > General and enter it in the Stacksync connection form. Connect the Supabase database through the Postgres connection flow using an IPv4-compatible Transaction Pooler connection string. Use the pair worksheet to record ownership and acceptance criteria.
-
Measure initial-load and ongoing-change latency separately. Source detection, selected objects, account limits, and destination validation determine the observed delay.
-
No. Stacksync documents that pre-existing duplicates are not merged automatically when two-way sync begins. Review the initial dataset and matching plan before enabling it; an empty destination can simplify the first load.
-
Start with one business entity and a stable record ID. Map a small set of editable fields with compatible types, test required values and relationships, then expand after the pilot passes.
-
Check the destination error, field constraints, permissions, and current source value. The Stacksync issues dashboard supports retry and revert; retry reads current source values, so verify the intended record state before acting.
-
Use the current Stacksync pricing page and confirm the supported implementation with the team. Scope the required objects, record volume, update frequency, initial load, and support needs when comparing a managed connector with native or custom development.
-
Choose the tables you need in MotherDuck and Supabase, then map their keys, field types, and filters. Your schemas determine how records relate and which system should own each field. Use the worksheet to document those choices before testing the first load.
-
Choose your tables and update rules before the integration method. A live application copy, a reporting table, and a one-time migration need different handling for updates, history, deletes, and reconciliation.
Integration directory
Related integrations
Review documented support, sync direction, and setup requirements on each pair page. Search all 483 integrations listed for MotherDuck and Supabase.
Popular · 5 of 483
-
MotherDuck and InfluxDB -
Supabase and Azure Synapse Analytics -
Supabase and ClickHouse -
Supabase and Cloudera Data Platform -
Supabase and Dremio
No integrations match .
Next step
See your workflow in Stacksync
Walk through your MotherDuck and Supabase records, field mappings, and requirements with an integration engineer.
