- name
- cognee-community
- description
- Use when the user needs something that ships outside cognee core — community database adapters (Qdrant, Milvus, Weaviate, Redis, Pinecone, FalkorDB, Memgraph, DuckDB, NetworkX, …), data-source connectors (Slack, Gmail, Notion, Confluence, Google Drive), custom tasks/pipelines/retrievers (Exa, ScrapeGraph, codify), Keywords AI observability — or wants to contribute a package to the cognee-community repo.
Use and contribute cognee-community packages
Community-maintained plugins live in a separate monorepo:
https://github.com/topoteretes/cognee-community. Everything installable is
under packages/; experimental/ holds demos (n8n nodes, dlt demos,
bauplan, tower) that are not published packages. Each package publishes to
PyPI as cognee-community-<family>-<kind>-<name> and imports as the same
name with underscores.
Package families
Using a database adapter
Install, then import the package's register module before cognee touches
any engine — registration is what makes the provider name valid:
uv pip install cognee-community-vector-adapter-qdrant
import cognee
from cognee import config
from cognee_community_vector_adapter_qdrant import register # noqa: F401
config.set_vector_db_config(
{
"vector_db_provider": "qdrant",
"vector_db_url": "http://localhost:6333",
"vector_db_key": "...",
"vector_dataset_database_handler": "qdrant", # only if the adapter ships one
}
)
The register.py calls use_vector_adapter(name, AdapterClass) /
use_graph_adapter(...). Setting VECTOR_DB_PROVIDER/
to a community name the register import raises "Unsupported
vector database provider". Hybrid adapters (e.g. falkordb) register as both
graph and vector — set both configs to the same provider name.