Data as of

Qdrant MCP Server for Windsurf: Setup & Config

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

What you can do with Qdrant in Windsurf

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

  • Find reusable code snippets from natural-language descriptions.
  • Share a remotely reachable memory server with an MCP workflow.

Before you start: Qdrant in Windsurf

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

  1. Choose Windsurf configuration scope

    For Qdrant MCP Server, open macOS/Linux: ~/.codeium/windsurf/mcp_config.json Windows: %USERPROFILE%\.codeium\windsurf\mcp_config.json. Merge into mcpServers; remote endpoints use serverUrl.

  2. Add Qdrant MCP Server to Windsurf

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

  3. Check Qdrant MCP Server in Windsurf

    Qdrant MCP Server: Refresh MCP in Windsurf settings and inspect Cascade’s tools.

Config file · macOS/Linux: ~/.codeium/windsurf/mcp_config.json

Windows: %USERPROFILE%\.codeium\windsurf\mcp_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 Windsurf

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

qdrant-store

After refreshing Qdrant in Windsurf settings, check Cascade's tool list for qdrant-store.

qdrant-find

After refreshing Qdrant in Windsurf settings, check Cascade's tool list for qdrant-find.

Retrieve stored information relevant to a semantic query.

Qdrant: full stored tool descriptions

Troubleshooting Qdrant in Windsurf

  • Check uvx mcp-server-qdrant (from uv, for Python tools) on the machine running Windsurf's MCP integration for Qdrant MCP Server; refresh MCP and inspect Cascade's tools.
  • Check COLLECTION_NAME, EMBEDDING_MODEL, QDRANT_API_KEY, QDRANT_URL for Qdrant MCP Server; do not bypass a Windsurf permission error with a broad administrator token.
  • Qdrant MCP Server uses stdio here: Windsurf 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 Windsurf troubleshooting lives in the /clients/windsurf guide.

Qdrant MCP Server — details. Windsurf guide

Frequently asked questions

Windsurf reads Qdrant MCP Server under mcpServers in ~/.codeium/windsurf/mcp_config.json on macOS/Linux; Windows uses %USERPROFILE%\.codeium\windsurf\mcp_config.json.

Windsurf's mcp-server-qdrant example uses stdio.

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

Windsurf'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 Windsurf'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.

Yes. SSE and streamable HTTP are documented in addition to the default stdio mode.