What problem does it solve?
Switching cognee between LLM providers, embedding models, databases, or storage backends requires knowing the correct environment variables and matching pip extras, and misconfiguring one side (LLM vs. embeddings) silently leaves the other on OpenAI defaults.
Core Features & Use Cases
- LLM & Embedding Provider Setup: Configure OpenAI, Azure, Gemini, Anthropic, Ollama, OpenRouter, or AWS Bedrock via
LLM_PROVIDER and related variables, with independent EMBEDDING_* configuration.
- Database & Storage Switching: Set relational (sqlite/postgres), vector (lancedb/pgvector/neptune/turso), graph (ladybug/neo4j/neptune) backends, plus S3 storage and session cache options.
- MCP Server for IDEs: Start the MCP server with
docker compose --profile mcp up to connect Cursor, Claude Desktop, or Claude Code to cognee memory.
- Use Case: You want to move a project from OpenAI to a local Ollama model with Neo4j as the graph store — the Skill tells you exactly which env vars, extras (
cognee[ollama], cognee[neo4j]), and post-switch reset steps are required.
Quick Start
Ask the assistant to switch cognee from OpenAI to Gemini for the LLM and from lancedb to pgvector for the vector store, and have it list the exact .env variables and pip extras needed.