Skip to main content
Glama
famtong8-dev

w3-mcp-server-qdrant

by famtong8-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to w3-mcp-server-qdrant

No user-submitted related servers found.

    Related Servers

    • qdrant-llamaindex-mcp-server

      azhang
      A
      license
      B
      quality
      D
      maintenance
      An MCP server for querying and managing LlamaIndex documents stored in Qdrant vector databases, with automatic embedding model detection and extensive tools for search, retrieval, and collection management.
      17
      Apache 2.0

    • mcp-server-qdrant

      vaporif
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for Qdrant vector database with local BERT embeddings. Enables semantic search and vector storage operations through natural language.
      MIT

    • vault-rag-mcp

      fjacquet
      F
      license
      A
      quality
      A
      maintenance
      MCP server for semantic search in an Obsidian Second Brain vault using self-hosted Qdrant and Google Gemini embeddings.
      3
      -

    • @sanderkooger/mcp-server

      sanderkooger
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server implementation that provides tools for retrieving and processing documentation through vector search, enabling AI assistants to augment their responses with relevant documentation context. Uses Ollama or OpenAI to generate embeddings. Docker files included
      21 npm
      30
      MIT

    • Tiny Chat

      to-aoki
      A
      license
      D
      quality
      C
      maintenance
      A lightweight RAG system that provides an MCP server for searching and interacting with vector-based knowledge bases. It enables users to perform retrieval-augmented generation and search across Qdrant collections through a standardized interface.
      1
      2
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: listing collections vs. searching within a collection. No overlap or ambiguity.

    Naming Consistency5/5

    Both tools follow a consistent 'qdrant_verb_noun' pattern (list_collections, search), making it predictable.

    Tool Count3/5

    Only two tools for a vector database feels thin; typical usage would benefit from additional CRUD operations. However, for a focused query-only server, it might be borderline acceptable.

    Completeness2/5

    Significant gaps: no tools to create/delete collections, insert/update/delete points. Agent cannot populate or manage data, only list and search existing content.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources