Qdrant MCP Server for VS Code: Setup & Config

What you can do with Qdrant in VS Code

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

• Store facts that an assistant can retrieve later.
• Keep metadata alongside semantic memories.

Before you start: Qdrant in VS 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 VS Code configuration

1. Choose VS Code configuration scope

   For Qdrant MCP Server, open Workspace: .vscode/mcp.json. Merge into servers; preserve existing inputs.

2. Add Qdrant MCP Server to VS Code

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

3. Check Qdrant MCP Server in VS Code

   Qdrant MCP Server: Start in VS Code’s MCP controls; inspect output and trust prompts.

{
  "servers": {
    "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 VS Code

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

qdrant-store

Look for qdrant-store among VS Code's agent-mode tools after starting Qdrant through the MCP controls.

Save information with optional JSON metadata in a Qdrant collection.

qdrant-find

Look for qdrant-find among VS Code's agent-mode tools after starting Qdrant through the MCP controls.

Qdrant: full stored tool descriptions

Troubleshooting Qdrant in VS Code

• Make uvx mcp-server-qdrant (from uv, for Python tools) available in the workspace, container, or remote environment hosting Qdrant MCP Server. Start through VS Code's MCP controls; inspect output and trust prompts.
• For Qdrant MCP Server, keep COLLECTION_NAME, EMBEDDING_MODEL, QDRANT_API_KEY, QDRANT_URL out of version control; VS Code documents input variables and secret handling.
• Qdrant MCP Server uses stdio here: VS 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 VS Code troubleshooting lives in the /clients/vscode guide.

Frequently asked questions