MCP Server for iceDQ Data Reliability Platform
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent β or use 1-click editor setup below.
We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag β we're steadily working through the catalog.
π‘ Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Connect your AI assistant to the iceDQ Data Reliability Platform
Website Β β’Β Documentation Β β’Β Support Β β’Β Privacy Policy
The iceDQ MCP Server lets you manage your entire data quality lifecycle through conversation with an AI assistant. Ask it to explore your data sources, create validation rules, run reconciliations, monitor executions, and analyze results β no UI switching required.
48 tools covering the full data quality lifecycle, grouped by what they do (see
manifest.json for the exact tool names and descriptions the assistant calls):
| Category | Tools | What you can do |
|---|---|---|
| Data Exploration | 8 | Browse workspaces, connections, databases, schemas, tables, and columns; verify a connection is reachable |
| Data Profiling & AI Suggestions | 3 | Pull real sample rows, get null/uniqueness/pattern stats per column, and get AI-suggested checks from that profile |
| Rule Creation | 6 | Create any of the five rule types β including AI-suggested join keys and column mappings before building a reconciliation rule |
| Rule Management | 3 | Search/filter existing rules, inspect full configuration, and update checks, source/target, or join keys |
| Workflows | 4 | Chain rules into a workflow and adjust membership later |
| Schedules & Automation | 6 | Set up one-time/daily/weekly schedules, add more jobs later, trigger on demand, review run history |
| Execution & Monitoring | 4 | Run a rule or workflow, poll it to completion, and pull per-activity results and history |
| Results & Exception Reporting | 2 | Get the specific failing rows and reasons, or a link to view the report in the iceDQ UI |
| Organization | 5 | Organize rules/workflows into folders and track the async move operations |
| Reusable Parameters | 3 | Define reusable thresholds/date ranges/reference values, including bulk-loading from CSV |
| Data Warehouse Analytics | 3 | Ask natural-language questions about DQ history via schema-validated structured queries (no raw SQL) |
(The 48th tool, get_guidance, isn't listed above β the assistant calls it internally before complex multi-step
operations; it's not something you ask for directly.)
Per the v1.0.0 release notes:
| Client | Support | Setup guide |
|---|---|---|
| Claude Desktop | β MCP Bundle | Step-by-step |
| VS Code + GitHub Copilot Chat | β MCP client | Step-by-step |
| VS Code + Claude Code | β MCP client | Step-by-step |
| Cursor | β MCP client | Step-by-step |
| Windows | β Tested | β |
| macOS | β Tested | β |
| Node.js | 18.x or higher | Only needed if you launch via npx β Claude Desktop's .mcpb path doesn't |
Recommended AI model: Claude Sonnet 4 or higher, for the most accurate rule creation and workflow understanding.
Every install method below needs the same values from your iceDQ instance. See the Credentials Guide for exactly where to find each one in the iceDQ UI, and the Authentication Guide for how the two auth modes differ.
| Value | Env var | Required for | Example |
|---|---|---|---|
| Base URL | ICEDQ_BASE_URL | Both modes | No default β always your own instance URL |
| Realm | ICEDQ_REALM | Both modes | icedq or iam.icedq |
| Client ID | ICEDQ_CLIENT_ID | Both modes | β |
| Client Secret | ICEDQ_CLIENT_SECRET | username_password only | β |
| Username | ICEDQ_USERNAME | username_password only | β |
| Password | ICEDQ_PASSWORD | username_password only | β |
| Tokens file path | TOKENS_PATH | access_token only | β |
| Organization ID | ICEDQ_ORG_ID | Both modes | org-icedq or org-iam.icedq |
Optional: VERIFY_SSL (default true; set "false" only for self-signed certs), REQUEST_TIMEOUT (default 60
seconds), DEBUG (default false).
Base URL has no default. Every organization runs its own iceDQ instance β the
https://app.icedq.netvalue used throughout this guide's examples is illustrative only, not a shared cloud endpoint. Always replace it with your own instance's URL.
If you're launching via
npx(every client below except Claude Desktop's packaged extension), also setNODE_OPTIONS=--use-system-cain theenvblock β this is in every official config example and avoids TLS errors on machines with a corporate root CA installed.
Jump to your client:
Each section below is a condensed quick-start. For the full walkthrough with screenshots and troubleshooting, follow the linked guide on docs.icedq.com.
π Full guide: Setup in Claude Desktop
Two paths β Path A (recommended) installs a packaged .mcpb extension with a settings form and stores your
password in your OS keychain; Path B hand-edits a config file and needs Node.js 18+.
Path A: Download the .mcpb from the Releases page, then
in Claude Desktop go to Settings β Extensions β Install Extension and select the file. Fill in the credentials
form that appears and click Save.
Path B: Edit claude_desktop_config.json (Windows: %APPDATA%\Claude\claude_desktop_config.json,
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json):
Fully quit and reopen Claude Desktop (closing the window isn't enough), then verify with List my iceDQ workspaces.
π Full guide: Setup in VS Code & Cursor
Requires Node.js 18+ and the GitHub Copilot Chat extension, installed and signed in.
Ctrl+Shift+P / Cmd+Shift+P) β MCP: Open user configuration β opens mcp.json.No reviews yet β be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/mcp-server-124)<a href="https://allmcps.com/mcp/mcp-server-124"><img src="https://allmcps.com/api/badge/mcp-server-124?style=directory" alt="MCP Server on AllMCPs" /></a>