Qdrant MCP Server for Cursor: Setup & Config

What you can do with Qdrant in Cursor

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

• Keep metadata alongside semantic memories.
• Share a remotely reachable memory server with an MCP workflow.

Before you start: Qdrant in Cursor

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

1. Choose Cursor configuration scope

   For Qdrant MCP Server, open Project: .cursor/mcp.json User: ~/.cursor/mcp.json. Merge into mcpServers at project or user scope.

2. Add Qdrant MCP Server to Cursor

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

3. Check Qdrant MCP Server in Cursor

   Qdrant MCP Server: Enable in Cursor’s MCP settings; inspect tools.

{
  "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 Cursor

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

qdrant-store

Find qdrant-store under Qdrant in Cursor's MCP settings; inspect its arguments when the agent requests a call.

qdrant-find

Find qdrant-find under Qdrant in Cursor's MCP settings; inspect its arguments when the agent requests a call.

Retrieve stored information relevant to a semantic query.

Qdrant: full stored tool descriptions

Troubleshooting Qdrant in Cursor

• Cursor must find uvx mcp-server-qdrant (from uv, for Python tools) for Qdrant MCP Server. Enable the project/user entry in MCP settings and inspect its tools.
• Review COLLECTION_NAME, EMBEDDING_MODEL, QDRANT_API_KEY, QDRANT_URL for Qdrant MCP Server before sharing project .cursor/mcp.json; project scope travels with the repository.
• Qdrant MCP Server uses stdio here: Cursor 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 Cursor troubleshooting lives in the /clients/cursor guide.

Frequently asked questions