Mcp Qdrant

io.github.infoinlet-marketplacePublished by GitHub account infoinlet-marketplacev0.1.1Updated Oct 24, 2026

Read-only Qdrant vector DB for AI agents — collections, info, browse points, count, search.

VerifiedSTDIODesktop onlyDatabasesKnowledge & Memory

Overview

AI-generated overview

A local, read-only MCP server that lets an AI assistant inspect a Qdrant vector database: list collections, view info, browse and count points, and run searches

What you can do
List collections and show collection information from a Qdrant instance. Browse stored points and count them. Run searches against the vector data. Access is read-only, so the assistant can inspect and query but not modify the database.
When to use it
Useful when an assistant needs to explore or query an existing Qdrant vector database, for example to check what collections exist, sample stored points, or run similarity searches without risking changes.
Requirements
Runs as a local process on the user's machine via the npm package, so a Node.js runtime is needed. It must be pointed at a reachable Qdrant instance; the manifest declares no environment variables, headers or authentication, so connection details are not specified in the provided material.
Before you install
The manifest declares no authentication, so anyone who can run it may reach the Qdrant instance it connects to; secure that endpoint and its network access. Although described as read-only, confirm that the configured credentials or endpoint cannot write or delete data.

Installation

In SourceWeft

  1. Open Mcp Qdrant in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.