Skip to main content
Glama
466,320 tools. Updated 2026-08-19 13:05

"Using Qdrant vector database for code indexing" matching MCP tools:

Matching MCP Servers

Matching MCP Connectors

  • Corporate travel: search and book flights, hotels, rail and transfers, manage orders.

  • Cloudflare Workers MCP server: code-explainer

  • Check health of all memory components: embedding provider, Qdrant vector store, and optional Memgraph graph database. Returns JSON status to verify backend connectivity before recall queries.
    Apache 2.0
  • Check the current index status, including database location, indexing state, total items, modules indexed, and progress if running.
    MIT
  • List all Qdrant collections with their point counts to inspect and manage vector store contents.
    Apache 2.0
  • Remove a project's codebase index from the vector database, safely stopping file watchers and canceling in-progress updates before deletion.
    AGPL 3.0
  • Add multiple context entries to a vector database in one batch operation for efficient bulk indexing and storage of semantic information.
    MIT
  • Ask questions about recent code changes and get answers synthesized from git diff and code context. Understand what changed, identify bugs, or assess impact without manual code review.
    MIT
  • Retrieve integration documentation for databases, vector stores, and models. Specify the integration type and optional name to get targeted guides.
    MIT
  • Set up a ChromaDB vector database with LangChain integration, storing text embeddings and optional metadata, with persistence support, returning a retriever.
    MIT
  • Query a ChromaDB vector database to retrieve relevant documents using LangChain integration. Specify the persist directory and number of results.
    MIT
  • Retrieve relevant information from a long-term knowledge base using semantic search. Access context, facts, or past interactions stored in Qdrant.
    MIT