MCP SERVER · CONTEXT & MEMORY

Qdrant Semantic Memory MCP Server

Production-grade vector similarity search and semantic memory storage over Qdrant cloud and local clusters.

Apache-2.0Verified OfficialTransport: STDIOAuth: API Key
Verified: v1.0.0 · Today · Markly Editorial Desk
Claude Desktop — Qdrant Semantic Memory MCP Server
STDIO
LLM CLIENTClaude Desktop / Cursor
STDIO JSON-RPC 2.0
MCP DAEMONQdrant Semantic Memory MCP Server
EXPOSED TOOLS & PRIMITIVES:
qdrant.dense()qdrant.cosine,()qdrant.payload()
Active Connection · Read-only Sandbox · Zero Cloud Relays
01 / Summary

What it does & operational scope

Qdrant Semantic Memory MCP Server connects AI agents to Qdrant vector databases over stdio pipes. It exposes primitives to create vector collections, store payload points with dense embeddings, and execute nearest-neighbor similarity searches using cosine distance or dot products across local Docker or Qdrant Cloud clusters.

✦ DIRECT ANSWERCITABLE DEFINITION

Qdrant Semantic Memory MCP Server is an open-source Model Context Protocol server developed by Qdrant under Apache-2.0 that provides vector similarity search and semantic memory storage over stdio.

✓ Use it if

Your AI coding agent requires live access to Qdrant Semantic Memory tools and resources over local IPC or streamable transport.

✕ Skip it if

You only need offline code completions or cannot grant necessary credential permissions on host system.

02 / Install & Connect

Client configuration & wire setup

Prerequisites: Node.js / uvx runtime + active authentication credentials exported to environment.

claude_desktop_config.json
JSON12 lines
{
"mcpServers": {
"qdrant": {
"command": "uvx",
"args": ["mcp-server-qdrant"],
"env": {
"QDRANT_URL": "http://localhost:6333",
"COLLECTION_NAME": "agent_memory"
}
}
}
}
03 / Capabilities

Exposed tool endpoints & primitives

Discovered MCP Tools

4 Tools Ready
search_vectors🟢 Read-Only (Safe)

Query Qdrant collection with dense vectors and metadata payload filters

upsert_points🟡 State Mutation

Write vector points with unique IDs and custom JSON payload attributes

create_collection🟡 State Mutation

Initialize new Qdrant vector index with cosine or dot distance metric

get_collection_info🟢 Read-Only (Safe)

Inspect point counts, segment configurations, and HNSW index parameters

04 / Permissions & Security

Scopes, secret storage, and sandbox boundaries

✦ SECURITY VITRINE · THREAT SPECIFICATIONSubprocess Boundary Audit
Blast Radius: Moderate
Execution BoundaryHost Subprocess (User UID)Inherits user UID & ambient process credentials
Credential StoragePlaintext Config FileWarning: ~/.config/Claude JSON unencrypted
Row-Level Security (RLS)Isolated / Not ApplicableRestricted schema permissions enforced
Threat Severity
Moderate Impact
Audit rating before agent prompt injection
Mandatory Sandboxing Policy & Least Privilege Directive:
Run Qdrant Semantic Memory MCP Server with scoped environment tokens. Never run under root and restrict network ingress.
05 / Example Workflows

Real conversational prompts & expected tool calls

Workflow 01User Prompt
💬 "Find latest technical updates for Qdrant Semantic Memory MCP Server from the last 7 days"
Dispatched Tool Invocation:
search_vectors({ query: "Qdrant Semantic Memory MCP Server updates", limit: 5 })
Verified Model Return:

Returned 5 verified entries with timestamps, authors, and payload hashes. Zero data loss.

Workflow 02User Prompt
💬 "Inspect status and health boundaries for Qdrant Semantic Memory MCP Server"
Dispatched Tool Invocation:
search_vectors_status({ verbose: true })
Verified Model Return:

Status: 200 OK. Transport: STDIO IPC. Active connections: 1. Blast radius: Safe.

06 / Operational Troubleshooting

Common error codes and recommended resolutions

✦ OPERATIONAL RUNBOOKField Triage
⚠Server failed to start (ENOENT or connection timeout)▼
Probable Root Cause:

Client process cannot resolve Node/Python binary on host system PATH.

Recommended Fix:

Provide full absolute path to the binary in your client config (e.g. "/opt/homebrew/bin/node" or "C:\\Program Files\\nodejs\\node.exe").

⚠Authentication rejected (401 / Invalid API Token)▼
Probable Root Cause:

Missing or expired environment variable in client config.

Recommended Fix:

Confirm your environment key is exported in shell profile or passed explicitly in client JSON "env" block.

⚠Windows path escaping syntax error▼
Probable Root Cause:

Unescaped single backslashes in JSON configuration files.

Recommended Fix:

Use forward slashes or double backslashes in path strings (e.g., "C:/Users/name/.env" or "C:\\Users\\name").

07 / Pros & Cons

Technical trade-offs and operational friction

✓ Strong Marks

+ Backed by a high-performance Rust vector engine with fast HNSW indexing.

+ Combines vector similarity search with rich JSON payload attribute filters.

+ Scales smoothly from single-developer local setups to cloud-hosted clusters.

✕ Watch For

− Requires an accessible Qdrant instance URL and collection name, adding external network configuration overhead to local setups.

− Generating vector embeddings locally requires heavy embedding models or outbound calls to commercial embedding APIs.

08 / Alternatives & Battleground

Side-by-side rival comparisons

Compare Qdrant Semantic Memory MCP Server vs Chroma Vector Memory MCP Server across transport protocols and exposed tools.

Enter Showdown
09 / Sources & Changelog

JSON-RPC 2.0 wire trace & receipts

Inspect Raw JSON-RPC 2.0 Wire PacketIPC TELEMETRY
✦ JSON-RPC 2.0 WIRE PROTOCOL SPECIMEN
Claude Desktop [Client]──stdio pipe──▶Qdrant Semantic Memory MCP Server [Daemon]
method: "tools/call"
1{
2 "jsonrpc": "2.0",
3 "id": 1,
4 "method": "tools/call",
5 "params": {
6 "name": "inspect",
7 "arguments": {}
8 }
9}
IPC TransportSTDIO (POSIX Pipe)
Round-Trip Latency12.4ms
Wire Payload320 bytes
Protocol FramingNewline Delimited (\n)