Apify MCP Server
MCP setupData and AI
FreeMCP setupData and AI
Let your agent run read-only SQL against ClickHouse and browse its databases and tables using ClickHouse's official MCP server.
npx workspacetemplates add clickhouse-mcp --tool claude-codeWrites 1 file to your project root
{
"mcpServers": {
"clickhouse": {
"command": "uv",
"args": [
"run",
"--with",
"mcp-clickhouse",
"--python",
"3.12",
"mcp-clickhouse"
],
"env": {
"CLICKHOUSE_HOST": "${CLICKHOUSE_HOST}",
"CLICKHOUSE_USER": "${CLICKHOUSE_USER}",
"CLICKHOUSE_PASSWORD": "${CLICKHOUSE_PASSWORD}",
"CLICKHOUSE_SECURE": "${CLICKHOUSE_SECURE}"
}
}
}
}npx workspacetemplates add clickhouse-mcp --tool codexWrites 1 file to ~/.codex/
[mcp_servers.clickhouse]
command = "uv"
args = ["run","--with","mcp-clickhouse","--python","3.12","mcp-clickhouse"]
[mcp_servers.clickhouse.env]
CLICKHOUSE_HOST = "${CLICKHOUSE_HOST}"
CLICKHOUSE_USER = "${CLICKHOUSE_USER}"
CLICKHOUSE_PASSWORD = "${CLICKHOUSE_PASSWORD}"
CLICKHOUSE_SECURE = "${CLICKHOUSE_SECURE}"npx workspacetemplates add clickhouse-mcp --tool cursorWrites 1 file to .cursor/
{
"mcpServers": {
"clickhouse": {
"command": "uv",
"args": [
"run",
"--with",
"mcp-clickhouse",
"--python",
"3.12",
"mcp-clickhouse"
],
"env": {
"CLICKHOUSE_HOST": "${env:CLICKHOUSE_HOST}",
"CLICKHOUSE_USER": "${env:CLICKHOUSE_USER}",
"CLICKHOUSE_PASSWORD": "${env:CLICKHOUSE_PASSWORD}",
"CLICKHOUSE_SECURE": "${env:CLICKHOUSE_SECURE}"
}
}
}
}npx workspacetemplates add clickhouse-mcp --tool gemini-cliWrites 1 file to .gemini/
{
"mcpServers": {
"clickhouse": {
"command": "uv",
"args": [
"run",
"--with",
"mcp-clickhouse",
"--python",
"3.12",
"mcp-clickhouse"
],
"env": {
"CLICKHOUSE_HOST": "$CLICKHOUSE_HOST",
"CLICKHOUSE_USER": "$CLICKHOUSE_USER",
"CLICKHOUSE_PASSWORD": "$CLICKHOUSE_PASSWORD",
"CLICKHOUSE_SECURE": "$CLICKHOUSE_SECURE"
}
}
}
}npx workspacetemplates add clickhouse-mcp --tool copilotWrites 1 file to .vscode/
{
"inputs": [
{
"type": "promptString",
"id": "clickhouse_host",
"description": "Hostname of the ClickHouse server.",
"password": true
},
{
"type": "promptString",
"id": "clickhouse_user",
"description": "A database user. Use one granted SELECT only.",
"password": true
},
{
"type": "promptString",
"id": "clickhouse_password",
"description": "Password for that user.",
"password": true
},
{
"type": "promptString",
"id": "clickhouse_secure",
"description": "Set to true to connect over HTTPS, which is the default.",
"password": true
}
],
"servers": {
"clickhouse": {
"type": "stdio",
"command": "uv",
"args": [
"run",
"--with",
"mcp-clickhouse",
"--python",
"3.12",
"mcp-clickhouse"
],
"env": {
"CLICKHOUSE_HOST": "${input:clickhouse_host}",
"CLICKHOUSE_USER": "${input:clickhouse_user}",
"CLICKHOUSE_PASSWORD": "${input:clickhouse_password}",
"CLICKHOUSE_SECURE": "${input:clickhouse_secure}"
}
}
}
}mcp-clickhouse is ClickHouse's own MCP server. It gives the agent three tools: run a query, list databases and list tables, with paging and name filters for large schemas. That is enough to explore an analytics warehouse and draft queries against real column names.
Queries run with the readonly setting on by default, because CLICKHOUSE_ALLOW_WRITE_ACCESS is false unless you change it. The ClickHouse user's grants remain the real boundary, so connect with an account that can only read.
you › In the analytics database, count page_views per day for the last 7 days and note any day that dips below half the average.
agent › Seven rows returned, averaging 41k views per day. Saturday shows 17k, under half the average, which matches the weekend traffic pattern.MCP setupData and AI
FreeMCP setupData and AI
FreeMCP setupData and AI
FreeMCP setupData and AI
Free