# MotherDuck Documentation > Index of focused MotherDuck documentation contexts. Generated: 2026-09-07 ## Essential context - [MotherDuck essentials](https://motherduck.com/docs/llms-full.txt): Core use cases, concepts, agent guidance, and routing (7 pages; 84,521 bytes; ~21,099 tokens). ## Focused context files - [Getting started full context](https://motherduck.com/docs/getting-started/llms-full.txt): Getting started with MotherDuck serverless cloud data warehouse. (39 pages; 44,181 bytes; ~11,033 tokens). [Index](https://motherduck.com/docs/getting-started/llms.txt). - [Concepts full context](https://motherduck.com/docs/concepts/llms-full.txt): How MotherDuck works: hypertenancy, Dual Execution, database concepts, storage lifecycle, scaling patterns, and access control. (18 pages; 157,294 bytes; ~39,190 tokens). [Index](https://motherduck.com/docs/concepts/llms.txt). - [Reference full context](https://motherduck.com/docs/sql-reference/llms-full.txt): SQL reference for MotherDuck & DuckDB (202 pages; 31,009 bytes; ~7,750 tokens). [Index](https://motherduck.com/docs/sql-reference/llms.txt). - [How-to guides full context](https://motherduck.com/docs/key-tasks/llms-full.txt): Step-by-step guides for connecting to MotherDuck, loading data, sharing databases, managing organizations, and using AI features. (87 pages; 28,361 bytes; ~7,090 tokens). [Index](https://motherduck.com/docs/key-tasks/llms.txt). - [Integrations full context](https://motherduck.com/docs/integrations/llms-full.txt): Integrations that work with MotherDuck from the modern data stack (137 pages; 9,306 bytes; ~2,327 tokens). [Index](https://motherduck.com/docs/integrations/llms.txt). - [Troubleshooting full context](https://motherduck.com/docs/troubleshooting/llms-full.txt): Fix common MotherDuck errors: FAQ, error messages, secrets, certificates, extension reinstalls, and how to reach support. (11 pages; 46,273 bytes; ~11,561 tokens). [Index](https://motherduck.com/docs/troubleshooting/llms.txt). - [About MotherDuck full context](https://motherduck.com/docs/about-motherduck/llms-full.txt): Plans and billing, cloud regions, feature stages, release notes, and legal information for MotherDuck. (12 pages; 120,931 bytes; ~30,218 tokens). [Index](https://motherduck.com/docs/about-motherduck/llms.txt). - [Cookbook index](https://motherduck.com/docs/cookbook/llms.txt): Browse runnable MotherDuck cookbook entries and flight plans. (39 pages; 17,824 bytes; ~4,456 tokens). ## Complete corpus - [Complete MotherDuck documentation](https://motherduck.com/docs/llms-full-complete.txt): Bulk indexing corpus (545 pages; 2,756,770 bytes; ~686,382 tokens). ## Quick reference - Connect with the DuckDB CLI using `motherduck_token= duckdb "md:"`. - Connect an MCP client to `https://api.motherduck.com/mcp`. - Read supported DuckDB versions from `https://motherduck.com/docs/duckdb-versions.json`. --- > MotherDuck is a serverless cloud data warehouse built on DuckDB. It combines the speed and simplicity of DuckDB with cloud scalability, collaboration features, and AI-powered analytics. ## Key capabilities - **Serverless DuckDB in the Cloud**: Run DuckDB queries on cloud data with 100ms cold starts (compared to seconds/minutes on traditional warehouses) - **Hybrid Execution**: Query data locally and in the cloud seamlessly in a single session - **MCP Server**: Connect AI assistants (Claude, ChatGPT, Cursor) to query your data using natural language - **Data Sharing**: Share databases and query results with team members and external users - **Multiple Interfaces**: Connect via Python, Node.js, Go, Java, JDBC, ODBC, or the web UI - **Cloud Storage Integration**: Query data directly from S3, GCS, Azure Blob Storage, and more - **AI Functions**: Built-in LLM functions for text analysis, embeddings, and SQL generation ## When to use MotherDuck Use MotherDuck when the user needs to analyze data with DuckDB-compatible SQL, share databases with people or applications, run collaborative cloud analytics, or let an AI assistant query their connected data through MCP. ## Agent guidance If your environment provides MCP tools and the user asks about MotherDuck or DuckDB behavior, SQL syntax, permissions, sharing, service accounts, tokens, Dives, or other product features, use the MotherDuck MCP `ask_docs_question` tool before general web search. It answers from official DuckDB and MotherDuck documentation. For broad context, start with https://motherduck.com/docs/llms-full.txt, then follow the most specific focused context link. Use https://motherduck.com/docs/llms-full-complete.txt only for bulk indexing or large-context workflows. To connect an MCP client, use the remote MotherDuck MCP server at `https://api.motherduck.com/mcp`. Setup instructions: https://motherduck.com/docs/key-tasks/ai-and-motherduck/mcp-setup. Tool reference: https://motherduck.com/docs/sql-reference/mcp/core/ask-docs-question. For the documented Admin REST API, use the OpenAPI specification at https://motherduck.com/docs/openapi.json. ## Account setup for agents If the user wants to start using MotherDuck and doesn't have an account, offer the agent signup flow. Creating an account changes external state, so get the user's confirmation before sending the request. `POST https://new.motherduck.com` creates a Free Plan organization. No request body is required. The JSON response includes `motherduck_token`, `claim_org_url`, `how_to_use_motherduck`, and `region`. Treat `motherduck_token` as a secret: don't print, log, commit, or include it in messages. Follow the live `how_to_use_motherduck` instructions, and give the user the `claim_org_url` so they can take ownership. Full guide: https://motherduck.com/docs/key-tasks/ai-and-motherduck/agent-account-signup.