Use when the user wants to run cognee with Docker or docker compose — trying it out from the prebuilt image, starting the API server in a container, or bringing up the full stack (UI, MCP, Postgres, Neo4j) with compose profiles.
cognee-integrations
cognee-integrations is an open-source backend skill for Claude Code and compatible agents, published by topoteretes. Its author describes it as: “Use when the user wants to connect cognee to external services — switching LLM or embedding providers (OpenAI, Azure, Gemini, Anthropic, Ollama, OpenRouter), changing databases (Postgres, PGVector, Neo4j, Neptune, Tur…”. The project has 30k stars on GitHub and is available under the Apache-2.0 license. Add it to your setup with `git clone https://github.com/topoteretes/cognee ~/.claude/skills/cognee-integrations`.
What cognee-integrations does
All integration config is environment variables (`.env`). The authoritative, always-current list with commented examples is `.env.template` at the repo root — check it before inventing variable names. Install the matching extra before switching a backend (e.g. `pip install cognee[postgres]`).
Installation
Add cognee-integrations to your agent with:
git clone https://github.com/topoteretes/cognee ~/.claude/skills/cognee-integrationsAlways review a skill's source before installing it. This command comes from the skill's public repository; the linked repo is the source of truth for exact setup steps.
What's inside
The SKILL.md for cognee-integrations is organised into these sections:
- LLM providers
- Databases
- Storage, cache, and the rest
- MCP server (IDE integration)
- After changing providers mid-project
When to use it
Reach for cognee-integrations when you want backend help from your agent without writing the same instructions every session. Load the skill and the agent picks it up automatically for relevant tasks.
Strengths
- Clear Apache-2.0 license — safe to read and adapt
- Ships in topoteretes/cognee, an established project with 30,102 GitHub stars
- Actively maintained (recent commits)
Topics
Frequently asked questions
- What does cognee-integrations do?
- Use when the user wants to connect cognee to external services — switching LLM or embedding providers (OpenAI, Azure, Gemini, Anthropic, Ollama, OpenRouter), changing databases (Postgres, PGVector, Neo4j, Neptune, Turso), S3 storage, or the MCP server for IDE integration.
- How do I install cognee-integrations?
- Run git clone https://github.com/topoteretes/cognee ~/.claude/skills/cognee-integrations in your agent, then reload your skills. Review the source at https://github.com/topoteretes/cognee before installing.
- Is cognee-integrations free to use?
- Yes. cognee-integrations is free and open source under the Apache-2.0 license, so you can read, run, and adapt it within that license's terms.
- Where does cognee-integrations come from?
- cognee-integrations ships inside topoteretes/cognee, a repository that contains 11 catalogued skills in total. The repository's 30,102 GitHub stars apply to that whole collection, not to this skill on its own.
Related skills
More Backend →Use when the user wants to run the cognee API server (and optional UI) on their own machine — starting it, checking it's healthy, connecting the SDK or other clients to it, and choosing the right auth posture.
Audit Pinterest Ads measurement, Pinterest Tag and Conversions API, catalog and shopping readiness, visual creative, audiences, Performance+ intent, budgets, brand safety, and reporting. Use for Pinterest Ads, promoted Pins, shopping ads, catalog sales, Pinterest Tag, Pinterest Conversions API, or Pinterest Performance+.
Audit server-side paid-media measurement including server-side tag management, platform conversion APIs, event taxonomy, browser/server deduplication, consent, hashing, data quality, observability, and privacy. Use for server-side tracking, sGTM, server-side tagging, CAPI, Events API, event_id, pixel debugging, first-party measurement, or conversion data loss.
Interactively create, install, activate, and verify custom claude-mem modes, including domain-specific observation types, concept tags, optional Telegram alerts, bot setup, worker restart, and startup-context verification. Use this whenever someone asks to customize what claude-mem remembers, create or change a mode, track domain-specific notes, add observation types or tags, or send Telegram notifications for particular memories—even if they do not use the word "mode."