ClickHouse · MCP server
How can an agent on our own infrastructure query our ClickHouse?
The ClickHouse MCP server lets an agent list databases and tables and run SELECT queries on your own ClickHouse. It talks to the ClickHouse at the host you give it, so where that database is yours, nothing goes to an outside service.
What it gives an agent.
Tool by tool.
- 01List databases
- 02List the tables of a database
- 03Run a SELECT query
- list_databases
- list_tables
- run_select_query
Tool names as the public catalog listed them on 15 November 2026
What leaves your environment
Nothing, where the system is yours.The server talks to the ClickHouse at the host you give it. Where that database runs on your infrastructure, the queries and the results stay there.
What it needs
Host, user and password. You give it when you connect the server.
How Katonic governs the calls
Tool calls go through the platform's tool gateway. It manages the connection to each MCP server, passes calls from the agent runtime, and applies the allowlists, rate limits and data-classification rules an administrator sets. Tool usage is recorded. A server can be deployed in your cluster or reached as a remote hosted server.
Use case pages that name ClickHouse.
Can the agent change our data?
The server lists three tools: list databases, list tables and run a SELECT query. Connect it with a database user that has read access only.
Who publishes this server?
ClickHouse. It is not Katonic's software. Katonic runs it and governs the calls an agent makes to it.
Does it need ClickHouse Cloud?
No. It connects to the ClickHouse at the host you give it.