Skip to main content
Glama
ChrisGVE

Workspace Qdrant MCP

by ChrisGVE
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Hybrid

Related Servers

Alternatives to Workspace Qdrant MCP

No user-submitted related servers found.

    Related Servers

    • Super-Memory-TS

      Veedubin
      A
      license
      Not graded
      quality
      D
      maintenance
      Local-first semantic memory server with project indexing for AI assistants. It enables AI assistants to store, retrieve, and search memories and project code using embeddings and vector search.
      68 npm
      MIT

    • mcp-vector-memory

      BBerthod
      A
      license
      Not graded
      quality
      C
      maintenance
      Gives multiple AI coding agents a shared, persistent memory by indexing your code and documentation into a vector database with AST-aware chunking and hybrid semantic/keyword search. Agents can search across projects and store, update, or forget decisions, conventions and lessons learned, all self-hosted with local embeddings.
      MIT

    • remembrallmcp

      roboticforce
      A
      license
      Not graded
      quality
      A
      maintenance
      Persistent knowledge memory layer for AI agents. Hybrid semantic + full-text search with pgvector, code dependency graph with blast-radius impact analysis, and incremental indexing for 7 languages. In-process ONNX embeddings, no external API required.
      31 npm
      35
      MIT

    • Vectr

      swapnanil
      A
      license
      A
      quality
      A
      maintenance
      Semantic codebase search + persistent working memory for AI code editors. Local, zero-config, MCP. No API key.
      23
      112 PyPI
      2
      MIT
    Deploy Server
    Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    A4/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct function: grep searches code lines, list navigates files, retrieve fetches known documents, rules manages preferences, search discovers content, and store ingests content. There is no functional overlap.

    Naming Consistency5/5

    All tool names are single lowercase verbs (grep, list, retrieve, rules, search, store), following a consistent and predictable pattern.

    Tool Count5/5

    With 6 tools covering searching, navigation, retrieval, storage, and rule management, the count is well-scoped for a workspace knowledge server without being excessive or sparse.

    Completeness4/5

    The tool surface covers the core workflows of searching, browsing, retrieving, storing, and managing rules. One minor gap is the lack of explicit update/delete operations for stored documents, though store may allow overwriting.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive

    Resources