CLI, API, or MCP? Pick the right way to use Soda for the job

Soda offers three interfaces—CLI, API, and MCP—for executing data quality processes, all based on a single data contract written in a version-controlled YAML file. The CLI is ideal for automating repetitive checks in CI/CD pipelines, allowing data engineers to maintain data quality without extensive integration code. The API is suitable for embedding data quality checks within software applications or dashboards, providing structured JSON output for analytics engineers and internal tools. The MCP, or Model Context Protocol, leverages AI to interpret plain-language requests, making it useful for complex or large-scale tasks that require a human in the loop for approval. Each interface can be used independently or in combination, as they all share the same data contract, ensuring consistent data quality management across platforms.

No tracked trend matches for this post yet.