# MotherDuck Documentation - Data Quality Tools > Monitor and maintain data quality in MotherDuck Generated: 2026-08-25 > 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. ## Included documentation Source: https://motherduck.com/docs/integrations/data-quality/index # Data Quality Tools > Monitor and maintain data quality in MotherDuck Ensure data quality and reliability in MotherDuck using these integrated tools. ## Included pages - [Great Expectations](https://motherduck.com/docs/integrations/data-quality/great-expectations): Great Expectations is a data quality management platform combining data quality and data governance. It integrates with MotherDuck for table monitoring as part of data quality and observability workflows. - [Monte Carlo](https://motherduck.com/docs/integrations/data-quality/monte-carlo): End-to-end data observability platform for monitoring data quality and reliability. It integrates with MotherDuck for table monitoring as part of data quality and observability workflows. - [Secoda](https://motherduck.com/docs/integrations/data-quality/secoda): Data discovery and documentation platform for managing data quality and governance. It integrates with MotherDuck for table monitoring as part of data quality and observability workflows. - [Soda](https://motherduck.com/docs/integrations/data-quality/soda): Data quality platform for monitoring and managing data quality in your pipelines. It integrates with MotherDuck for table monitoring as part of data quality and observability workflows. --- Source: https://motherduck.com/docs/integrations/data-quality/great-expectations # Great Expectations > Great Expectations is a data quality management platform combining data quality and data governance. It integrates with MotherDuck for table monitoring as part of data quality and observability workflows. ## How it works with MotherDuck 1. Create a connection or data source in Great Expectations for the MotherDuck database you want to monitor. 2. Provide a MotherDuck access token or supported connection string in the tool's secret manager. 3. Start with a narrow set of schemas or tables, then expand checks and monitoring after the connection is validated. ## Related content - [View the full process in the Great Expectations documentation](https://docs.greatexpectations.io/docs/guides/connecting_to_your_data/database/duckdb) - [MotherDuck authentication](/key-tasks/authenticating-and-connecting-to-motherduck/authenticating-to-motherduck) - [Connecting to MotherDuck](/key-tasks/authenticating-and-connecting-to-motherduck/connecting-to-motherduck) --- Source: https://motherduck.com/docs/integrations/data-quality/monte-carlo # Monte Carlo > End-to-end data observability platform for monitoring data quality and reliability. It integrates with MotherDuck for table monitoring as part of data quality and observability workflows. ## How it works with MotherDuck Monte Carlo connects to MotherDuck for data observability workflows, including custom SQL monitors over MotherDuck tables. ## Prerequisites - A Monte Carlo account with access to the MotherDuck integration. - A MotherDuck account and database access for the objects you want to monitor. - A MotherDuck service token that can run the monitor queries. ## Setup 1. In MotherDuck, create a service token for Monte Carlo. 2. In Monte Carlo, add MotherDuck as a data source. 3. Enter the MotherDuck connection details requested by Monte Carlo. 4. Validate the connection. 5. Create custom SQL monitors for the tables, freshness checks, or metrics you need to observe. ## Authentication and configuration - Use a dedicated token for Monte Carlo monitoring. - Grant access to the databases and schemas where monitor queries run. - Keep monitor queries scoped to the smallest useful result set. ## Important notes - Monte Carlo lists the MotherDuck integration as public preview in its documentation. Confirm current availability and support requirements with Monte Carlo before relying on it for production alerting. - Query complexity and result size affect monitor performance. ## Use cases - Monitor freshness or row-count expectations for MotherDuck tables. - Run custom SQL checks against curated analytics models. - Route MotherDuck data quality incidents into existing Monte Carlo notification workflows. ## Related content - [View the full Monte Carlo MotherDuck setup guide](https://docs.getmontecarlo.com/docs/motherduck) - [MotherDuck authentication](/key-tasks/authenticating-and-connecting-to-motherduck/authenticating-to-motherduck) - [Connecting to MotherDuck](/key-tasks/authenticating-and-connecting-to-motherduck/connecting-to-motherduck) --- Source: https://motherduck.com/docs/integrations/data-quality/secoda # Secoda > Data discovery and documentation platform for managing data quality and governance. It integrates with MotherDuck for table monitoring as part of data quality and observability workflows. ## How it works with MotherDuck Secoda connects to MotherDuck as a data warehouse integration for metadata extraction, catalog search, documentation, lineage, and governance workflows. ## Prerequisites - A Secoda workspace with permission to add integrations. - A MotherDuck service token. - Access to the MotherDuck databases and schemas Secoda should catalog. ## Setup 1. In MotherDuck, create or copy a service token. 2. In Secoda, open the **Integrations** tab. 3. Select **Add Integration**. 4. Search for and select **MotherDuck**. 5. Paste the MotherDuck service token. 6. Connect the integration and let Secoda extract metadata. ## Authentication and configuration - Use a dedicated service token for Secoda. - Limit the token to the data assets Secoda should discover and document. - Configure ownership, documentation, and governance rules in Secoda after the metadata sync completes. ## Important notes - Secoda's setup requires only the MotherDuck token from the MotherDuck side. - If assets do not appear after connecting, first verify the token and database access for the account that created it. ## Use cases - Catalog MotherDuck tables, views, schemas, and columns. - Generate and maintain table documentation in Secoda. - Add governance context, lineage, and quality monitoring around MotherDuck assets. ## Related content - [View the full Secoda MotherDuck setup guide](https://docs.secoda.co/integrations/data-warehouses/motherduck) - [MotherDuck authentication](/key-tasks/authenticating-and-connecting-to-motherduck/authenticating-to-motherduck) - [Connecting to MotherDuck](/key-tasks/authenticating-and-connecting-to-motherduck/connecting-to-motherduck) --- Source: https://motherduck.com/docs/integrations/data-quality/soda # Soda > Data quality platform for monitoring and managing data quality in your pipelines. It integrates with MotherDuck for table monitoring as part of data quality and observability workflows. ## How it works with MotherDuck Soda connects to MotherDuck through the `soda-duckdb` package and runs quality scans against a MotherDuck `md:` database connection. ## Prerequisites - Soda installed in the environment that will run scans. - The `soda-duckdb` package. - A MotherDuck access token and database path. ## Setup 1. Install the Soda DuckDB package: ```bash pip install soda-duckdb ``` 2. Add a MotherDuck data source to your Soda configuration: ```yaml data_source motherduck: type: duckdb database: "md:sample_data?motherduck_token=" read_only: true ``` 3. Test the connection: ```bash soda test-connection -d motherduck -c configuration.yml -V ``` ## Authentication and configuration - The MotherDuck token can be passed in the `md:` connection string shown in Soda's reference configuration. - Store the token through your deployment secret manager or CI secret store before rendering the Soda configuration. - Set `read_only: true` for scan-only workflows. ## Important notes - Some Soda users report using `path` instead of `database` successfully. If `database` does not work in your environment, test `path` with the same `md:` value. - Keep Soda checks focused on the tables and columns you need to monitor so scans remain predictable. ## Use cases - Run SodaCL data quality checks against MotherDuck tables. - Validate pipeline outputs after loading data into MotherDuck. - Add MotherDuck quality scans to CI or scheduled data checks. ## Related content - [View the full Soda MotherDuck setup guide](https://docs.soda.io/data-source-reference/connect-motherduck) - [MotherDuck authentication](/key-tasks/authenticating-and-connecting-to-motherduck/authenticating-to-motherduck) - [Connecting to MotherDuck](/key-tasks/authenticating-and-connecting-to-motherduck/connecting-to-motherduck) --- ## Docs feedback MotherDuck accepts optional user-submitted feedback about this page at `GET https://motherduck.com/docs/api/feedback/agent`. For agents and automated tools, feedback submission should be user-confirmed before sending. URL-encode query parameter values and send a GET request: ```text GET https://motherduck.com/docs/api/feedback/agent?page_path=%2Fintegrations%2Fdata-quality%2F&page_title=MotherDuck%20Documentation%20-%20Data%20Quality%20Tools&text= ``` Optionally append `&source=` such as `claude.ai` or `chatgpt`. `page_path` and `text` are required; `page_title` and `source` are optional. Responses: `200 {"feedback_id": ""}`, `400` for malformed query parameters, and `429` when rate-limited.