MCP Clickhousex MCP Server

All settings use the **MCP_CLICKHOUSE** prefix. **Flat** environment variables (e.g. `MCP_CLICKHOUSE_DSN`) are the straightforward way to configure

Local serverstdioPython

What is the MCP Clickhousex MCP server?

If you already use MCP Clickhousex, the mcp clickhousex mcp server is the piece that lets your assistant work with it directly. All settings use the MCP_CLICKHOUSE prefix. Flat environment variables (e.g. MCP_CLICKHOUSE_DSN) are the straightforward way to configure the default profile when you have a single connection. For multiple profiles, the.

Installation

@modelcontextprotocol/inspector on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • Cursor — The Cursor tool exposed by this server
  • Codex — The Codex tool exposed by this server
  • OpenCode — The OpenCode tool exposed by this server
  • Copilot — The Copilot tool exposed by this server

Credentials and setup notes

Configuration is passed through the environment: MCP_CLICKHOUSE_DSN, MCP_CLICKHOUSE_DESCRIPTION, MCP_CLICKHOUSE_QUERY_MAX_ROWS, MCP_CLICKHOUSE_SNAPSHOT_MAX_ROWS, MCP_TEST_CLICKHOUSE_DSN, MCP_CLICKHOUSE_PROFILES_WAREHOUSE_DSN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Worth knowing first

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. MCP Clickhousex's toolset — Cursor, Codex, OpenCode and 1 more — is a fair guide to whether it matches your workflow. It is maintained by alyiox; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Available tools

ToolWhat it does
CursorThe Cursor tool exposed by this server.
CodexThe Codex tool exposed by this server.
OpenCodeThe OpenCode tool exposed by this server.
CopilotThe Copilot tool exposed by this server.

How to install the MCP Clickhousex MCP server

{
  "mcpServers": {
    "clickhouse": {
      "command": "uvx",
      "args": ["mcp-clickhousex"],
      "env": {
        "MCP_CLICKHOUSE_DSN": "http://default:@localhost:8123/default"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
MCP_CLICKHOUSE_DSNEndpoint or connection string the server talks to.Yes
MCP_CLICKHOUSE_DESCRIPTIONConfiguration value read at startup.Optional
MCP_CLICKHOUSE_QUERY_MAX_ROWSConfiguration value read at startup.Optional
MCP_CLICKHOUSE_SNAPSHOT_MAX_ROWSConfiguration value read at startup.Optional
MCP_TEST_CLICKHOUSE_DSNEndpoint or connection string the server talks to.Yes
MCP_CLICKHOUSE_PROFILES_WAREHOUSE_DSNEndpoint or connection string the server talks to.Yes

Example prompts to try

  • Use MCP Clickhousex to Cursor.
  • Use MCP Clickhousex to Codex.
  • Use MCP Clickhousex to OpenCode.

Frequently asked questions

It connects MCP Clickhousex to MCP-compatible AI assistants such as Claude and Cursor, exposing 4 tools (Cursor, Codex, OpenCode, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with MCP Clickhousex directly.