Linksee Memory vs Cognee

A side-by-side look at the Linksee Memory and Cognee MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Linksee Memory logoLinksee MemoryKnowledge & Memory · Local subprocess (stdio)Local-first cross-agent memory with a 6-layer structure, Ebbinghaus-style forgetting curve, and drift detection that catches when code diverges from past decisions. One SQLite file shared across Claude Code, Cursor, Codex, and Gemini — no account or API key. npx linksee-memory57GoodAuth: no auth requiredCognee logoCogneeKnowledge & MemoryMemory manager for AI apps and Agents using various graph and vector stores and allowing ingestion from 30+ data sources48FairAuth: no auth required

Verdict: choose Linksee Memory for knowledge & memory work as a local process; choose Cognee for knowledge & memory. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Linksee Memory logoChoose Linksee Memory when

  • You need dedicated capabilities in the Knowledge & Memory domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
Explore Linksee Memory

Cognee logoChoose Cognee when

  • You need dedicated capabilities in the Knowledge & Memory domain.
  • Its auth model fits you: No auth required.
  • You have the keys it needs: LLM_API_KEY.
Explore Cognee

Feature & specification comparison

Rows where the two servers differ are marked.

SpecLinksee Memory logoLinksee MemoryCognee logoCognee
CategoryKnowledge & MemoryKnowledge & Memory
Quality signal57/100 · Good48/100 · Fair
Install commandConfirmedNot confirmed yet
TransportLocal subprocess (stdio)—
AuthNo auth requiredNo auth required
PricingFreeFree
Required env varsNone listedLLM_API_KEY
Verified ownerCommunity listingCommunity listing
GitHub stars1532,581
Directory activity 4 views 0 installs 0 upvotes 5 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Linksee Memory tools

No tool names declared yet. Check the project README from the listing page.

Cognee tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Linksee Memory

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "michielinksee-linksee-memory": {
      "command": "npx",
      "args": [
        "-y",
        "linksee-memory"
      ]
    }
  }
}

Cognee

No confirmed install command for Cognee yet — follow the setup steps linked from its listing page rather than a guessed package name.

Frequently asked questions

Linksee Memory is categorized under Knowledge & Memory and uses a local stdio subprocess. Cognee belongs to Knowledge & Memory and uses an install path we have not confirmed yet. Pick Linksee Memory for knowledge & memory work and Cognee for knowledge & memory.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Cognee has no confirmed install command yet — follow its own setup instructions.

Linksee Memory is listed as free. Auth: no auth required. Cognee is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add michielinksee-linksee-memory and topoteretes-cognee as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Linksee Memory has a quality signal of 57/100 (Good) with 4 views, 0 installs and 15 GitHub stars. Cognee has 48/100 (Fair) with 5 views, 0 installs and 32,581 GitHub stars.