qdrant-full-mcp 0.4.1

The complete Qdrant MCP server. Manage Qdrant Cloud and your vector data from Claude Code, Codex, Cursor, VS Code or any MCP client, in plain English.

Quick start · Features · How it works · Comparison · FAQ

qdrant-full-mcp is an open-source Model Context Protocol (MCP) server for the Qdrant vector database. It gives AI coding agents 43 tools to run Qdrant end to end: Qdrant Cloud management (clusters, backups, API keys), data operations (collections, upserts, dense, sparse and hybrid search, payload indexes) and plain-text memory with local embeddings. It does everything the official mcp-server-qdrant does, and adds infrastructure management and safety rails on top.

Zero to a working RAG store in one chat "Create a free Qdrant cluster in Mumbai, store these notes, then find what we said about refunds." The agent creates the cluster, creates a database key, asks once whether to remember it, stores your text and searches it. No console, no config edits, no restart.

Features

Quick start

1. Get a key. In the Qdrant Cloud console: Access Management → Cloud Management Keys → create one. That is the only setting you need; the account is detected automatically.

2. Download once. Requires uv. The first run fetches dependencies (about 40 seconds, then cached), which is longer than some clients wait for a server to start:

uvx qdrant-full-mcp --help

_{On a slow connection: UV_HTTP_TIMEOUT=180 uvx qdrant-full-mcp --help (PowerShell: $env:UV_HTTP_TIMEOUT=180; uvx qdrant-full-mcp --help).}

3. Add it to your AI client.

Claude Code

claude mcp add qdrant -e QDRANT_CLOUD_API_KEY=your-management-key -- uvx qdrant-full-mcp

Check with claude mcp list or /mcp, then ask: "List my Qdrant Cloud clusters."

/plugin marketplace add Jeevav62/qdrant-full-mcp
/plugin install qdrant@qdrant-full-mcp

OpenAI Codex

codex mcp add qdrant --env QDRANT_CLOUD_API_KEY=your-management-key -- uvx qdrant-full-mcp

[mcp_servers.qdrant]
command = "uvx"
args = ["qdrant-full-mcp"]
startup_timeout_sec = 60

[mcp_servers.qdrant.env]
QDRANT_CLOUD_API_KEY = "your-management-key"

{
  "mcpServers": {
    "qdrant": {
      "command": "uvx",
      "args": ["qdrant-full-mcp"],
      "env": { "QDRANT_CLOUD_API_KEY": "your-management-key" }
    }
  }
}

{
  "servers": {
    "qdrant": {
      "type": "stdio",
      "command": "uvx",
      "args": ["qdrant-full-mcp"],
      "env": { "QDRANT_CLOUD_API_KEY": "your-management-key" }
    }
  }
}

git clone https://github.com/Jeevav62/qdrant-full-mcp
claude mcp add qdrant -e QDRANT_CLOUD_API_KEY=your-management-key -- uv run --project ./qdrant-full-mcp qdrant-full-mcp

How it works

flowchart LR
    A["Claude Code, Codex, Cursor, VS Code"] -->|"MCP: stdio or HTTP"| B["qdrant-full-mcp"]
    B -->|"Cloud management key"| C["Qdrant Cloud API<br/>clusters, backups, keys"]
    B -->|"database key, created and remembered"| D["Qdrant cluster<br/>collections, search"]
    B -->|"QDRANT_LOCAL_PATH"| E["Local Qdrant<br/>no server needed"]
    B -.->|"FastEmbed"| F["Local embeddings<br/>store_text, find_text"]

• Two credentials, handled for you. The Cloud management key runs infrastructure; Qdrant does not let it read data. When the agent creates a database key with create_database_api_key, the server remembers it for that cluster, so data tools work at once. The agent asks whether to save it on this machine; if you agree, every later session in any MCP client uses it (%APPDATA%\qdrant-full-mcp\keys.json on Windows, ~/.config/qdrant-full-mcp/keys.json elsewhere, file mode 600, never printed). Keys you set yourself (QDRANT_API_KEY_<CLUSTER_ID>, QDRANT_API_KEY) always take priority.
• Endpoints are looked up for you. Pass cluster_id to any data tool. For self-hosted Qdrant, set QDRANT_URL and QDRANT_API_KEY instead.

Use cases

• Build a RAG backend from chat: create a cluster, a collection with dense and sparse vectors, a payload index, and run hybrid search to test retrieval quality.
• Give your agent long-term memory: set COLLECTION_NAME=memory and say "remember that…" / "what do we know about…".
• Operate production safely: scale clusters, schedule backups, rotate keys, and inspect collections with dry runs and exact-name confirmations.
• Learn vector search locally: QDRANT_LOCAL_PATH=./qdrant-data, no account and no server.

Plain-text memory (store and find)

store_text and find_text embed text on your machine with FastEmbed, the same approach as the official server, so you never handle vectors. For an agent memory with one default collection:

claude mcp add qdrant -e QDRANT_URL=https://your-cluster:6333 -e QDRANT_API_KEY=db-key -e COLLECTION_NAME=memory -- uvx qdrant-full-mcp

• Stores into COLLECTION_NAME happen in one step and create the collection on first use; other collections keep the dry-run-then-confirm flow.
• Default model sentence-transformers/all-MiniLM-L6-v2 (384 dimensions, about 90 MB on first use); change it with EMBEDDING_MODEL.
• Same layout as the official server (named vector fast-<model>, payload {"document", "metadata"}), so both servers can share a collection.
• TOOL_STORE_DESCRIPTION / TOOL_FIND_DESCRIPTION customize the tools (for example, a code-snippet library); QDRANT_SEARCH_LIMIT sets the default result count.
• On Qdrant Cloud, a field you filter on needs a payload index; if it is missing, the error tells the agent the exact create_payload_index call that fixes it.

Run as an HTTP server or in Docker

qdrant-full-mcp --transport streamable-http --port 8000   # http://127.0.0.1:8000/mcp
qdrant-full-mcp --transport sse                           # older SSE clients

docker build -t qdrant-full-mcp .
docker run -p 127.0.0.1:8000:8000 -e QDRANT_URL=https://your-cluster:6333 -e QDRANT_API_KEY=db-key -e COLLECTION_NAME=memory qdrant-full-mcp

The server binds to 127.0.0.1 by default and has no built-in authentication while holding your Qdrant keys. If you expose it (--host 0.0.0.0), put an authenticating proxy in front. The Docker image includes the default embedding model and runs as a non-root user.

Example prompts

• "List my Qdrant Cloud clusters." · "Show the available AWS regions and prices."
• "Create a Qdrant cluster in AWS London with the smallest paid package." (shows the price, waits for approval)
• "Scale cluster X to 3 nodes." · "Suspend cluster X."
• "Back up cluster X every day at 3am and keep backups for 14 days."
• "Restore backup Y into a new cluster called restored-1."
• "Make a database key for cluster X and save it on this machine."
• "Create a collection docs with a 768-dim dense vector and a sparse vector for hybrid search."
• "Add a keyword index on tenant_id in docs." · "How many points are in docs?"
• "Store these three FAQ answers in faq." · "Search faq for how refunds work."
• "Delete cluster old-test." (you confirm the exact name)

Compared with the official Qdrant MCP server

Both servers use the same collection layout for text, so you can switch or run them side by side.

Tools

Safety and security

• Every mutating tool is a dry run unless confirm=true, and tool descriptions tell the agent to get your approval.
• Irreversible actions need the exact name: delete_cluster and restore_backup (confirm_cluster_name), delete_collection (confirm_collection_name).
• QDRANT_MCP_READ_ONLY=1 (or QDRANT_READ_ONLY=1) blocks every write; QDRANT_MCP_MODULES loads only the modules you list (cloud, data, text).
• Keys come from your environment or the opt-in key file, are never logged or echoed, and saved keys are removed when the key or cluster is deleted. QDRANT_MCP_KEY_FILE=off never writes keys to disk.
• Ids and paths are validated before any request. Prefer least-privilege keys.

Configuration

FAQ

What is qdrant-full-mcp? An open-source MCP server that lets AI agents such as Claude Code and OpenAI Codex manage Qdrant Cloud (clusters, backups, API keys) and work with Qdrant data (collections, vector and hybrid search, text memory) through natural language.

How do I connect Claude Code to Qdrant? Run claude mcp add qdrant -e QDRANT_CLOUD_API_KEY=your-key -- uvx qdrant-full-mcp, then ask Claude to list your clusters. For Codex, use codex mcp add qdrant --env QDRANT_CLOUD_API_KEY=your-key -- uvx qdrant-full-mcp.

How is it different from the official mcp-server-qdrant? The official server is a semantic memory with two tools (store and find). qdrant-full-mcp includes the same store and find behaviour and collection layout, and adds Qdrant Cloud management, backups, database keys, named and sparse vectors, payload indexes, hybrid search and confirmation-based safety. See the comparison.

Can it create a free Qdrant Cloud cluster? Yes. Ask "create a free cluster in <region>". Qdrant allows one free cluster per account; a second request returns a clear quota error.

Do I need to generate embeddings myself? No for text: store_text and find_text embed locally with FastEmbed. Yes for the vector tools (upsert_points, query_points, hybrid_query_points), which take your own dense or sparse vectors.

Does it support hybrid search? Yes. hybrid_query_points combines a dense and a sparse query with reciprocal rank fusion (RRF) or distribution-based score fusion (DBSF).

Can I use it without Qdrant Cloud? Yes. Point QDRANT_URL at a self-hosted Qdrant, or set QDRANT_LOCAL_PATH to run Qdrant inside the server with no installation.

Is it safe to let an AI agent manage my database? Changes are dry runs until confirmed, deletes and in-place restores require the exact resource name, and QDRANT_MCP_READ_ONLY=1 blocks all writes. Your MCP client also asks before running tools.

Is this an official Qdrant product? No. It is an independent, MIT-licensed community project and is not affiliated with or endorsed by Qdrant.

Status

Verified live on Qdrant Cloud: cluster create, update, restart, suspend and unsuspend; database API keys including the remembered-key flow across server restarts; collections, named and sparse vectors, payload indexes, upserts, dense, sparse and hybrid search, deletes; store_text / find_text and filters. Also verified through the MCP protocol over stdio and streamable HTTP, in local mode, and in Docker.

Not yet verified live: backups, backup schedules, restores and cluster delete (free-tier clusters do not support backups). Reports from paid-cluster users are welcome.

Roadmap: snapshots, collection aliases, quantization and HNSW options, payload updates without re-upserting, a copy_collection tool. Out of scope: members, roles and billing; hybrid-cloud environments.

Contributing

Issues and pull requests are welcome.

git clone https://github.com/Jeevav62/qdrant-full-mcp && cd qdrant-full-mcp
pip install -e ".[dev]"
pytest

The Cloud REST gateway expects snake_case query parameters (for example page_size) and accepts camelCase JSON bodies; schemas live in qdrant-cloud-public-api.

License

MIT. Unofficial community project, not affiliated with or endorsed by Qdrant. "Qdrant" is a trademark of its owner.