Clients
Connect Hypequery MCP to Claude Desktop, Cursor, and other MCP clients.
Hypequery MCP runs over stdio. Your MCP client launches hypequery-mcp and passes a config path.
Claude Desktop
Add a server entry to Claude Desktop's config file:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"hypequery": {
"command": "npx",
"args": [
"-y",
"@hypequery/mcp",
"--config",
"/absolute/path/to/mcp-config.mjs"
],
"env": {
"CLICKHOUSE_URL": "https://example.clickhouse.cloud:8443",
"CLICKHOUSE_USER": "default",
"CLICKHOUSE_PASSWORD": "password",
"CLICKHOUSE_DATABASE": "analytics"
}
}
}
}Restart Claude Desktop after changing the config.
Cursor
Use the same command and arguments in Cursor's MCP configuration:
{
"mcpServers": {
"hypequery": {
"command": "npx",
"args": [
"-y",
"@hypequery/mcp",
"--config",
"/absolute/path/to/mcp-config.mjs"
],
"env": {
"CLICKHOUSE_URL": "https://example.clickhouse.cloud:8443",
"CLICKHOUSE_USER": "default",
"CLICKHOUSE_PASSWORD": "password",
"CLICKHOUSE_DATABASE": "analytics"
}
}
}
}Test the server directly
Before connecting a client, run the server from a terminal:
npx -y @hypequery/mcp --config /absolute/path/to/mcp-config.mjsYou should see startup logs on stderr. The process keeps running because the MCP client normally owns its lifecycle.
Use absolute paths in client config. Desktop clients often launch from a different working directory than your terminal.