What problem does it solve?
Cognee core ships with a limited set of built-in database providers and data sources, so teams needing Qdrant, Milvus, Slack, Notion, or other backends must find, install, and correctly register community packages from the separate cognee-community monorepo.
Core Features & Use Cases
- Database Adapter Registration: Guides installing vector, graph, and hybrid adapters (Qdrant, Milvus, Weaviate, FalkorDB, Memgraph, DuckDB, and more) and importing their
register module before cognee initializes any engine.
- Data-Source Connectors: Explains wiring dlt-based connectors for Slack, Gmail, Notion, Confluence, and Google Drive directly into
cognee.remember() with dedicated datasets.
- Contribution Workflow: Documents how to structure, test, and publish a new package to the cognee-community repo, including the shared contract test suite.
- Use Case: A team wants cognee to store embeddings in their existing Qdrant instance; this Skill walks through installing
cognee-community-vector-adapter-qdrant, importing its register module, and setting the vector DB config.
Quick Start
Ask the assistant to configure cognee to use Qdrant as its vector database using the community adapter package.