Soda MCP

Use Soda from your preferred AI agent.

Soda MCP allows your team to fully manage your data from inside the AI agents your team already works in, such as Claude, Cursor, Codex, or GitHub Copilot.

soda-mcp is a Model Context Protocol (MCP) server for Soda Cloud. It lets MCP-capable AI clients use Soda Cloud's public API to inspect and manage data quality resources such as datasets, checks, contracts, scans, monitors, incidents, attributes, data sources, users, and user groups.

Reach for Soda MCP when you want an AI agent to help with data workflows, for example:

• List datasets and inspect their health status.
• Retrieve checks, contracts, scans, and incidents.
• Create or update contracts and monitors.
• Trigger discovery, contract verification, historical metric collection, or other supported Soda Cloud actions.
• Manage Soda Cloud resources such as attributes, roles, users, and user groups.
• Build complex workflows across your entire AI layer, connecting to other agents and MCPs

MCP vs. Soda AI

​Soda AI and Soda MCP both let you work with Soda Cloud through natural language, and they overlap on what they can do, but they suit different jobs.

• Soda MCP is the choice for automated, scheduled, parallel, and background workflows. Because it runs inside your own tooling you can build cron, parallelism, and completion notifications around it.
• Soda AI, on the other hand, is a conversational tool for one-off work, like drafting a contract, or asking what an incident means, while you're on the loop.

Workflow	Soda MCP	Soda AI
Scheduled runs	Wire MCP-driven tasks into a cron job or pipeline so they run unattended on a schedule.	Soda AI is designed to run only when you're in a session with it, in order to confirm actions.
Parallel work	MCP tasks can fan out across many datasets or datasources at once, driven by your own orchestration.	Soda AI works through one interactive flow and does not orchestrate tasks, it keeps you in the loop.
Background execution with notifications	A long-running MCP job can run in the background and ping you through whatever tooling you've wired up (Slack, email, your pipeline's own alerts) when it finishes.	Soda AI completes the API call but won't notify you when a background-style job is done.

In short: use Soda AI for interactive, human-in-the-loop work, and Soda MCP when you want the same kinds of actions to run on a schedule, in parallel, or in the background as part of an automated workflow.

---

{% if (visitor.claims.plan === 'datasetStandard') %}

You are logged in to Soda and seeing the Dataset Standard license documentation. Learn more about Documentation access & licensing.

{% if (visitor.claims.plan === 'enterprise') %}

You are logged in to Soda and seeing the Team license documentation. Learn more about Documentation access & licensing.

{% if (visitor.claims.plan === 'enterpriseUserBased') %}

You are logged in to Soda and seeing the Enterprise license documentation. Learn more about Documentation access & licensing.

{% if !(visitor.claims.plan === 'enterprise' || visitor.claims.plan === 'enterpriseUserBased' || visitor.claims.plan === 'datasetStandard') %}

You are not logged in to Soda and are viewing the default public documentation. Learn more about Documentation access & licensing.

If you do have a Soda license, make sure to log in to Soda Cloud in this same browser.