MCP Clickhouse vs MCP Snowflake Server
A side-by-side look at the MCP Clickhouse and MCP Snowflake Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose MCP Clickhouse for databases work as a local process; choose MCP Snowflake Server for databases as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose MCP Clickhouse when
- You need dedicated capabilities in the Databases domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: other.
- You want tools like
list_databases, list_tables, run_query.
Choose MCP Snowflake Server when
- You need dedicated capabilities in the Databases domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: other.
- You have the keys it needs:
SNOWFLAKE_USER, SNOWFLAKE_ACCOUNT, SNOWFLAKE_ROLE, SNOWFLAKE_DATABASE, SNOWFLAKE_SCHEMA, SNOWFLAKE_WAREHOUSE, SNOWFLAKE_PASSWORD, SNOWFLAKE_PRIVATE_KEY_PATH. - You want tools like
read_query, query, SELECT.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Databases | Databases |
| Quality signal | 67/100 · Great | 55/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | other | other |
| Pricing | Free | BYOK (pay the provider) |
| Required env vars | None listed | SNOWFLAKE_USERSNOWFLAKE_ACCOUNTSNOWFLAKE_ROLESNOWFLAKE_DATABASESNOWFLAKE_SCHEMASNOWFLAKE_WAREHOUSESNOWFLAKE_PASSWORDSNOWFLAKE_PRIVATE_KEY_PATH |
| Verified owner | Community listing | Community listing |
| GitHub stars | 890 | 184 |
| Directory activity | 6 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 3 | 15 |
| Full listing | View MCP Clickhouse | View MCP Snowflake Server |
Tools & capabilities
MCP Clickhouse tools 3
list_databasesList available ClickHouse databaseslist_tablesList available ClickHouse tables in a database, including schema, comment, row count, and column count. Integers outside [-9007199254740991, 9007199254740991] in table metadata are returned as decimal strings. Pagination tokens are single-use and retained for up to one hour.run_queryExecute SQL queries in ClickHouse. Queries run in read-only mode by default. Bind optional params by name with {name:Type} placeholders, such as {name:String} or {vector:Array(Float32)}. Values may be JSON scalars, nulls, or arrays. Pass exact large integers as decimal strings. JSON lists and objects cannot bind to Tuple and Map types. Python percent formatting and $name$ raw binary parameters are not supported. Parameter values stay out of the MCP server's normal SQL log lines, but may appear in errors and backend logs. Set CLICKHOUSE_ALLOW_WRITE_ACCESS=true to allow DDL and DML operations. Set CLICKHOUSE_ALLOW_DROP=true to additionally allow destructive operations (DROP, TRUNCATE, DELETE, UPDATE, REPLACE TABLE/PARTITION, CREATE OR REPLACE, CLEAR COLUMN/INDEX/PROJECTION, DETACH PERMANENTLY). That gate is a best-effort accident guard, not a security boundary. Integers outside [-9007199254740991, 9007199254740991] are returned as decimal strings. Two optional checks also run through this tool. Use DESCRIBE (<query>) when you need a query's output columns and types; it inspects the result schema and surfaces analysis errors such as an unknown column, but a query that describes cleanly can still fail at runtime. Consider EXPLAIN ESTIMATE <query> before a SELECT that could be expensive; it returns the estimated parts, rows and marks read from MergeTree family tables, which is not run time and not result size. Neither runs the query body, though analysis can execute scalar subqueries.
MCP Snowflake Server tools 15
read_queryquerySELECTwrite_querycreate_tablelist_databaseslist_schemasdatabaselist_tablesschemadescribe_tabletable_name- +3 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
MCP Clickhouse
{
"mcpServers": {
"clickhouse-mcp-clickhouse": {
"command": "uvx",
"args": [
"mcp-clickhouse"
]
}
}
}
MCP Snowflake Server
{
"mcpServers": {
"isaacwasserman-mcp-snowflake-server": {
"command": "uvx",
"args": [
"--python=3.12",
"mcp_snowflake_server"
],
"env": {
"SNOWFLAKE_USER": "YOUR_SNOWFLAKE_USER_HERE",
"SNOWFLAKE_ACCOUNT": "YOUR_SNOWFLAKE_ACCOUNT_HERE",
"SNOWFLAKE_ROLE": "YOUR_SNOWFLAKE_ROLE_HERE",
"SNOWFLAKE_DATABASE": "YOUR_SNOWFLAKE_DATABASE_HERE",
"SNOWFLAKE_SCHEMA": "YOUR_SNOWFLAKE_SCHEMA_HERE",
"SNOWFLAKE_WAREHOUSE": "YOUR_SNOWFLAKE_WAREHOUSE_HERE",
"SNOWFLAKE_PASSWORD": "YOUR_SNOWFLAKE_PASSWORD_HERE",
"SNOWFLAKE_PRIVATE_KEY_PATH": "YOUR_SNOWFLAKE_PRIVATE_KEY_PATH_HERE"
}
}
}
}
Frequently asked questions
MCP Clickhouse is categorized under Databases and uses a local stdio subprocess. MCP Snowflake Server belongs to Databases and uses a local stdio subprocess. Pick MCP Clickhouse for databases work and MCP Snowflake Server for databases.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
MCP Clickhouse is listed as free. Auth: other. MCP Snowflake Server is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: other. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add clickhouse-mcp-clickhouse and isaacwasserman-mcp-snowflake-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP Clickhouse has a quality signal of 67/100 (Great) with 6 views, 0 installs and 890 GitHub stars. MCP Snowflake Server has 55/100 (Good) with 2 views, 0 installs and 184 GitHub stars.