What is the key difference between MCP Server Qdrant and MCP Clickhouse?

MCP Server Qdrant belongs to the Databases category with local stdio execution, while MCP Clickhouse belongs to the Databases category with local stdio execution.

How do I install MCP Server Qdrant or MCP Clickhouse in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are MCP Server Qdrant and MCP Clickhouse free or paid?

MCP Server Qdrant operates under a Free / Open Source model (API Key required). MCP Clickhouse operates under a Free / Open Source model (other).

Which MCP server has more tools and community activity?

MCP Server Qdrant lists 4 tools with 3 views and 1,530 GitHub stars. MCP Clickhouse lists 3 tools with 3 views and 872 GitHub stars.

Can I use both MCP Server Qdrant and MCP Clickhouse together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

MCP Server Qdrant vs MCP Clickhouse

In-depth architectural comparison of the MCP Server Qdrant and MCP Clickhouse 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

MCP Server Qdrant

Databases · Local stdio

Quality: 80/100 (Excellent) | Auth: API Key required

MCP Clickhouse

Databases · Local stdio

Quality: 65/100 (Great) | Auth: other

Verdict Summary: Choose MCP Server Qdrant if you need specialized Databases tools running via a local process. Choose MCP Clickhouse 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 MCP Server Qdrant when:

You need dedicated capabilities in the Databases domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: QDRANT_URL, QDRANT_API_KEY, QDRANT_LOCAL_PATH, COLLECTION_NAME, EMBEDDING_PROVIDER, EMBEDDING_MODEL, QDRANT_SEARCH_LIMIT, QDRANT_READ_ONLY.
Primary tools included: information, metadata, collection_name.

Explore MCP Server Qdrant Details

Choose MCP 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).
Primary tools included: list_databases, list_tables, run_query.

Feature & Specification Comparison

Specification	MCP Server Qdrant qdrant VerifiedDatabases	MCP Clickhouse ClickHouse Databases
Summary	An official Qdrant Model Context Protocol (MCP) server implementation	ClickHouse database integration with schema inspection and query capabilities
Category & Scope

Tools & Capabilities Breakdown

MCP Server Qdrant Tools (4)

information

metadata

collection_name

query

MCP Clickhouse Tools (3)

list_databases

List available ClickHouse databases

list_tables

List available ClickHouse tables in a database, including schema, comment, row count, and column count. Args: database: The database to list tables from like: Optional LIKE pattern to filter table names not_like: Optional NOT LIKE pattern to exclude table names page_token: Token for pagination, obtained from a previous call page_size: Number of tables to return per page (default: 50) include_detailed_columns: Whether to include detailed column metadata (default: True). When False, the columns array will be empty but create_table_query still contains all column information. This reduces payload size for large schemas. Returns: A JSON-encoded string of an object containing: - tables: List of table information (as dictionaries) - next_page_token: Token for the next page, or None if no more pages - total_tables: Total number of tables matching the filters

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

MCP Server Qdrant Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "qdrant-mcp-server-qdrant": {
      "command": "uvx",
      "args": [
        "When"
      ],
      "env": {
        "QDRANT_URL": "YOUR_QDRANT_URL_HERE",
        "QDRANT_API_KEY": "YOUR_QDRANT_API_KEY_HERE",
        "QDRANT_LOCAL_PATH": "YOUR_QDRANT_LOCAL_PATH_HERE",
        "COLLECTION_NAME": "YOUR_COLLECTION_NAME_HERE",
        "EMBEDDING_PROVIDER": "YOUR_EMBEDDING_PROVIDER_HERE",
        "EMBEDDING_MODEL": "YOUR_EMBEDDING_MODEL_HERE",
        "QDRANT_SEARCH_LIMIT": "YOUR_QDRANT_SEARCH_LIMIT_HERE",
        "QDRANT_READ_ONLY": "YOUR_QDRANT_READ_ONLY_HERE"
      }
    }
  }
}

MCP Clickhouse Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "clickhouse-mcp-clickhouse": {
      "command": "uvx",
      "args": [
        "mcp-clickhouse"
      ]
    }
  }
}

Frequently Asked Questions

MCP Server Qdrant is categorized under Databases and uses a local stdio subprocess. In contrast, MCP Clickhouse belongs to Databases using local stdio subprocess. Select MCP Server Qdrant when you need capabilities focused on databases and MCP Clickhouse when you require tools for databases.

More alternatives to MCP Server Qdrant More alternatives to MCP Clickhouse Databases category hub Canonical compare URL