Icedq Tools runs on your own machine — the client starts it, so there is no endpoint to ping. 262 installs a week from npm. Last commit 18 Sep 2026.
MCP Server for iceDQ Data Reliability Platform
Nothing serious here today
Today is the operative word: we check Icedq Tools every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add mcp-server -e 'ICEDQ_BASE_URL=<ICEDQ_BASE_URL>' -e 'ICEDQ_REALM=<ICEDQ_REALM>' -e 'ICEDQ_CLIENT_ID=<ICEDQ_CLIENT_ID>' -e 'AUTH_TYPE=<AUTH_TYPE>' -e 'ICEDQ_ORG_ID=<ICEDQ_ORG_ID>' -- npx -y @icedq/mcp-server{
"mcpServers": {
"mcp-server": {
"command": "npx",
"args": [
"-y",
"@icedq/mcp-server"
],
"env": {
"AUTH_TYPE": "<AUTH_TYPE>",
"ICEDQ_BASE_URL": "<ICEDQ_BASE_URL>",
"ICEDQ_CLIENT_ID": "<ICEDQ_CLIENT_ID>",
"ICEDQ_ORG_ID": "<ICEDQ_ORG_ID>",
"ICEDQ_REALM": "<ICEDQ_REALM>"
}
}
}
}[mcp_servers.mcp-server]
command = "npx"
args = ["-y", "@icedq/mcp-server"]
env = { ICEDQ_BASE_URL = "<ICEDQ_BASE_URL>", ICEDQ_REALM = "<ICEDQ_REALM>", ICEDQ_CLIENT_ID = "<ICEDQ_CLIENT_ID>", AUTH_TYPE = "<AUTH_TYPE>", ICEDQ_ORG_ID = "<ICEDQ_ORG_ID>" }{
"mcpServers": {
"mcp-server": {
"command": "npx",
"args": [
"-y",
"@icedq/mcp-server"
],
"env": {
"AUTH_TYPE": "<AUTH_TYPE>",
"ICEDQ_BASE_URL": "<ICEDQ_BASE_URL>",
"ICEDQ_CLIENT_ID": "<ICEDQ_CLIENT_ID>",
"ICEDQ_ORG_ID": "<ICEDQ_ORG_ID>",
"ICEDQ_REALM": "<ICEDQ_REALM>"
}
}
}
}{
"servers": {
"mcp-server": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@icedq/mcp-server"
],
"env": {
"AUTH_TYPE": "<AUTH_TYPE>",
"ICEDQ_BASE_URL": "<ICEDQ_BASE_URL>",
"ICEDQ_CLIENT_ID": "<ICEDQ_CLIENT_ID>",
"ICEDQ_ORG_ID": "<ICEDQ_ORG_ID>",
"ICEDQ_REALM": "<ICEDQ_REALM>"
}
}
}
}Put your own values in place of
<ICEDQ_BASE_URL> (The base URL of your iceDQ instance (e.g., https://app.icedq.net)), <ICEDQ_REALM> (The authentication realm name (e.g., icedq or iam.icedq)), <ICEDQ_CLIENT_ID> (OAuth client ID for API authentication), <AUTH_TYPE> (How to authenticate: 'username_password' uses credentials below, 'access_token' uses a token file instead), <ICEDQ_ORG_ID> (Your iceDQ organization ID (e.g., org-icedq or org-iam.icedq)).
The author’s registry entry marks them as required.
Optional settings from the registry entry, left out of the block above:
ICEDQ_CLIENT_SECRET (OAuth client secret. Required when AUTH_TYPE is 'username_password'), ICEDQ_USERNAME (Your iceDQ username. Required when AUTH_TYPE is 'username_password'), ICEDQ_PASSWORD (Your iceDQ password. Required when AUTH_TYPE is 'username_password'), TOKENS_PATH (Path to JSON file containing access_token and refresh_token. Required when AUTH_TYPE is 'access_token'), VERIFY_SSL (Enable SSL certificate verification. Set to false only for self-signed certs in testing), REQUEST_TIMEOUT (Timeout for API requests, in seconds).
Alternatives to Icedq Tools
same job, measured the same wayMCP server for RoboShadow's Rubicon Platform Data API.
MCP server for RescueTime productivity data
MCP server for Appcircle mobile CI/CD platform.
MCP server for Pylon customer support platform
MCP server for plausible
MCP server for Security
MCP Server for RQ-SCAN - AI-powered document OCR and data extraction platform
MCP server for recurly
Icedq Tools — questions
Answers built from our own checks of this server.