Qdrant Rag MCP Server

A context-aware Model Context Protocol (MCP) server that provides semantic search capabilities across your codebase using Qdrant vector database. Now

Local serverstdioPython

What is the Qdrant Rag MCP MCP server?

Qdrant Rag MCP MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. A context-aware Model Context Protocol (MCP) server that provides semantic search capabilities across your codebase using Qdrant vector database. Now with intelligent GitHub issue resolution (v0.3.0), GitHub Projects V2 management.

What the assistant can call

Once Qdrant Rag MCP is connected, these are the calls the assistant has available:

  • Prerequisites — The Prerequisites tool exposed by this server
  • Installation — The Installation tool exposed by this server
  • Configuration — Control logging via environment variables: bash export QDRANT_LOG_LEVEL=DEBUG # Set log level export QDRANT_LOG_DIR=/custom/path # Custom log

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

Configuration and credentials

You will need 4 environment variables: MCP_CLIENT_CWD, QDRANT_RAG_AUTO_INDEX, QDRANT_LOG_LEVEL, QDRANT_LOG_DIR. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

  • Claude Code CLI - Docker - Python 3.10+ with uv (ultraviolet package manager)

Choosing this one

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Qdrant Rag MCP's toolset — Prerequisites, Installation, Configuration — is a fair guide to whether it matches your workflow. It is maintained by ancoleman; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the qdrant rag mcp mcp server does with a few real requests.

Available tools

ToolWhat it does
PrerequisitesThe Prerequisites tool exposed by this server.
InstallationThe Installation tool exposed by this server.
ConfigurationControl logging via environment variables: bash export QDRANT_LOG_LEVEL=DEBUG # Set log level export QDRANT_LOG_DIR=/custom/path # Custom log directory

How to install the Qdrant Rag MCP MCP server

{
  "mcpServers": {
    "qdrant-rag": {
      "command": "python",
      "args": ["/path/to/qdrant-rag/src/qdrant_mcp_context_aware.py"],
      "env": {
        "MCP_CLIENT_CWD": "${workspaceFolder}"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

  • Claude Code CLI - Docker - Python 3.10+ with uv (ultraviolet package manager)
VariableDescriptionRequired
MCP_CLIENT_CWDConfiguration value read at startup.Optional
QDRANT_RAG_AUTO_INDEXConfiguration value read at startup.Optional
QDRANT_LOG_LEVELConfiguration value read at startup.Optional
QDRANT_LOG_DIRFilesystem location the server is allowed to use.Optional

Example prompts to try

  • Use Qdrant Rag MCP to Prerequisites.
  • Use Qdrant Rag MCP to Installation.
  • Use Qdrant Rag MCP to Configuration.

Frequently asked questions

It connects Qdrant Rag MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 3 tools (Prerequisites, Installation, Configuration) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Qdrant Rag MCP directly.