MotherDuck MCP connector
The MotherDuck connector lets Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent query your MotherDuck databases, browse tables and shares, and work with dives and flights, with every query running inside the signed-in person's own access.
- Connects over OAuth
- Free 14-day trial
- No credit card
Which tables in the sales database were updated this week?
Working in MotherDuck with Elaichi
-
List databases
-
List shares
-
List tables
How to connect MotherDuck to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
MotherDuck MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
MotherDuck MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
MotherDuck MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web. The plugin directory lives at chatgpt.com/plugins.
MotherDuck MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
MotherDuck MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
Connect MotherDuck to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
What teams do with MotherDuck through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in MotherDuck is logged.
-
Analytics
Answer a metrics question without writing SQL
Ask for last quarter's revenue by region and the agent finds the right table in MotherDuck, runs the query and explains the result in plain language.
-
Finance
Check month-end numbers against the warehouse
Pull totals from the billing and orders tables in MotherDuck and compare them with the close spreadsheet before anyone signs off.
-
Sales
Pull pipeline figures from the sales database
Get open pipeline by owner and stage straight from MotherDuck ahead of the Monday forecast call, without waiting on a data request.
-
Marketing
Measure a campaign from the events tables
Ask how many signups came from last week's campaign and the agent queries the events and attribution tables in MotherDuck for you.
-
Data
Find the right table before building anything
Search the MotherDuck catalog for a column or view, see what each one holds, and ask the docs how a feature works instead of guessing.
-
Operations
Save a recurring check as a dive
Turn a weekly inventory or SLA query into a saved dive in MotherDuck, update it as the question changes, and share the results with the team.
Try asking
- “Which tables in the sales database were updated this week?”
- “Show me last month's revenue by region from the orders table.”
- “Save this churn analysis as a dive and share it with Finance.”
What connecting MotherDuck gets you
6 screens from Elaichi, each doing one job for your MotherDuck account.
Ask Elaichi to work across your apps.
Which tables in the sales database were updated this week?
Show me last month's revenue by region from the orders table.
Save this churn analysis as a dive and share it with Finance.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask MotherDuck questions in plain language.
Get answers from live tables, views and shares without writing a line of SQL.
Copy the endpoint
AI apps
One governed endpoint reaches MotherDuck from every client.
Claude, ChatGPT, Cursor and Microsoft Copilot connect over OAuth, with no SDK and no shared API key.
Tool catalog
39 MotherDuck tools, ready with no connector code.
Databases, tables, columns, views, macros, dives and flights, covered the moment you connect.
Toolboxes
Every team gets its own MotherDuck toolbox.
Scope what Finance, Sales and Data can reach, each from one shared endpoint.
Shared connections
Teammates query MotherDuck without ever seeing a credential.
One person connects an account and shares it; nobody else handles a credential.
Audit log
Every MotherDuck query is logged with a name.
See when, who, what happened, type and resource for every call, in an append-only log.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.
MotherDuck digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch databases
MotherDuck
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
MotherDuck
Queued
Workflows
Schedules turn MotherDuck tables into approved digests.
Records are fetched, grouped and drafted, a person approves, then it posts back to MotherDuck.
MotherDuck health
Refreshed 4 minutes ago · every 15 minutes · from the databases collection
Databases
1,284 ↓ 12%
Tables
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Databases created
Last 14 days
By team
Share of activity
Data platform 34%
Analytics 27%
Finance 21%
Sales ops 18%
Collections and dashboards
MotherDuck health numbers arrive before anyone asks.
Four metrics and a 14 day chart, computed on a schedule with no model involved.
Why connect MotherDuck's MCP server through Elaichi
MotherDuck builds and runs this MCP server. Elaichi sits in front of it, so MotherDuck's tools follow the same sign-in, access rules and audit log as every other connector your organization uses. Calls an AI client makes to MotherDuck's server directly, outside Elaichi, get none of this.
-
One address for every AI client
Claude, ChatGPT, Cursor and Microsoft Copilot reach MotherDuck's tools at the same Elaichi address as every other connected app. Nobody adds MotherDuck's server to each client one by one.
-
Each person signs in as themselves
Each person signs in to Elaichi as themselves. Members connect with their own MotherDuck sign-in, and a connection someone shares runs on its owner's account. The credential stays in Elaichi's separate credential service, and the AI client holds only its Elaichi sign-in.
-
Rules checked before a call leaves
Restrictions on a role or a person, for the whole connector or a single tool, are checked before a call reaches MotherDuck's server. By default, a tool MotherDuck does not mark read-only or non-destructive counts as destructive, and over MCP it still runs under the "Use your connected apps" consent.
-
One audit log for every app
Each call that runs is recorded with the person, the tool, the connection and the AI client that made it, in the same audit log as every other app.
-
Tool issues go to MotherDuck
MotherDuck builds and runs these tools, and Elaichi staff do not curate them, so a report about how a tool behaves goes to the MotherDuck team.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for MotherDuck
All three can connect MotherDuck to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over MotherDuck tools | Allow or restrict single MotherDuck tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per MotherDuck call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
MotherDuck tools for your AI agents
39 tools are ready to call through Elaichi's MCP endpoint the moment you connect MotherDuck, governed by the same roles, restrictions, and audit log as everything else in Elaichi. MotherDuck builds and runs these tools.
No tools match your search.
Questions, answered
How do I connect MotherDuck to Claude?
Connect MotherDuck in Elaichi first; it signs in over OAuth, so you approve access in your MotherDuck account and there is no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the endpoint. Claude signs you in through Elaichi and MotherDuck is ready to query.
Does MotherDuck work with ChatGPT and Cursor as well as Claude?
Yes. Once MotherDuck is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. You connect MotherDuck once and every client picks it up.
What can an AI agent actually do with my MotherDuck data?
An agent can browse your MotherDuck databases, shares, tables, views and macros, search the catalog for the right column, run queries and explain the answers, and, where allowed, write results back. It can also save, update and share dives, create and update flights, and look up the MotherDuck docs when it is unsure. Short, concrete asks such as "revenue by region last month" work better than long paragraphs.
Can I stop an agent from deleting or changing things in MotherDuck?
Yes. In Elaichi you restrict actions one by one, so you can allow reading from MotherDuck tables while restricting writes, dive deletion or flight changes. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor or Microsoft Copilot cannot run it, whatever the prompt says.
What happens to a MotherDuck connection when someone leaves?
Offboarding a person in Elaichi ends their access to MotherDuck through every client at once. If they had shared a MotherDuck connection with a team, it keeps working for everyone else. Disconnecting MotherDuck once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client together.
Does the MotherDuck MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. MotherDuck is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for MotherDuck?
Yes. Both let Claude, ChatGPT or Cursor use MotherDuck. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every MotherDuck call.
How is Elaichi different from Composio for MotherDuck?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to MotherDuck: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put MotherDuck in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot