Ext Ops Panel
Open dashboard
Comparison

SQL vs Qdrant MCP

SQL is an MCP server published by Abhishekkumar2021. Marketplaces we read that list it: 1 (Official MCP Registry). Qdrant MCP is an MCP server published by avaazquezz. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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

Where each is published
MarketplaceSQLQdrant MCP
Official MCP Registry Listed
Version: 0.1.0
Downloads/month (npm): 190
Downloads/week (npm): 35
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Listed
Version: 1.0.1
Downloads/month (PyPI): 152
Downloads/week (PyPI): 33
Forks (GitHub): 0
Stars (GitHub): 1
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

SQL vs Qdrant MCP
FactSQLQdrant MCP
Marketplaces that list it11
Stars (GitHub)11
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@abhishekmcp/sql)On your machine (mcp-qdrant)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)2, secrets among them: 15, secrets among them: 1
Licence (differs)MITNot stated
Repository (differs)github.com/abhishekkumar2021/mcp-suitegithub.com/avaazquezz/qdrant-mcp
Changes in the last 7 days (differs)40
First seen2026-10-112026-10-11

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

SQL

In its own words, on Official MCP Registry:

Read-only SQL querying + schema introspection over Postgres & SQLite, with a gated write mode.

Qdrant MCP

In its own words, on Official MCP Registry:

MCP server that wraps the Qdrant vector database API as tools.

How to run each

SQL As a local MCP server: npm package

Claude Code
claude mcp add --env "DB_CONN_default=<YOUR_DB_CONN_DEFAULT>" --transport stdio sql -- npx -y @abhishekmcp/sql

Requires: DB_CONN_default (secret)

Qdrant MCP As a local MCP server: PyPI package

Claude Code
claude mcp add --env "QDRANT_API_KEY=<YOUR_QDRANT_API_KEY>" --transport stdio mcp-qdrant -- uvx mcp-qdrant

Requires: QDRANT_API_KEY (secret)

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

Only SQL asks for

  • DB_CONN_default (secret)
  • DB_WRITABLE

Only Qdrant MCP asks for

  • QDRANT_API_KEY (secret)
  • QDRANT_LOCAL_PATH
  • QDRANT_MCP_READ_ONLY
  • QDRANT_MCP_TOOLSETS
  • QDRANT_URL

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: SQL · What it can do: Qdrant MCP · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built