Data as of

Qdrant MCP Server for Claude Desktop: Setup & Config

Claude Desktop: Qdrant MCP Server stores information and retrieves relevant memories through semantic search.

What you can do with Qdrant in Claude Desktop

A focused official Qdrant memory layer with customizable tools for semantic recall and snippet reuse.

  • Store facts that an assistant can retrieve later.
  • Find reusable code snippets from natural-language descriptions.

Before you start: Qdrant in Claude Desktop

  • uv / uvx
  • A Qdrant server or a configured local Qdrant database path

stdio is the default. For local mode, replace QDRANT_URL with QDRANT_LOCAL_PATH. The README also documents --transport sse and --transport streamable-http; database and model settings use environment variables.

Qdrant Claude Desktop configuration

  1. Choose Claude Desktop configuration scope

    For Qdrant MCP Server, open macOS: ~/Library/Application Support/Claude/claude_desktop_config.json Windows: %APPDATA%\Claude\claude_desktop_config.json. Merge under mcpServers via Settings → Developer → Edit Config when available.

  2. Add Qdrant MCP Server to Claude Desktop

    Use the mcp-server-qdrant entry below in mcpServers. Keep Qdrant MCP Server's documented stdio connection fields and your other Claude Desktop entries.

  3. Check Qdrant MCP Server in Claude Desktop

    Qdrant MCP Server: Fully quit and reopen Claude Desktop; check developer diagnostics.

Config file · macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

Windows: %APPDATA%\Claude\claude_desktop_config.json

JSON
{
  "mcpServers": {
    "mcp-server-qdrant": {
      "command": "uvx",
      "args": [
        "mcp-server-qdrant"
      ],
      "env": {
        "QDRANT_URL": "<Qdrant server URL; omit when using a local path>",
        "QDRANT_API_KEY": "<API key if required by the Qdrant server>",
        "COLLECTION_NAME": "<Default memory collection>",
        "EMBEDDING_MODEL": "<FastEmbed model; default sentence-transformers/all-MiniLM-L6-v2>"
      }
    }
  }
}

Qdrant tools available to Claude Desktop

Qdrant's stored tool list documents 2 tools; compare it with Claude Desktop's connected tool list, because the stored list is not a live check.

qdrant-store

When Claude Desktop requests qdrant-store from Qdrant, review the action before approving it.

Save information with optional JSON metadata in a Qdrant collection.

qdrant-find

When Claude Desktop requests qdrant-find from Qdrant, review the action before approving it.

Qdrant: full stored tool descriptions

Troubleshooting Qdrant in Claude Desktop

  • Fully quit and reopen Claude Desktop for Qdrant MCP Server. If uvx mcp-server-qdrant (from uv, for Python tools) is missing, check the desktop process's PATH, which may differ from your terminal.
  • In Claude Desktop's Qdrant MCP Server entry, check COLLECTION_NAME, EMBEDDING_MODEL, QDRANT_API_KEY, QDRANT_URL. Keep secrets out of shared screenshots and repositories.
  • Qdrant MCP Server uses stdio here: Claude Desktop must keep the configured process running; protocol output belongs on stdout and diagnostics on stderr.
  • Known limitation: Only FastEmbed models are currently supported.
  • Known limitation: A database URL and local path cannot be configured together.
  • Known limitation: The documented tools focus on memory rather than database administration.
  • General Claude Desktop troubleshooting lives in the /clients/claude-desktop guide.

Qdrant MCP Server — details. Claude Desktop guide

Frequently asked questions

Claude Desktop loads Qdrant MCP Server from claude_desktop_config.json: ~/Library/Application Support/Claude/ on macOS, or %APPDATA%\Claude\ on Windows. Open it via Settings → Developer → Edit Config when available.

Claude Desktop's mcp-server-qdrant example uses stdio.

Qdrant MCP Server's Claude Desktop configuration invokes uvx mcp-server-qdrant (from uv, for Python tools).

Claude Desktop's Qdrant MCP Server example references COLLECTION_NAME, EMBEDDING_MODEL, QDRANT_API_KEY, QDRANT_URL. Check these names if startup or authentication fails; the example alone does not distinguish required from optional values.

Qdrant MCP Server's stored list contains 2 tools, including qdrant-store, qdrant-find. Compare those names with Claude Desktop's connected tool list; the stored list is not a live check.

qdrant-store saves information and optional metadata; qdrant-find retrieves relevant stored information.

Yes. Set QDRANT_LOCAL_PATH instead of QDRANT_URL.

The README currently supports FastEmbed only.