Connecting Claude & ChatGPT
Thunderduck exposes a remote MCP server, so an AI assistant can discover your catalogs and query them in plain language — under your credentials, with the same guards as any other client.
https://mcp.thunderduck.ai/mcpClaude
Settings → Connectors → Add custom connector, paste the URL, and sign in when prompted. Authentication is OAuth against your Thunderduck identity; the assistant never sees a password or a catalog credential.
ChatGPT
Add it as a connector with the same URL. The consent screen lists what the tools can do, which is why every tool declares whether it only reads, whether it can destroy data, and whether it reaches systems outside our control.
What the assistant can see
Only what a tool returns. For a query, that means the rows themselves — and once returned, they are handled by the assistant provider under their policy and may sit in your conversation history there. Two consequences worth planning for:
- Prefer aggregates to
SELECT *when the data is sensitive. - Issue read-only tokens unless you specifically want an assistant able to write.
Bundled skills
Four skills ship with the server so the assistant uses it well on the first try
rather than by trial and error: exploring data before writing SQL, estimating
before executing, the SQL rules, and how to read a refusal. They are packaged in
the repo under thunderduck-mcp/skills/.