Elasticsearch MCP Server vs MCP Server Qdrant

A side-by-side look at the Elasticsearch MCP Server and MCP Server Qdrant MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Elasticsearch MCP Server logoElasticsearch MCP ServerDatabases · Local subprocess (stdio)MCP Server implementation that provides Elasticsearch interaction65GreatAuth: api key requiredMCP Server Qdrant logoMCP Server QdrantDatabases · Local subprocess (stdio)An official Qdrant Model Context Protocol (MCP) server implementation79GreatAuth: api key required

Verdict: choose Elasticsearch MCP Server for databases work as a local process; choose MCP Server Qdrant for databases as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Elasticsearch MCP Server logoChoose Elasticsearch MCP Server when

  • You need dedicated capabilities in the Databases domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: API key required.
  • You want tools like list_indices, get_index, create_index.
Explore Elasticsearch MCP Server

MCP Server Qdrant logoChoose MCP Server Qdrant when

  • You need dedicated capabilities in the Databases domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: API key required.
  • You have the keys it needs: QDRANT_URL, QDRANT_API_KEY, QDRANT_LOCAL_PATH, COLLECTION_NAME, EMBEDDING_PROVIDER, EMBEDDING_MODEL, QDRANT_SEARCH_LIMIT, QDRANT_READ_ONLY.
  • You want tools like information, metadata, collection_name.
Explore MCP Server Qdrant

Feature & specification comparison

Rows where the two servers differ are marked.

SpecElasticsearch MCP Server logoElasticsearch MCP ServerMCP Server Qdrant logoMCP Server Qdrant
CategoryDatabasesDatabases
Quality signal65/100 · Great79/100 · Great
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthAPI key requiredAPI key required
PricingFreeFree
Required env varsNone listedQDRANT_URLQDRANT_API_KEYQDRANT_LOCAL_PATHCOLLECTION_NAMEEMBEDDING_PROVIDEREMBEDDING_MODELQDRANT_SEARCH_LIMITQDRANT_READ_ONLY
Verified ownerCommunity listing Verified
GitHub stars3131,553
Directory activity 3 views 0 installs 0 upvotes 7 views 0 installs 0 upvotes
Tools204

Tools & capabilities

Elasticsearch MCP Server tools 20

  • list_indicesList all indices.
  • get_indexReturns information (mappings, settings, aliases) about one or more indices.
  • create_indexCreate a new index.
  • delete_indexDelete an index.
  • search_documentsSearch for documents.
  • index_documentCreates or updates a document in the index.
  • get_documentGet a document by ID.
  • delete_documentDelete a document by ID.
  • delete_by_queryDeletes documents matching the provided query.
  • get_cluster_healthReturns basic information about the health of the cluster.
  • get_cluster_statsReturns high-level overview of cluster statistics.
  • list_aliasesList all aliases.
  • +8 more on the listing page

MCP Server Qdrant tools 4

  • information
  • metadata
  • collection_name
  • query

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.

Elasticsearch MCP Server

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "cr7258-elasticsearch-mcp-server": {
      "command": "uvx",
      "args": [
        "elasticsearch-mcp-server"
      ]
    }
  }
}

MCP Server Qdrant

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "qdrant-mcp-server-qdrant": {
      "command": "uvx",
      "args": [
        "mcp-server-qdrant"
      ],
      "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"
      }
    }
  }
}

Frequently asked questions

Elasticsearch MCP Server is categorized under Databases and uses a local stdio subprocess. MCP Server Qdrant belongs to Databases and uses a local stdio subprocess. Pick Elasticsearch MCP Server for databases work and MCP Server Qdrant 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.

Elasticsearch MCP Server is listed as free. Auth: api key required. MCP Server Qdrant is listed as free. Auth: api key required. 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 cr7258-elasticsearch-mcp-server and qdrant-mcp-server-qdrant as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Elasticsearch MCP Server has a quality signal of 65/100 (Great) with 3 views, 0 installs and 313 GitHub stars. MCP Server Qdrant has 79/100 (Great) with 7 views, 0 installs and 1,553 GitHub stars.