MCP Server Qdrant vs MCP Victorialogs

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

MCP Server Qdrant logoMCP Server QdrantDatabases · Local subprocess (stdio)An official Qdrant Model Context Protocol (MCP) server implementation79GreatAuth: api key requiredMCP Victorialogs logoMCP VictorialogsDatabases · Remote HTTP/SSEProvides comprehensive integration with your VictoriaLogs instance APIs and documentation for working with logs, investigating and debugging tasks related to your VictoriaLogs instances.64GoodAuth: no auth required

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

Which MCP server should you choose?

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

MCP Victorialogs logoChoose MCP Victorialogs when

  • You need dedicated capabilities in the Databases domain.
  • You prefer a remote HTTP/SSE transport.
  • Its auth model fits you: No auth required.
  • You have the keys it needs: VL_INSTANCE_ENTRYPOINT, VL_INSTANCE_BEARER_TOKEN, VL_INSTANCE_HEADERS, MCP_PASSTHROUGH_HEADERS, VL_DEFAULT_TENANT_ID, MCP_SERVER_MODE, MCP_LISTEN_ADDR.
  • You want tools like documentation, facets, field_names.
Explore MCP Victorialogs

Feature & specification comparison

Rows where the two servers differ are marked.

SpecMCP Server Qdrant logoMCP Server QdrantMCP Victorialogs logoMCP Victorialogs
CategoryDatabasesDatabases
Quality signal79/100 · Great64/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Remote HTTP/SSE
AuthAPI key requiredNo auth required
PricingFreeFree
Required env varsQDRANT_URLQDRANT_API_KEYQDRANT_LOCAL_PATHCOLLECTION_NAMEEMBEDDING_PROVIDEREMBEDDING_MODELQDRANT_SEARCH_LIMITQDRANT_READ_ONLYVL_INSTANCE_ENTRYPOINTVL_INSTANCE_BEARER_TOKENVL_INSTANCE_HEADERSMCP_PASSTHROUGH_HEADERSVL_DEFAULT_TENANT_IDMCP_SERVER_MODEMCP_LISTEN_ADDR
Verified owner VerifiedCommunity listing
GitHub stars1,552104
Directory activity 6 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
Tools413

Tools & capabilities

MCP Server Qdrant tools 4

  • information
  • metadata
  • collection_name
  • query

MCP Victorialogs tools 13

  • documentationSearch documentation resources for the given search query, returning the URIs of the resources that match the search criteria sorted by relevance. This tool can help to get context for any VictoriaLogs related question.
  • facetsThe most frequent values per each log field seen in the logs returned by the given <query> on the given [<start> ... <end>] time range. This tool uses `/select/logsql/facets` endpoint of VictoriaLogs API.
  • field_namesGet field names from results of the given <query> on the given [<start> ... <end>] time range. The response also contains the number of log results per every field name. This tool uses `/select/logsql/field_names` endpoint of VictoriaLogs API.
  • field_valuesGet unique values for the given <fieldName> field from results of the given <query> on the given [<start> ... <end>] time range. The response also contains the number of log results per every field value. This tool uses `/select/logsql/field_values` endpoint of VictoriaLogs API.
  • flagsList of non-default flags (parameters) of the VictoriaLogs instance. This tools uses `/flags` endpoint of VictoriaLogs API.
  • hitsThe number of matching log entries for the given <query> on the given [<start> ... <end>] time range grouped by <step> buckets. The returned results are sorted by time. This tool uses `/select/logsql/hits` endpoint of VictoriaLogs API.
  • queryExecutes LogsQL query expression to search log entries. This tool uses `/select/logsql/query` endpoint of VictoriaLogs API.
  • stats_queryLog stats for the given query at the given timestamp (time) in the format compatible with Prometheus querying API. This tool uses `/select/logsql/stats_query` endpoint of VictoriaLogs API.
  • stats_query_rangeLog stats for the given query on the given [start ... end] time range with the given step interval. The stats is returned in the format compatible with Prometheus querying API. This tool uses `/select/logsql/stats_query_range` endpoint of VictoriaLogs API.
  • stream_field_namesGet log stream field names from results of the given <query> on the given [<start> ... <end>] time range. The response also contains the number of log results per every field name.. This tool uses `/select/logsql/stream_field_names` endpoint of VictoriaLogs API.
  • stream_field_valuesGet unique values for the given <fieldName> field from results of the given <query> on the given [<start> ... <end>] time range. The response also contains the number of log results per every field value. This tool uses `/select/logsql/stream_field_values` endpoint of VictoriaLogs API.
  • stream_idsGet _stream_id values for the log streams from results of the given <query> on the given [<start> ... <end>] time range. The response also contains the number of log results per every _stream_id. This tool uses `/select/logsql/stream_ids` endpoint of VictoriaLogs API.
  • +1 more on the listing page

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.

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"
      }
    }
  }
}

MCP Victorialogs

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "victoriametrics-community-mcp-victorialogs": {
      "url": "https://play-vmlogs-mcp.victoriametrics.com/mcp"
    }
  }
}

Frequently asked questions

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

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

On AllMCPs, MCP Server Qdrant has a quality signal of 79/100 (Great) with 6 views, 0 installs and 1,552 GitHub stars. MCP Victorialogs has 64/100 (Good) with 1 views, 0 installs and 104 GitHub stars.