MCP server starters · Rank #25
mcp-server-qdrant
Grade A: derived only from the two verdicts below. How grades work
An official Qdrant Model Context Protocol (MCP) server implementation
Why this verdict
How we check →- 1 commit in the last 90 days, none in the last 30. receipt ↗
- Latest release v0.8.1, 312 days ago. receipt ↗
- On current major: Pydantic. receipt ↗
Snapshot: commit c56ae5a on master, checked 2026-10-19 06:41 UTC. Receipts link to files at this exact commit.
Dependency freshness
Declared = lowest version the kit's dependency file (package.json, pyproject.toml or requirements.txt) allows. Latest = the npm "latest" tag or the newest PyPI release. TypeScript, the Stripe SDK, FastAPI and other 0.x packages are shown but not counted in the verdict.
What's in the stack
- API layer
- Pydantic
Detected from declared dependencies. A listed package means it's installed, not necessarily fully wired up.
What the README says you get
- AdminRead-only mode
Enable read-only mode (disables `qdrant-store` tool)
- AdminFastMCP logging level
Set logging level (DEBUG, INFO, WARNING, ERROR, CRITICAL)
- AISemantic memory layer
It acts as a semantic memory layer on top of the Qdrant database.
- AIFastEmbed embedding provider
Embedding provider to use (currently only "fastembed" is supported)
- AIConfigurable embedding model
Name of the embedding model to use
- APICustom tool descriptions
Custom description for the store tool
- DataStore information tool
Store some information in the Qdrant database
- DataRetrieve information tool
Retrieve relevant information from the Qdrant database
- DataLocal Qdrant database
Path to the local Qdrant database (alternative to `QDRANT_URL`)
- DataSearch result limit
Maximum number of results to return from search
- DeployMultiple transport protocols
The server supports different transport protocols that can be specified using the `--transport` flag
- DeployDocker support
A Dockerfile is available for building and running the MCP server
- DeploySmithery installation
To install Qdrant MCP Server for Claude Desktop automatically via Smithery
- TestingMCP inspector
The MCP inspector is a developer tool for testing and debugging MCP servers.
Extracted from the kit's README by a local AI model (deepseek-flash) on Sep 29, 2026. Every item is checked against an exact README quote. A README claim is the maker's description, not something we tested.
Watch mcp-server-qdrant
Get told if it goes dormant, gets archived, falls further behind on a core dependency, or changes its license or price.
History
Sep 29, 2026 → Oct 19, 2026. One square per check, colored by maintenance status. Hover for details.
Show as a table
| Date | Maintenance | Dependencies | Commits (90d) |
|---|---|---|---|
| Oct 19, 2026 | Steady | Current deps | 1 |
| Oct 12, 2026 | Steady | Current deps | 1 |
| Sep 29, 2026 | Steady | Current deps | 1 |
Sources
Every claim on this page comes from these public records, checked . Open them to verify.
- Commit history ↗ default branch (master) at the checked commit: pulse, contributors, last commit
- Releases ↗ latest release
- pyproject.toml ↗ declared dependency versions and stack (at commit c56ae5a)
- README ↗ quoted features at the checked commit
- PyPI ↗ latest versions of Python packages (each linked in the table above)