Icedq Tools MCP

iceDQ MCP Server

Connect your AI assistant to the iceDQ Data Reliability Platform

Website • Documentation • Support • Privacy Policy

How It Works?

The iceDQ MCP Server connects Claude Desktop, VS Code, Cursor, and Claude Code to your iceDQ Data Reliability Platform instance, letting you manage data quality using natural language. Ask your AI assistant to explore databases, files, or REST APIs; profile data; and create Validation, Duplicate, Checksum, Pushdown, and Reconciliation rules (including API Validation and API Recon) — then execute, monitor, and analyze results, all through conversation.

Rules created through MCP tools are published immediately and ready to execute. The server also bundles eight agent skills (skills/) that guide authoring, comparison, API testing, runs, and schedules. Parameter names and schemas are listed in TOOLS.md.

49 tools covering the full data quality lifecycle:

System Requirements

Linux users: Install via the npx method (works in VS Code and Cursor). The packaged Claude Desktop extension (.mcpb) is currently macOS and Windows only because Claude Desktop itself does not ship a Linux build.

Quick Start

Step 1 — Get Your iceDQ Credentials

You need six values from your iceDQ instance before you can configure the MCP server:

• iceDQ Base URL
• Realm (default iam.icedq)
• Client ID and Client Secret (created in iceDQ → Administration → Security → Client Credentials)
• Your iceDQ username and password
• Organization ID (read from any rule's metadata)

For step-by-step instructions with screenshots, see the Credentials Guide.

Step 2 — Install via npm

The iceDQ MCP Server is published on npm as [`@icedq/mcp-server`](https://www.npmjs.com/package/@icedq/mcp-server). Most AI clients can launch it automatically with npx — no manual download or build step required.

Add the following to your AI client's MCP configuration:

{

"mcpServers": { "icedq": { "command": "npx", "args": ["-y", "@icedq/mcp-server"], "env": { "ICEDQ_BASE_URL": "https://app.icedq.net", "ICEDQ_REALM": "iam.icedq", "ICEDQ_CLIENT_ID": " ", "ICEDQ_CLIENT_SECRET": " ", "AUTH_TYPE": "username_password", "ICEDQ_USERNAME": " ", "ICEDQ_PASSWORD": " ", "ICEDQ_ORG_ID": " ", "NODE_OPTIONS": "--use-system-ca" } } } }

Configuration Reference

Claude Desktop users can install the packaged extension instead of editing JSON — follow the setup guide below.

Alternative: Device Flow Authentication (no password required)

Instead of supplying a username and password, you can authenticate via Device Flow (RFC 8628) — the server opens a browser login page for you, and tokens are cached securely in your OS keychain (Windows Credential Manager, macOS Keychain, or Linux libsecret) so you only log in once. This is the recommended option for SSO/MFA-enabled accounts or shared machines where you don't want credentials stored in the MCP config.

{

"mcpServers": { "icedq": { "command": "npx", "args": ["-y", "@icedq/mcp-server"], "env": { "ICEDQ_BASE_URL": "https://app.icedq.net", "ICEDQ_REALM": "iam.icedq", "ICEDQ_CLIENT_ID": " ", "AUTH_TYPE": "device_flow", "ICEDQ_ORG_ID": " ", "NODE_OPTIONS": "--use-system-ca" } } } }

On first run, the server prints a verification URL and code to the console and opens your browser automatically. Once you log in, tokens are cached (OS keychain, falling back to a token file) and silently refreshed on subsequent runs — no need to re-authenticate. Set REMEMBER_ME=false to skip the cache and force a fresh login every time. See the Device Flow internals guide for details.

Alternative: Access Token Authentication (pre-issued tokens)

If you already have an OAuth access/refresh token pair (e.g. issued by your own automation or a prior login), point the server at a token JSON file instead of supplying credentials directly:

{

"mcpServers": { "icedq": { "command": "npx", "args": ["-y", "@icedq/mcp-server"], "env": { "ICEDQ_BASE_URL": "https://app.icedq.net", "ICEDQ_REALM": "iam.icedq", "ICEDQ_CLIENT_ID": " ", "AUTH_TYPE": "access_token", "TOKENS_PATH": "/path/to/tokens.json", "ICEDQ_ORG_ID": " ", "NODE_OPTIONS": "--use-system-ca" } } } }

TOKENS_PATH must point to a JSON file shaped like:

{

"accessToken": " ", "refreshToken": " " }

The server reads this file on startup, uses the access token until it expires, and automatically refreshes it (rewriting the file) using the refresh token — no browser or password prompt involved. This is the recommended option for headless automation, CI, or server-to-server integrations where interactive login isn't possible.

Setup Guides

Choose your AI client for a step-by-step walkthrough:

| Cursor | Cursor Setup