Skip to main content
Choose the interface that best fits how you use ClickHouse. For application development, start with an official language client or driver. For interactive work, use a native or web-based tool. For direct integrations, use a network protocol. Before connecting, configure network ports, access rights, and TLS as needed.

Native tools

clickhousectl

The official ClickHouse CLI (chctl): local ClickHouse and Postgres development, and ClickHouse Cloud management.

ClickHouse Client

Native command-line client supporting command-line options and configuration files.

Web Terminal

An in-browser clickhouse-client session over WebSocket.

Model Context Protocol (MCP)

Connect AI assistants to ClickHouse through a standardized interface.

Drivers and language clients

ADBC driver

Connect ADBC-compatible applications to ClickHouse.

ODBC driver

Connect ODBC-compatible applications to ClickHouse.

Language clients

Browse official ClickHouse clients for your programming language.

Protocols

HTTP interface

Use ClickHouse over HTTP from any platform or language.

Native TCP interface

Use the native protocol for ClickHouse-aware clients and inter-server communication.

gRPC interface

Use ClickHouse’s gRPC interface.

Arrow Flight interface

Connect Flight SQL clients using Apache Arrow.

MySQL interface

Connect MySQL-compatible clients.

PostgreSQL interface

Connect PostgreSQL-compatible clients.

SSH interface

Connect with an SSH client to the ClickHouse server.

Prometheus

Prometheus API and PromQL

Store Prometheus metrics in ClickHouse and query them with PromQL.

Prometheus metrics endpoint

Expose ClickHouse server metrics for a Prometheus server to scrape.

Built-in web interfaces

Web SQL UI (Play)

The built-in in-browser SQL interface served by ClickHouse at /play.

SQL Console

An embedded web interface for running queries and exploring data.

Documentation Search

Search the reference documentation embedded in a running ClickHouse server.