MotherDuck documents a remote Model Context Protocol server at motherduck.com/docs/sql-reference/mcp hosted at `https://api.motherduck.com/mcp` with OAuth (or Bearer token) and read-write SQL access to MotherDuck cloud databases. Tools include `list_databases`, `list_tables`, `list_columns`, `search_catalog`, `query`, `query_rw`, `ask_docs_question`, Dive tools (`list_dives`, `read_dive`, `view_dive`, `save_dive`, etc.), and Flight scheduling tools (`list_flights`, `create_flight`, `run_flight`, etc.) per MotherDuck MCP docs. For local DuckDB files or custom configs, MotherDuck points to the open-source `mcp-server-motherduck` package (`uvx mcp-server-motherduck --db-path md:`) on github.com/motherduckdb/mcp-server-motherduck.
Use cases
- Let Cursor agents explore MotherDuck schemas and run analytical SQL
- Build Dives (interactive visualizations) from natural-language data questions
- Schedule and monitor Flights (Python jobs) on MotherDuck compute via MCP
- Query local DuckDB files with uvx mcp-server-motherduck for air-gapped analytics
- Attach shares and search catalogs without leaving the MCP client
Key features
- Cursor
- Claude Desktop
- Claude Code
- ChatGPT
- VS Code
Frequently Asked Questions
- Remote vs local MCP?
- MotherDuck recommends the hosted remote server for most cloud users; local mcp-server-motherduck is for DuckDB files and custom setups.
- Is write access available?
- Yes—the remote server exposes both read-only `query` and read-write `query_rw` tools; docs describe restricting to read-only when needed.
- Where does data process?
- MotherDuck docs note data is processed in your organization's region but results transit through the remote MCP server—use local MCP for strict residency.
Related
Related
3 Indexed items
MotherDuck MCP Server
MotherDuck documents a remote Model Context Protocol server at `https://api.motherduck.com/mcp` (fully managed, read-write) that lets Claude, ChatGPT, Cursor, Claude Code, Codex, and other MCP clients query MotherDuck cloud databases via OAuth or Bearer tokens with zero local install per motherduck.com/docs/sql-reference/mcp. Remote tools include read-only `query` and read-write `query_rw` plus schema exploration helpers documented in the MCP workflows guide. For local DuckDB files, S3 paths, or custom limits, the open-source `mcp-server-motherduck` package (motherduckdb/mcp-server-motherduck on GitHub, PyPI `mcp-server-motherduck`) runs via `uvx` with flags such as `--db-path`, `--motherduck-token`, and `--read-write` for self-hosted stdio or HTTP transports.
PlanetScale MCP Server
PlanetScale documents a hosted Model Context Protocol server at planetscale.com/docs/connect/mcp, reachable at `https://mcp.pscale.dev/mcp/planetscale` with OAuth authentication for organizations, databases, branches, schemas, and Insights data. An insights-only endpoint at `https://mcp.pscale.dev/mcp/planetscale-insights-only` omits read/write query tools. Tools documented include organization/database/branch listing, schema inspection, `planetscale_get_insights`, documentation search, and—when scopes allow—`planetscale_execute_read_query` and `planetscale_execute_write_query` with replica routing, ephemeral credentials, and destructive-query safeguards per the January 2026 changelog. PlanetScale notes the older local CLI MCP path is deprecated in favor of the hosted HTTP server for Cursor, Claude Code, and other MCP clients.
PostHog MCP Server
PostHog documents a free hosted Model Context Protocol endpoint at `https://mcp.posthog.com/mcp` per posthog.com/docs/model-context-protocol that lets MCP clients query analytics, manage feature flags, investigate errors, run HogQL, triage support workflows, and configure CDP destinations from natural-language prompts. The PostHog Wizard installs the server into Cursor, Claude Code, Claude Desktop, Codex, VS Code, Windsurf, and Zed via `npx @posthog/wizard@latest mcp add`. Authentication routes to the correct US or EU data region; manual setups can pass a personal API key with the MCP Server preset through `mcp-remote` and an `Authorization` Bearer header. Source lives in the PostHog monorepo at `services/mcp` (the standalone PostHog/mcp repository redirects there).