topmcps
Browse MCPs

MCP Comparison · 2026

ClickHouse vs PostgreSQL (archived) MCP Server

Comparing ClickHouse and PostgreSQL (archived) as MCP servers? ClickHouse (query clickhouse) is best when product analytics queries. PostgreSQL (archived) (query postgres) is best when auditing or replacing an existing install. Both run as Model Context Protocol servers and can coexist in the same client. Updated 2026.

ClickHouse

ClickHouse

Query ClickHouse and ClickHouse Cloud columnar warehouses from an AI agent.

PostgreSQL (archived)

PostgreSQL (archived)

Anthropic's reference Postgres MCP — archived July 2025 and superseded by Postgres MCP Pro or the Supabase MCP.

Side-by-side specs

Pulled from each MCP's verified fact sheet.

 ClickHousePostgreSQL (archived)
Primary functionQuery ClickHouseQuery Postgres
MaintainerClickHouseAnthropic (archived 2025-07-10)
PricingOpen sourceOpen source
Setup complexityMedium · ~10 minLow · ~3 min
Transportstdiostdio
Auth modelAPI keyAPI key
LicenseApache-2.0MIT
LanguagePythonTypeScript
Latest versionlatestarchived
Compatible clientsClaude, Cursor, VS Code, Windsurf, Any MCP-compatible client, ClickHouse 22+, ClickHouse CloudClaude, Cursor, Any MCP-compatible client, PostgreSQL 12+
Last verified2026-06-022026-05-29

Which one should you pick?

Decision rubric drawn from each MCP's documented strengths.

Choose ClickHouse

  • Product analytics queries
  • Observability log search
  • Time-series rollups
See full ClickHouse write-up →

Choose PostgreSQL (archived)

  • Auditing or replacing an existing install
  • Reference reading for how the early MCP servers were structured
See full PostgreSQL (archived) write-up →

Pick something else if…

  • OLTP workflows
  • New installs (the repo is archived)

Feature breakdown

Key capabilities each server ships out of the box.

ClickHouse

  • Official ClickHouse maintainership
  • Read-only by default
  • ClickHouse Cloud + self-hosted
  • Dictionary and materialized-view introspection
  • Query log inspection for cost auditing

PostgreSQL (archived)

  • Archived on 2025-07-10 — no upstream maintenance
  • Read-only contract is bypassable per Datadog Security Labs
  • SELECT-only tool surface (when the contract holds)
  • Stdio transport; one connection per process
  • Recommended migration: Postgres MCP Pro or Supabase MCP

Install snippets

Open the detail page for ready-to-paste config for every major client.

Install ClickHouse

Setup snippets for Claude, Cursor, VS Code, Windsurf →

uvx mcp-clickhouse

Install PostgreSQL (archived)

Setup snippets for Claude, Cursor, VS Code, Windsurf →

npx -y @modelcontextprotocol/server-postgres postgresql://user:pass@localhost/db

FAQ

ClickHouse vs PostgreSQL (archived): which MCP server should I use?

Pick ClickHouse when product analytics queries. Pick PostgreSQL (archived) when auditing or replacing an existing install. ClickHouse is built for query clickhouse, while PostgreSQL (archived) focuses on query postgres.

Can I run both ClickHouse and PostgreSQL (archived) together?

Yes. MCP clients run each server as a separate process and surface every server's tools simultaneously, so you can install both and let your agent decide which to call. Be deliberate with auth scopes when stacking servers.

Which is easier to set up, ClickHouse or PostgreSQL (archived)?

PostgreSQL (archived) has the lighter setup. ClickHouse reports medium complexity (~10 min); PostgreSQL (archived) reports low complexity (~3 min).

More ClickHouse comparisons

ClickHousevsBigQueryClickHousevsSnowflakeClickHousevsDuckDBClickHousevsElasticsearch

Browse all Databases MCPs? See the full ranked list →