qdrant-llamaindex-mcp-server: LlamaIndex-Compatible Qdrant MCP Server

The Model Context Protocol (MCP) is an open protocol that enables seamless integration between LLM applications and external data sources and tools. Whether you're building an AI-powered IDE, enhancing a chat interface, or creating custom AI workflows, MCP provides a standardized way to connect LLMs with the context they need.

This repository is a fork of qdrant/mcp-server-qdrant specifically designed to work with documents stored by LlamaIndex in Qdrant vector databases.

⚠️ Important Differences from Official Server

This fork has breaking changes compared to the official qdrant/mcp-server-qdrant:

• 🔧 Many More Tools: Provides 10+ tools vs. the official server's basic find/store tools

• 🎯 Dynamic Collection Selection: Collection names are specified at runtime by MCP clients, not hardcoded in configuration

• 🤖 Dynamic Embedding Model Detection: Automatically detects and loads the correct embedding model for each collection

• 📚 LlamaIndex Compatibility: Adapts to different content field names and metadata structures used by LlamaIndex

• 🔒 Enhanced Security: Built-in embedding model whitelist to prevent accidental loading of large models

These changes make configurations incompatible with the official server. You cannot simply swap this server for the official one without updating your configuration and workflow.

Related MCP server: qdrant-mcp

Overview

A comprehensive Model Context Protocol server for working with documents stored by LlamaIndex in Qdrant vector databases. Unlike the original server which provides basic functionality with a fixed document structure, this version offers extensive tooling and automatically adapts to different payload formats used by LlamaIndex.

Key Features

• LlamaIndex Compatibility: Automatically detects and adapts to different content field names (text, document, _node_content, etc.)

• Dynamic Embedding Model Detection: Automatically detects and uses the correct embedding model for each collection based on its vector configuration

• Embedding Model Whitelist: Built-in safety mechanism to prevent accidentally loading large models

• Flexible Metadata Handling: Works with both flat and nested metadata structures

• Read-Only Access: Designed specifically for querying existing LlamaIndex-indexed data

• Smart Content Detection: Automatically identifies the most likely content field when standard names aren't found

Tools

Read-Only Tools (Available with QDRANT_READ_ONLY=true)

1. qdrant-find - Search and retrieve documents stored by LlamaIndex in Qdrant

   • query (string): Semantic search query

   • collection_name (string): Name of the collection to search

   • Returns: Relevant documents with content and metadata

2. qdrant-get-point - Get a specific point by its ID

   • point_id (string): The ID of the point to retrieve

   • collection_name (string): The collection to get the point from

   • Returns: Point information with content and metadata

3. qdrant-get-collections - Get a list of all collections

   • Returns: Array of collection names in the Qdrant server

4. qdrant-get-collection-details - Get detailed information about a collection

   • collection_name (string): The name of the collection

   • Returns: Collection configuration, statistics, and status

5. qdrant-get-collection-count - Get the number of points in a collection

   • collection_name (string): The name of the collection

   • Returns: Number of points in the collection

6. qdrant-peek-collection - Preview sample points from a collection

   • collection_name (string): The name of the collection

   • limit (int, optional): Maximum number of points to return (default: 10)

   • Returns: Sample points from the collection

7. qdrant-get-documents - Retrieve multiple documents by their IDs

   • point_ids (array of strings): List of point IDs to retrieve

   • collection_name (string): The collection to get documents from

   • Returns: Array of found documents

8. qdrant-search-by-vector - Search using a raw vector instead of text query

   • vector (array of floats): The query vector to search with

   • collection_name (string): The collection to search in

   • limit (int, optional): Maximum number of results to return (default: 10)

   • Returns: Relevant documents based on vector similarity

9. qdrant-list-document-ids - List document IDs with pagination

   • collection_name (string): The collection to list IDs from

   • limit (int, optional): Maximum number of IDs to return (default: 100)

   • offset (int, optional): Number of IDs to skip for pagination (default: 0)

   • Returns: Array of document IDs

10. qdrant-scroll-points - Paginated retrieval of points using scroll

    • collection_name (string): The collection to scroll through

    • limit (int, optional): Maximum number of points to return (default: 10)

    • offset (int, optional): Offset for pagination

    • Returns: Points with pagination info

Write Tools (Available when QDRANT_READ_ONLY=false)

When read-only mode is disabled, additional tools become available for modifying data:

• qdrant-store - Store new documents in Qdrant

• qdrant-delete-point - Delete a specific point by ID

• qdrant-update-point-payload - Update point metadata

• qdrant-create-collection - Create new collections

• qdrant-delete-collection - Delete entire collections

• qdrant-add-documents - Batch add multiple documents

• qdrant-delete-documents - Batch delete multiple documents

Environment Variables

The configuration of the server is done using environment variables:

Note: You cannot provide both QDRANT_URL and QDRANT_LOCAL_PATH at the same time.

FastMCP Environment Variables

Since mcp-server-qdrant is based on FastMCP, it also supports all the FastMCP environment variables. The most important ones are listed below:

Dynamic Embedding Model Detection

This server automatically detects which embedding model was used for each collection and uses the appropriate model for queries. This is especially useful when you have multiple collections created with different embedding models.

How It Works

1. Collection Creation: When LlamaIndex creates a collection, the full model name is stored as the vector name (e.g., "BAAI/bge-small-en-v1.5")

2. Query Time: When searching a collection, the server:

   • Inspects the collection's vector configuration

   • Extracts the model name from the vector name

   • Loads the appropriate embedding model (with caching for performance)

   • Uses that model to embed the query

Embedding Model Whitelist

For security and resource management, the server includes a built-in whitelist of allowed embedding models. By default, only small, efficient models are permitted:

• sentence-transformers/all-MiniLM-L6-v2 (384 dims, ~90MB)

• BAAI/bge-small-en-v1.5 (384 dims, ~67MB)

• snowflake/snowflake-arctic-embed-xs (384 dims, ~90MB)

• jinaai/jina-embeddings-v2-small-en (512 dims, ~120MB)

Customizing the Whitelist

Using Environment Variables

# Allow only specific models
export EMBEDDING_ALLOWED_MODELS='["sentence-transformers/all-MiniLM-L6-v2", "BAAI/bge-small-en-v1.5"]'

# Allow all models (removes safety protection)
export EMBEDDING_ALLOWED_MODELS='null'

In Claude Desktop Config

{
  "mcpServers": {
    "qdrant": {
      "command": "uvx",
      "args": ["qdrant-llamaindex-mcp-server"],
      "env": {
        "QDRANT_URL": "http://localhost:6333",
        "COLLECTION_NAME": "your-collection",
        "EMBEDDING_ALLOWED_MODELS": "[\"sentence-transformers/all-MiniLM-L6-v2\", \"BAAI/bge-small-en-v1.5\"]"
      }
    }
  }
}

Behavior with Blocked Models

When the server encounters a collection using a model not in the whitelist:

• ⚠️ Logs a warning message

• 🔄 Falls back to the default configured model (EMBEDDING_MODEL)

• ✅ Continues operating normally

This ensures your system remains stable while preventing accidental downloads of large models.

Installation

Using uvx (Recommended)

From PyPI

QDRANT_URL="http://localhost:6333" \
uvx qdrant-llamaindex-mcp-server

From GitHub Repository (Development)

QDRANT_URL="http://localhost:6333" \
uvx --from git+https://github.com/azhang/qdrant-llamaindex-mcp-server.git qdrant-llamaindex-mcp-server

From Local Directory (Development)

# Clone and run locally
git clone https://github.com/azhang/qdrant-llamaindex-mcp-server.git
cd qdrant-llamaindex-mcp-server

QDRANT_URL="http://localhost:6333" \
uvx --from . qdrant-llamaindex-mcp-server

Transport Protocols

The server supports different transport protocols that can be specified using the --transport flag:

QDRANT_URL="http://localhost:6333" \
uvx qdrant-llamaindex-mcp-server --transport sse

Supported transport protocols:

• stdio (default): Standard input/output transport, might only be used by local MCP clients

• sse: Server-Sent Events transport, perfect for remote clients

• streamable-http: Streamable HTTP transport, perfect for remote clients, more recent than SSE

The default transport is stdio if not specified.

When SSE transport is used, the server will listen on the specified port and wait for incoming connections. The default port is 8000, however it can be changed using the FASTMCP_PORT environment variable.

QDRANT_URL="http://localhost:6333" \
FASTMCP_PORT=1234 \
uvx qdrant-llamaindex-mcp-server --transport sse

Using Docker

A Dockerfile is available for building and running the MCP server:

# Build the container
docker build -t mcp-server-qdrant .

# Run the container
docker run -p 8000:8000 \
  -e FASTMCP_HOST="0.0.0.0" \
  -e QDRANT_URL="http://your-qdrant-server:6333" \
  -e QDRANT_API_KEY="your-api-key" \
  -e COLLECTION_NAME="your-collection" \
  mcp-server-qdrant

Installing via Smithery

To install Qdrant MCP Server for Claude Desktop automatically via Smithery:

npx @smithery/cli install mcp-server-qdrant --client claude

Manual configuration of Claude Desktop

To use this server with the Claude Desktop app, add the following configuration to the "mcpServers" section of your claude_desktop_config.json:

{
  "qdrant": {
    "command": "uvx",
    "args": ["qdrant-llamaindex-mcp-server"],
    "env": {
      "QDRANT_URL": "https://xyz-example.eu-central.aws.cloud.qdrant.io:6333",
      "QDRANT_API_KEY": "your_api_key",
      "QDRANT_READ_ONLY": "true"
    }
  }
}

For local Qdrant mode:

{
  "qdrant": {
    "command": "uvx",
    "args": ["qdrant-llamaindex-mcp-server"],
    "env": {
      "QDRANT_LOCAL_PATH": "/path/to/qdrant/database",
      "QDRANT_READ_ONLY": "true"
    }
  }
}

By default, the server will use the sentence-transformers/all-MiniLM-L6-v2 embedding model to encode memories. For the time being, only FastEmbed models are supported.

Support for other tools

This MCP server can be used with any MCP-compatible client. For example, you can use it with Cursor and VS Code, which provide built-in support for the Model Context Protocol.

Using with Cursor/Windsurf

You can configure this MCP server to work as a code search tool for Cursor or Windsurf by customizing the tool descriptions:

QDRANT_URL="http://localhost:6333" \
TOOL_STORE_DESCRIPTION="Store reusable code snippets for later retrieval. \
The 'information' parameter should contain a natural language description of what the code does, \
while the actual code should be included in the 'metadata' parameter as a 'code' property. \
The value of 'metadata' is a Python dictionary with strings as keys. \
Use this whenever you generate some code snippet." \
TOOL_FIND_DESCRIPTION="Search for relevant code snippets based on natural language descriptions. \
The 'query' parameter should describe what you're looking for, \
and the tool will return the most relevant code snippets. \
Use this when you need to find existing code snippets for reuse or reference." \
uvx qdrant-llamaindex-mcp-server --transport sse # Enable SSE transport

In Cursor/Windsurf, you can then configure the MCP server in your settings by pointing to this running server using SSE transport protocol. The description on how to add an MCP server to Cursor can be found in the Cursor documentation. If you are running Cursor/Windsurf locally, you can use the following URL:

http://localhost:8000/sse

This configuration transforms the Qdrant MCP server into a specialized code search tool that can:

1. Store code snippets, documentation, and implementation details

2. Retrieve relevant code examples based on semantic search

3. Help developers find specific implementations or usage patterns

You can populate the database by storing natural language descriptions of code snippets (in the information parameter) along with the actual code (in the metadata.code property), and then search for them using natural language queries that describe what you're looking for.

If you have successfully installed the mcp-server-qdrant, but still can't get it to work with Cursor, please consider creating the Cursor rules so the MCP tools are always used when the agent produces a new code snippet. You can restrict the rules to only work for certain file types, to avoid using the MCP server for the documentation or other types of content.

Using with Claude Code

You can enhance Claude Code's capabilities by connecting it to this MCP server, enabling semantic search over your existing codebase.

Setting up qdrant-llamaindex-mcp-server

1. Add the MCP server to Claude Code:

   # Add qdrant-llamaindex-mcp-server configured for code search
   claude mcp add code-search \
   -e QDRANT_URL="http://localhost:6333" \
   -e QDRANT_READ_ONLY="true" \
   -e TOOL_STORE_DESCRIPTION="Store code snippets with descriptions. The 'information' parameter should contain a natural language description of what the code does, while the actual code should be included in the 'metadata' parameter as a 'code' property." \
   -e TOOL_FIND_DESCRIPTION="Search for relevant code snippets using natural language. The 'query' parameter should describe the functionality you're looking for." \
   -- uvx qdrant-llamaindex-mcp-server

2. Verify the server was added:

   claude mcp list

Using Semantic Code Search in Claude Code

Tool descriptions, specified in TOOL_STORE_DESCRIPTION and TOOL_FIND_DESCRIPTION, guide Claude Code on how to use the MCP server. The ones provided above are examples and may need to be customized for your specific use case. However, Claude Code should be already able to:

1. Use the qdrant-store tool to store code snippets with descriptions.

2. Use the qdrant-find tool to search for relevant code snippets using natural language.

Run MCP server in Development Mode

The MCP server can be run in development mode using the mcp dev command. This will start the server and open the MCP inspector in your browser.

fastmcp dev src/mcp_server_qdrant/server.py

Using with VS Code

For one-click installation, click one of the install buttons below:

Manual Installation

Add the following JSON block to your User Settings (JSON) file in VS Code. You can do this by pressing Ctrl + Shift + P and typing Preferences: Open User Settings (JSON).

{
  "mcp": {
    "inputs": [
      {
        "type": "promptString",
        "id": "qdrantUrl",
        "description": "Qdrant URL"
      },
      {
        "type": "promptString",
        "id": "qdrantApiKey",
        "description": "Qdrant API Key",
        "password": true
      },
      {
        "type": "promptString",
        "id": "collectionName",
        "description": "Collection Name"
      }
    ],
    "servers": {
      "qdrant": {
        "command": "uvx",
        "args": ["qdrant-llamaindex-mcp-server"],
        "env": {
          "QDRANT_URL": "${input:qdrantUrl}",
          "QDRANT_API_KEY": "${input:qdrantApiKey}",
          "COLLECTION_NAME": "${input:collectionName}"
        }
      }
    }
  }
}

Or if you prefer using Docker, add this configuration instead:

{
  "mcp": {
    "inputs": [
      {
        "type": "promptString",
        "id": "qdrantUrl",
        "description": "Qdrant URL"
      },
      {
        "type": "promptString",
        "id": "qdrantApiKey",
        "description": "Qdrant API Key",
        "password": true
      },
      {
        "type": "promptString",
        "id": "collectionName",
        "description": "Collection Name"
      }
    ],
    "servers": {
      "qdrant": {
        "command": "docker",
        "args": [
          "run",
          "-p", "8000:8000",
          "-i",
          "--rm",
          "-e", "QDRANT_URL",
          "-e", "QDRANT_API_KEY",
          "-e", "COLLECTION_NAME",
          "qdrant-llamaindex-mcp-server"
        ],
        "env": {
          "QDRANT_URL": "${input:qdrantUrl}",
          "QDRANT_API_KEY": "${input:qdrantApiKey}",
          "COLLECTION_NAME": "${input:collectionName}"
        }
      }
    }
  }
}

Alternatively, you can create a .vscode/mcp.json file in your workspace with the following content:

{
  "inputs": [
    {
      "type": "promptString",
      "id": "qdrantUrl",
      "description": "Qdrant URL"
    },
    {
      "type": "promptString",
      "id": "qdrantApiKey",
      "description": "Qdrant API Key",
      "password": true
    },
    {
      "type": "promptString",
      "id": "collectionName",
      "description": "Collection Name"
    }
  ],
  "servers": {
    "qdrant": {
      "command": "uvx",
      "args": ["qdrant-llamaindex-mcp-server"],
      "env": {
        "QDRANT_URL": "${input:qdrantUrl}",
        "QDRANT_API_KEY": "${input:qdrantApiKey}",
        "COLLECTION_NAME": "${input:collectionName}"
      }
    }
  }
}

For workspace configuration with Docker, use this in .vscode/mcp.json:

{
  "inputs": [
    {
      "type": "promptString",
      "id": "qdrantUrl",
      "description": "Qdrant URL"
    },
    {
      "type": "promptString",
      "id": "qdrantApiKey",
      "description": "Qdrant API Key",
      "password": true
    },
    {
      "type": "promptString",
      "id": "collectionName",
      "description": "Collection Name"
    }
  ],
  "servers": {
    "qdrant": {
      "command": "docker",
      "args": [
        "run",
        "-p", "8000:8000",
        "-i",
        "--rm",
        "-e", "QDRANT_URL",
        "-e", "QDRANT_API_KEY",
        "-e", "COLLECTION_NAME",
        "qdrant-llamaindex-mcp-server"
      ],
      "env": {
        "QDRANT_URL": "${input:qdrantUrl}",
        "QDRANT_API_KEY": "${input:qdrantApiKey}",
        "COLLECTION_NAME": "${input:collectionName}"
      }
    }
  }
}

Contributing

If you have suggestions for how mcp-server-qdrant could be improved, or want to report a bug, open an issue! We'd love all and any contributions.

Testing qdrant-llamaindex-mcp-server locally

The MCP inspector is a developer tool for testing and debugging MCP servers. It runs both a client UI (default port 5173) and an MCP proxy server (default port 3000). Open the client UI in your browser to use the inspector.

QDRANT_URL=":memory:" \
fastmcp dev src/mcp_server_qdrant/server.py

Once started, open your browser to http://localhost:5173 to access the inspector interface.

License

This MCP server is licensed under the Apache License 2.0. This means you are free to use, modify, and distribute the software, subject to the terms and conditions of the Apache License 2.0. For more details, please see the LICENSE file in the project repository.