ClickHouse vs Pgmcp

In-depth architectural comparison of the ClickHouse and Pgmcp 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.

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.
• Primary tools included: list_profiles, run_query, run_show.

Explore ClickHouse Details

Choose Pgmcp when:

• You need dedicated capabilities in the Databases domain.
• You prefer remote streaming HTTP/SSE transport architecture.
• Your security boundary fits: API Key required (Free / Open Source).
• You have access to required keys: DATABASE_URL.
• Primary tools included: Natural-language to SQL generation, Read-only SQL enforcement, Automatic result streaming and pagination.

Feature & Specification Comparison

Specification	ClickHouse Databases	Pgmcp subnetmarco Databases
Summary	Read-only MCP server for ClickHouse metadata, parameterized queries, and plan analysis.	Natural language PostgreSQL queries with automatic streaming, read-only safety, and universal database compatibility.
Category & Scope	Databases	Databases

Tools & Capabilities Breakdown

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).

{
  "mcpServers": {
    "clickhouse": {
      "command": "uvx",
      "args": [
        "mcp-clickhousex"
      ],
      "env": {
        "MCP_CLICKHOUSE_DSN": "YOUR_MCP_CLICKHOUSE_DSN_HERE"
      }
    }
  }
}

{
  "mcpServers": {
    "subnetmarco-pgmcp": {
      "url": "http://localhost:8080/mcp"
    }
  }
}

Related MCP Server Comparisons