Qdrant MCP Server for Claude Code: Setup & Config

What you can do with Qdrant in Claude Code

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

• Store facts that an assistant can retrieve later.
• Share a remotely reachable memory server with an MCP workflow.

Before you start: Qdrant in Claude Code

• 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 Code configuration

1. Choose Claude Code configuration scope

   For Qdrant MCP Server, open Project scope: .mcp.json at the repository root. Project JSON: merge into mcpServers; user scope: use the CLI.

2. Add Qdrant MCP Server to Claude Code

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

3. Check Qdrant MCP Server in Claude Code

   Qdrant MCP Server: Inspect claude mcp list and /mcp status.

{
  "mcpServers": {
    "mcp-server-qdrant": {
      "type": "stdio",
      "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>"
      }
    }
  }
}

claude mcp add-json --scope project 'mcp-server-qdrant' '{"type":"stdio","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 Code

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

qdrant-store

For Qdrant's qdrant-store, review the permission request and arguments in Claude Code before approval.

Save information with optional JSON metadata in a Qdrant collection.

qdrant-find

For Qdrant's qdrant-find, review the permission request and arguments in Claude Code before approval.

Qdrant: full stored tool descriptions

Troubleshooting Qdrant in Claude Code

• If Qdrant MCP Server fails to start, check uvx mcp-server-qdrant (from uv, for Python tools), the working directory, and Claude Code's selected scope; inspect claude mcp list and /mcp.
• Qdrant MCP Server: check COLLECTION_NAME, EMBEDDING_MODEL, QDRANT_API_KEY, QDRANT_URL; keep credentials out of shared .mcp.json.
• Qdrant MCP Server uses stdio here: Claude Code 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 Code troubleshooting lives in the /clients/claude-code guide.

Frequently asked questions