pickfit

BrowseMCP servers

mcp-server-qdrant

An MCP server that stores and retrieves memories in the Qdrant vector search engine, acting as a semantic memory layer.

Use it

Before you install: known vulnerabilities

pickfit found 5 known high or critical vulnerabilities in the packages a fresh install brings (OSV.dev, 16 Nov 2026). Weigh this before you install it.

  • pypi:fastmcp 2.7.0 FastMCP OpenAPI Provider has an SSRF & Path Traversal Vulnerability (GHSA-vv7q-7jx5-f767, critical, fixed in 3.2.0)
See 4 more

Linux x86_64

  1. uv tool install mcp-server-qdrant and pre-download the default FastEmbed model so the server works offline

    uv tool install mcp-server-qdrant && ~/.local/share/uv/tools/mcp-server-qdrant/bin/python -c "from fastembed import TextEmbedding; m=TextEmbedding('sentence-transformers/all-MiniLM-L6-v2'); print(len(list(m.embed(['hi']))[0]))"

Add it to your agent

claude mcp add mcp-server-qdrant -- mcp-server-qdrant
JSON for Claude Desktop, Cursor and other clients
{
  "mcpServers": {
    "mcp-server-qdrant": {
      "command": "mcp-server-qdrant",
      "args": []
    }
  }
}

Add mcp-server-qdrant as a server in your MCP client, setting QDRANT_LOCAL_PATH (or a Qdrant URL) and COLLECTION_NAME in its environment, and the client will list the qdrant-store and qdrant-find to

What it does

  • Store information in a Qdrant collection
    How to use it
    1. Start mcp-server-qdrant from your MCP client with QDRANT_LOCAL_PATH=<folder> and COLLECTION_NAME=<collection> set in its environment.
    2. Call the qdrant-store tool with an information text and optional metadata.
    Tested
  • Find stored information by meaning
    How to use it
    1. Store some information with the qdrant-store tool.
    2. Call the qdrant-find tool with a query written in plain language, such as <your question>.
    Tested
  • Search code snippets by meaning for coding agents
    How to use it
    1. Start mcp-server-qdrant with COLLECTION_NAME=<collection>, and set TOOL_STORE_DESCRIPTION and TOOL_FIND_DESCRIPTION to describe storing and finding code snippets.
    2. Call qdrant-store with a description in information and the code in metadata, such as {"code": "<your code>"}.
    3. Call qdrant-find with a query describing the code you need.
    Tested

How far pickfit got

Linux x86_64

  1. Installs
  2. Connects
  3. 3 of 3 features work
  4. Works offline

Good for

  • store code snippets for later retrieval
  • search code examples semantically

How pickfit tested it

Each run starts from a clean machine and follows the steps above. How pickfit verifies

Linux x86_64

An MCP client called one of its tools

  • Replayed from scratch
  • Works offline
  • Checked on 15 Nov 2026
  • Version 0.8.1

An MCP client handshake over stdio listed 2 tools, and a call to qdrant-store returned a result.

Differences the test machine hit

  • README: Examples use QDRANT_URL=http://localhost:6333 (a running Qdrant server)
    In the test: Used QDRANT_LOCAL_PATH=/tmp/qdrant-db (embedded local mode, documented in the README) because no Qdrant server runs here
  • README: uvx mcp-server-qdrant needs no specific installation
    In the test: On first use the server downloads the FastEmbed model sentence-transformers/all-MiniLM-L6-v2 from Hugging Face. To make it work offline, the model was downloaded ahead of time in the install step.
  • README: Code search example uses --transport sse for Cursor/Windsurf
    In the test: Tested the same store/find with custom tool descriptions over stdio

How to read a tool card

Stitching
pickfit installed this tool itself. Everything under the stitches comes from that run. A tool pickfit has not run never gets stitches.
Verified on your OS
The install steps ran on the system you chose. “Ran on Linux only” means it has not been run on yours yet.
macOS, Linux and WindowsWhere it ran
Green OS marks: pickfit ran the install steps there. Grey ones: the README says it runs there, and pickfit has not tried.
How far the run got
Installs and starts, its main function works, its service answers, it produces model output. A window means a desktop app opened; a plug, an MCP client used it. The mark sits beside the run’s result, under “Why it fits and how we know” and in “How pickfit tested it”.
Visual check
pickfit looked at screenshots of the app. Green: it looks right. Amber with a number: things that look wrong; open it to see them. Grey and dashed: not checked yet.
Known vulnerabilities
Known high or critical vulnerabilities (OSV.dev) in what it installs. Green: none known. Red with a number: how many; open it for the list, and read it before you install. Grey and dashed: not checked, which does not mean safe.
About the run
The day it ran, and the version that ran.
Source of a reason
Every reason a pick fits rests on one profile field. Open the reason to see the field and the value it relies on.
Hidden gem
High quality, little known.
Quality and popularity
Two scores out of 100. Quality: how well it installed and worked when pickfit tried it, and how good its install docs and upkeep are. Popularity: from stars, downloads and Hacker News.
Features checked
Of the main features the README advertises, how many the run actually exercised (green), and how many failed (red). Grey ones were not checked, and the card says why.
Not verified
A well-known tool Fitz mentions from general knowledge. No run record, no steps, no score.