ClickHouse vs Dbridge MCP — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
ClickHouse vs Dbridge MCP
In-depth architectural comparison of the ClickHouse and Dbridge MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
ClickHouse
Databases · Local stdio
Quality: 53/100 (Good) | Auth: other
Dbridge MCP
Databases · Local stdio
Quality: 57/100 (Good) | Auth: other
Verdict Summary: Choose ClickHouse if you need specialized Databases tools running via a local process. Choose Dbridge MCP if your workspace requires Databases integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose ClickHouse when:
You need dedicated capabilities in the Databases domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: other (Free / Open Source).
You have access to required keys: MCP_CLICKHOUSE_DSN.
Read-only MCP server for ClickHouse metadata, parameterized queries, and plan analysis.
Query SQLite, PostgreSQL, and MySQL in plain language — read-only by design, with column hiding/masking, row caps, per-query timeouts, cost-based rejection, and rate limiting.
List configured profiles. Each entry includes name and optional description.
get_cluster_properties
Get cluster properties and execution limits. Returns ClickHouse server version plus enforced limits (max rows, timeouts) for the profile.
run_query
Execute read-only SELECT or WITH … SELECT. One statement; DML, DDL, SET, SYSTEM, and similar are rejected. Returns `{data, row_count}` where `data` is an RFC 4180 CSV string. Pass `snapshot=true` to persist the result to disk and receive `{snapshot_uri, row_count}` instead; fetch the CSV via the sn…
run_show
Execute SHOW introspection statement. One statement per call; INTO OUTFILE rejected. Interactive row limits apply (default 500, hard ceiling 1 000). Same timeout as run_query.
analyze_query
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
ClickHouse is categorized under Databases and uses a local stdio subprocess. In contrast, Dbridge MCP belongs to Databases using local stdio subprocess. Select ClickHouse when you need capabilities focused on databases and Dbridge MCP when you require tools for databases.
Explain read-only SELECT or WITH … SELECT. Returns plan, pipeline, and/or syntax text. Default types plan and pipeline. Uses query timeout and optional database; no max-rows cap unlike run_query.
list_databases
List databases. Rows from system.databases visible to the connection.
list_tables
List tables and views in a database. Rows from system.tables: name, engine, primary_key, sorting_key, partition_key, total_rows, total_bytes for query planning.
list_columns
List columns for a table or view. Rows from system.columns for the resolved database and table.
Dbridge MCP Tools (11)
list_tables
List every table in the database.
describe_table
Return a table's columns, primary key, foreign keys, and row-count estimate.
sample_table
Preview the first rows of a table (`json`/`csv`/`markdown`).
count_rows
Return the exact row count of a table.
run_query
Run a single read-only `SELECT` / `WITH` and return rows as `json`, `csv`, or `markdown`.
explain_query
Return a query's plan and estimated cost without running it.
column_stats
Per-column distinct-value counts and null fractions — is this column selective enough to index?
index_health
List indexes with sizes and scan counts, flagging unused, duplicate, and invalid ones.
test_index
Simulate a `CREATE INDEX` without building it and report whether the planner would use it (PostgreSQL, via [hypopg](https://github.com/HypoPG/hypopg)).
slow_queries
The most expensive recorded statements with call counts and timings (PostgreSQL `pg_stat_statements`, MySQL `performance_schema`).
get_limits
Report the safety limits in effect (caps, timeouts, hidden/masked columns).