qdrant-full-mcp vs @vecto-os/mcp-server
qdrant-full-mcp is an MCP server published by Jeevav62. Marketplaces we read that list it: 1 (PyPI (MCP servers)). @vecto-os/mcp-server is an MCP server published by @vecto-os. Marketplaces we read that list it: 1 (npm registry (MCP servers)). As of our marketplace pass on 2026-11-11. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  qdrant-full-mcp | |
|---|---|---|
| PyPI (MCP servers) | Listed Version: 0.4.1 Downloads/month (PyPI): 0 Downloads/week (PyPI): 205 Forks (GitHub): 0 Stars (GitHub): 2 Not marked · First seen |
Not listed |
| npm registry (MCP servers) | Not listed | Listed Version: 0.18.0 Downloads/month (npm): 672 Downloads/week (npm): 187 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | qdrant-full-mcp | @vecto-os/mcp-server |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 2 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release (differs) | Not published | 2026-11-10 |
| Where it runs (differs) | On your machine (qdrant-full-mcp) | On your machine (@vecto-os/mcp-server) |
| Transport | Not stated | Not stated |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | MIT | UNLICENSED |
| Repository (differs) | github.com/jeevav62/qdrant-full-mcp | github.com/vecto-build/vecto-core |
| Changes in the last 7 days (differs) | 0 | 1 |
| First seen (differs) | 2026-10-13 | 2026-10-12 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
qdrant-full-mcp
The complete Qdrant MCP server: manage Qdrant Cloud (clusters, backups, API keys) and your vector data (collections, hybrid search, text memory) from Claude Code, Codex, Cursor or any MCP client.
@vecto-os/mcp-server
Vecto Model Context Protocol server — exposes /api/v1 as MCP tools + resources for Claude Code, Cursor, Claude Desktop, etc.
How to run each
qdrant-full-mcp
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
@vecto-os/mcp-server
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: qdrant-full-mcp · What it can do: @vecto-os/mcp-server · Compare two other plugins
Package data comes from the Python Package Index (pypi.org). Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.